<html><body><div id="zimbraEditorContainer" style="font-family: Times New Roman; font-size: 12pt; color: #000000" class="2"><div data-marker="__QUOTED_TEXT__">Hi,<br><br>as a LIR I do *totally* agree with Gert's position to not "give away<br>control on critical services". RIPE is in the position to guarantee a<br>service with a relevant uptime, like it did for tens of years, and should<br>think to "outsourced resources" just as backup in case of unavailability<br>of internal resources.<br><br>Regards,<br>Giuliano Peritore<br><br>-- <br> Giuliano Peritore - g.peritore@panservice.it<br> Direzione Generale - Panservice (AS20912)<br> Servizi professionali per Internet ed il Networking<br> Telefono: +39 0773 410020 - Fax +39 0773 470219<br> Numero verde: 800 901492 - http://www.panservice.it<br><br>----- Messaggio originale -----<br>Da: "Gert Doering" <gert@space.net><br>A: "Alun Davies" <adavies@ripe.net><br>Cc: ncc-services-wg@ripe.net<br>Inviato: Mercoledì, 12 maggio 2021 9:19:11<br>Oggetto: Re: [ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud<br><br>Hi,<br><br>On Mon, May 10, 2021 at 01:40:07PM +0200, Alun Davies wrote:<br>> The mission critical services the RIPE NCC provides to the Internet<br>> community require a solid technical foundation. In this new article<br>> on RIPE Labs, Felipe Silveira looks at plans to use cloud infrastructure<br>> as a means to that end. The full article is available here:<br><br>As a member, I do not want the RIPE NCC to spend our money on "give away<br>control on critical services".<br><br>Use of cloud services (or any other "outsourced infrastructure") is something<br>I consider acceptable as a *backup* in case of something catastrophic <br>happening to the RIPE NCC operated machines, to restore services to members<br>and community quicker.<br><br>Using cloud services generally implies<br><br> - loss of control <br> --> so the NCC *must* be primary authority on all data, and the cloud<br> can only be a cache<br><br> - loss of contact and responsibility<br> --> if a NCC provided service does not work, I do not want to talk to<br> a cloud provider hotline, or hear from the NCC "well, there is nothing <br> we can do, something in the cloud is broken"<br><br><br>All this cloudstuff is really great if you need "elastic services" (like,<br>when the big run on the last IPv4 space starts, scale up the LIR portal<br>to 200 instances - oh, wait, this opportunity got missed), or "low latency<br>for high bandwidth content delivery" (so, yeah, ... no?).<br><br>But for the services the NCC provides, "cloud" sounds like "yeah, someone<br>else to blaim if it explodes", and this is not why we give the NCC money.<br><br><br>(And no, there is not much trust from my side, since the ticket system is<br>*still* a major annoyance in our day to day dealing with the NCC - despite<br>promises, two years ago, to make this more usable)<br><br>Gert Doering<br> -- voting LIR contact<br>-- <br>have you enabled IPv6 on something today...?<br><br>SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer<br>Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann<br>D-80807 Muenchen HRB: 136055 (AG Muenchen)<br>Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279</div><div><br></div></div></body></html>