On 10 May 2021, at 12:40, Alun Davies wrote:
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-...
This article is an excellent teaser for next week’s presentation in the RIPE NCC Services WG at RIPE 82. It raises a number of questions in the reader’s mind and gives an implicit promise that these will be addressed in the presentation and in subsequent discussion. Here below are some questions which occur to me, in no particular order. I am interested to know the extent to which community input has informed the project, as it touches the scope of three RIPE working groups (Database, Routing, and NCC Services) and that of the Database Requirements Task Force. The intention to include an additional cloud provider is mentioned; I would like to know what the timeline for this is, and what the current state of progress is. I wonder how the availability of the service will be assessed for testing against the proposed targets (five nines and worst-case 1-hour recovery from catastrophe). I also wonder how apparent conflict between these availability targets will be resolved. I will share my arithmetic separately later. I would like to know the rationale for two design choices: the use of the DNS, rather than BGP and anycast for maintaining or restoring service under fault conditions, and the selection of a “fallback” model rather than a “composite cloud” model. I am sure that other members of the community will have equally (or even more) interesting questions, and look forward to an interesting presentation at RIPE 82 and to the subsequent discussion. Best regards, Niall O’Reilly