This page details the work we'll do on RPKI in the coming quarter, how you can give your input on that work and our reaction to that input.
We have three objectives in publishing our quarterly planning:
We launched this initiative in Q3 2021, and we are open to improving what we publish here and how we do that. So let us know if there are ways we can better present our plans.
We will update this page as our activities progress and continue to share updates on RIPE Labs, on the Routing Working Group (WG) mailing list and at RIPE Meetings and other events.
Last updated: 20 March 2024
Item 1: RPKI compliance project (ISAE3000)
Description: We needed a well-recognised audit framework that both encompasses all important IT security elements and can be tailored towards the design principals and RFCs of RPKI. For this purpose, we want to develop an RPKI audit framework that can potentially also be used by other Trust Anchors. This is now an ISAE3000/SOC 2 Type II audit framework.
The tailored ISAE3000 control framework for RPKI was designed, and we completed a gap analysis against this framework. We have completed 90% of the relevant documentation, control implementation and evidence gathering for the first certification audit.
We have also engaged with known international audit firms and are planning the execution for the first half of 2024.
Status: In progress
Item 2: RPKI Dashboard improvements
Description: We are working on the RPKI dashboard to improve its usability and make it possible to extend its functionality with new object types. We have performed a user study of the existing dashboard and have started the implementation of the new dashboard.
Status: In progress
We want the community to contribute to our plans and suggest additional work items. Please share your comments with us or post them on the Routing Working Group mailing list. We will also monitor all the other channels where people talk about RPKI.
We will be adding your feedback on this page as we progress with our plans.
Community input RPKI-2021#02: Request to add BGPsec support in Hosted RPKI
For more information, check the Routing WG mailing list archives.
Status: We are investigating possibilities here and will add a reaction when ready.
Community input RPKI-2021#04: Request to add real-time metrics and status updates of alerts or subsections to a feed
For more information, read the Q&A section of the RIPE NCC RPKI Update at RIPE 83 (presentation no.4).
Status: We are investigating possibilities here and will add a reaction when ready.
Community input RPKI-2021#05: Suggestion to allow 3rd party access to the LIR Portal to make RPKI changes
Status: We are waiting for an internal SSO project to be completed, and we will add a reaction when ready.
Community input RPKI-2024#01: Suggestion to add RSC support
Status: We are aware of multiple use cases for RSC (e.g. proof of ownership of an ASN). We will investigate the possibilities and will add a full reaction when ready.
Community input RPKI-2024#02: Known routing beacons with changing RPKI validity would help researchers
Status: Changes to the routing beacons have been proposed. However, we could not yet add an RPKI beacon as the API used would allow editing ROAs for all the RIPE NCC space, and this was not acceptable to us. We will investigate this together with the RIS team in the future.
You can find our plans from previous quarters on this page. The Q2 2024 plan will be archived once we publish the Q3 2024 planning.