<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">Dear Kurt,</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">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.</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">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.</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">Kind regards,</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">Felipe</span><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 10 May 2021, at 14:09, Kurt Kayser <<a href="mailto:kurt_kayser@gmx.de" class="">kurt_kayser@gmx.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div class=""><p class="">Hello Alun,</p><p class="">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.<br class="">
</p><p class="">I could also envision a difficult situation for DNS over HTTPS
(i.e. how would you run HTTPS <u class="">without</u> DNS?).</p><p class="">What I want to say is, core-services that are fundamentally
important, such as the RIPE-Database or RPKI-validations rely on <u class="">direct</u>
availability.</p><p class="">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.</p><p class="">So this is a vote towards "keep also a plan-b in reserve" in case
there a problem.</p><p class="">All the best - and please keep healthy,</p><p class="">regards, Kurt</p><p class=""><br class="">
</p>
<div class="moz-cite-prefix">Am 10.05.21 um 13:40 schrieb Alun
Davies:<br class="">
</div>
<blockquote type="cite" cite="mid:FC210712-4ECE-4992-A1DE-E554B6AA7855@ripe.net" class="">
<pre class="moz-quote-pre" wrap="">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:
<a class="moz-txt-link-freetext" href="https://labs.ripe.net/author/felipe_victolla_silveira/rpki-repositories-and-the-ripe-database-in-the-cloud/">https://labs.ripe.net/author/felipe_victolla_silveira/rpki-repositories-and-the-ripe-database-in-the-cloud/</a>
Kind regards,
Alun Davies
RIPE Labs Editor
RIPE NCC
</pre>
</blockquote>
</div>
</div></blockquote></div><br class=""></body></html>