Dear Kurt,

Thank you for your response. We agree with you: avoiding deadlocks and keeping our architecture simple without too many interdependencies are very important principles in our design. We believe that having a secondary cloud provider for RPKI repositories and keeping our own-premises infrastructure for WHOIS is one of the steps in achieving this goal, and we will continuously review our plans and adapt as needed.

We appreciate your input and welcome others to join the discussion too. Next week I will present part of those plans in NCC Services WG, looking forward to hear your feedback there.

Kind regards,
Felipe

On 10 May 2021, at 14:09, Kurt Kayser <kurt_kayser@gmx.de> wrote:

Hello Alun,

while I welcome this technical move towards the cloud and a more resilient infrastructure, please let's not forget to avoid any deadlocks in the future.

I could also envision a difficult situation for DNS over HTTPS (i.e. how would you run HTTPS without DNS?).

What I want to say is, core-services that are fundamentally important, such as the RIPE-Database or RPKI-validations rely on direct availability.

In case of a catastrophic AWS failure, or simply "bootstrapping the Internet" - let's always keep this in mind that we are able to start up the net without too many interwoven services.

So this is a vote towards "keep also a plan-b in reserve" in case there a problem.

All the best - and please keep healthy,

regards, Kurt


Am 10.05.21 um 13:40 schrieb Alun Davies:
Dear colleagues,

The mission critical services the RIPE NCC provides to the Internet community require a solid technical foundation. In this new article on RIPE Labs, Felipe Silveira looks at plans to use cloud infrastructure as a means to that end. The full article is available here:

https://labs.ripe.net/author/felipe_victolla_silveira/rpki-repositories-and-the-ripe-database-in-the-cloud/

Kind regards,

Alun Davies
RIPE Labs Editor
RIPE NCC