<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span class="">Hi all,</span><br class=""><br class=""><span class="">First of all, I would like to thank you for your input and the engaged discussion. It is highly appreciated and helps us to decide how to proceed with our new service.</span><br class=""><br class=""><span class="">After carefully going through the different points raised, we have decided to proceed with the deployment of the service as it currently stands, without restrictions.</span><br class=""><br class=""><span class="">At the same time, we took note of opposing views and encourage you to continue the discussion here. Should the community reach consensus on implementing the restriction at a later stage, we will add this to our roadmap and implement it as part of our existing process. Our quarterly roadmaps are published at the following address:</span><br class=""><br class=""><a href="https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-planning-and-roadmap" class="">https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-planning-and-roadmap</a><br class=""><br class=""><span class="">Kind regards,</span></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span class=""><br class=""></span></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span class="">Felipe Victolla Silveira</span></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Chief Operations Officer</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">RIPE NCC</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On 29 Sep 2022, at 16:15, Felipe Victolla Silveira <<a href="mailto:fvictolla@ripe.net" class="">fvictolla@ripe.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Dear all,</span><br style="caret-color: rgb(0, 0, 0);" class=""><br style="caret-color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0);" class="">As some of you are aware, the RIPE NCC has been working on a new service for RPKI, called Publish in Parent. This service is intended for RPKI users who have chosen to run their own Certificate Authority (delegated RPKI) but don’t want to take the burden of maintaining a highly available publication point. By using this service, it will be possible for our members with delegated RPKI to publish their signed RPKI objects in the RIPE NCC repositories (RRDP and rsync) instead of maintaining their own.</span><br style="caret-color: rgb(0, 0, 0);" class=""><br style="caret-color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Following a discussion with the Executive Board in our meeting last June, we would like to ask our community for input on the requirements for this service. The service was originally designed to allow all objects to be published in our repositories, regardless of whether the associated resources are part of the RIPE NCC or another RIR, and this is how we would like to proceed. However, it has been argued that there should be a restriction in this service so that it allows only RIPE NCC resources to be published and not resources belonging to a different RIR.</span><br style="caret-color: rgb(0, 0, 0);" class=""><br style="caret-color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0);" class="">If you are potential user of this service, what are your expectations for its functionality? Do you want to be able to publish all your objects in RIPE NCC repositories, regardless of whether they are from the RIPE NCC or not? Or will you publish each object in the corresponding RIR repositories? Please note that we are only talking about publication. The objects out of region will be signed with their own parent certificate.</span><br style="caret-color: rgb(0, 0, 0);" class=""><br style="caret-color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0);" class="">If you are a developer of one of the Relying Party softwares, will the presence or absence of such a restriction impact your software package in any way? Do you expect the need to make changes, depending on the direction this takes?</span><br style="caret-color: rgb(0, 0, 0);" class=""><br style="caret-color: rgb(0, 0, 0);" class=""><font class=""><span style="caret-color: rgb(0, 0, 0);" class="">To make informed decisions on how we should progress with Publish in Parent, we need input from potential users of the service. Please reply with your feedback until 14 October so we can incorporate it in our planning and inform you about our progress at RIPE 85.</span></font><br style="caret-color: rgb(0, 0, 0);" class=""><br style="caret-color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Kind regards,</span><div class=""><font class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class=""></span></font><div class=""><span style="caret-color: rgb(0, 0, 0);" class="">Felipe Victolla Silveira</span></div><div class=""><span style="caret-color: rgb(0, 0, 0);" class="">Chief Operations Officer</span></div><div class=""><span style="caret-color: rgb(0, 0, 0);" class="">RIPE NCC</span></div></div></div></div></blockquote></div><br class=""></body></html>