[routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]?

Dear Job,

> Op 20 sep. 2021, om 13:26 heeft Job Snijders via routing-wg <routing-wg at ripe.net> het volgende geschreven:
> 
> Hi working group,
> 
> In recent mail threads the concepts of "Hosted RPKI" and "Delegated
> RPKI" came up, but as mentioned by Tim and Rubens, another flavor also
> exists! A "hybrid" between Delegated and Hosted, informally known as
> "publish in parent" (aka RFC 8181 compliant Publication Services).
> 
> There are multiple benefits to the general RPKI ecosystem when RIRs and
> NIRs support RFC 8181:
> 
>    * Resource Holders are relieved from the responsibility to operate
>      always online RSYNC and RRDP servers.
> 
>    * Reducing the number of Publication servers reduces overall
>      resource consumption for Relying Parties. Consolidation of
>      Publication Servers improves efficiency and is generally
>      considered advantageous.
> 
>    * Helps avoid "reinventing the wheel": it might be better to have a
>      small group of experts build a globally performant and resillient
>      infrastructure that serves everyone, rather than everyone building
>      the 'same' infrastructure.
> 
> Other RIRs and NIRs are also working on RFC 8181 support. RFC 8181 is
> relatively new so it'll take some time before we see universal
> availability.
> 
>    NIC.BR (available): https://registro.br/tecnologia/numeracao/rpki/
>    APNIC (available): https://blog.apnic.net/2020/11/20/apnic-now-supports-rfc-aligned-publish-in-parent-self-hosted-rpki/
>    ARIN (planned): https://www.arin.net/participate/community/acsp/suggestions/2020/2020-1/
> 
> Is implementing RFC 8181 support something RIPE NCC should add to the
> https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-planning-and-roadmap ?
> 
> What do others think?
> 
> Kind regards,
> 
> Job
> 
> Relevant documentation:
> https://datatracker.ietf.org/doc/html/rfc8181

Thanks for bringing this up. 
Please be aware that the roadmap you mentioned just shows the roadmap for the current quarter and not for a longer period. 
If you see something missing there, it does not mean that we don’t intend to work on it, just (probably) not in the current quarter, unless it is urgent of course. The reason why we chose to publish a quarterly roadmap, is to facilitate discussions on our priorities with this working group. 
This is exactly why I’m very pleased that you brought up this topic (potential work item). We can always add new functionality to future roadmaps. In about a week, we will publish our roadmap for Q4. 

In the past, RFC8181 support (Hybrid RPKI, publish in parent, repo-as-a-service) has been asked from RIPE NCC by a few community members, for example by Benno Overeinder at RIPE82 in the routing-wg session:https://ripe82.ripe.net/archives/steno/47/ <https://ripe82.ripe.net/archives/steno/47/> 

I look forward to seeing a discussion here on this topic to find out if there is a broader interest.

Kind regards,

Nathalie Trenaman
RIPE NCC





-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/routing-wg/attachments/20210920/60fe4aac/attachment.html>