RPKI 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.
Q2 2025 Plans
Last updated: 27 March 2025
Item 1: Improve ROA History
After the delivery of the RPKI Dashboard, we plan to improve ROA history insights that allow users to review and revert past changes more easily.
Status: In progress
Item 2: SOC Type II Audit
After receiving the SOC2 Type I Assurance Report for the RPKI service in October 2024, we are now working on evidence gathering and process improvements (where applicable) in preparation for the SOC2 Type II audit that is planned for summer 2025.
Status: In progress
Item 3: Business Continuity Plan Testing
We formalised our RPKI service Business Continuity Plan (BCP) in 2024 as part of the work done in support of the SOC2 Type I audit. We intend to actively test our BCP in Q1-Q2 2025 to review if we need to make any further amendments.
Status: In progress
Item 4: Support BGPsec Router Certificates in API
Support for BGPsec Router Certificates was requested in the Routing WG. We recorded this request with reference RPKI-2021#02.
To support early adopters to use the BGPSec Protocol (RFC 8205) we plan to support BGPsec Router Certificates (RFC 8209) using the API. The RPKI Dashboard can be extended in future once more experience has been obtained.
Status: Planned
Item 5: Support ASPA
ASPA is a developing RPKI standard in the IETF that can help improve routing security by allowing AS holders to declare which provider ASNs they use, thus reducing the risks for route leaks and, to an extent, BGP path spoofing.
The pilot environment has been supporting ASPA objects for some time in its API. Details on how to use this API were shared with the routing-wg.
We would like to enable ASPA API in the production environment and extend the dashboard support for this. However, while IETF consensus seems to be close, there is still some discussion, and we plan to start by implementing this in the pilot environment only so that we can release this production when the IETF SIDROPS working group reaches consensus
Status: On hold (pending IETF consensus)
Community Input on Planning
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.
We also invite you to participate in our user research to help us with the development and improvement of the tools and services.
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.
Archived Quarterly Plans
You can find our plans from previous quarters on this page. The Q2 2025 plans will be archived once we publish the Q3 2025 planning.