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.
Q3 2025 Plans
Last Updated: 24 June 2025
Item 1: SOC Type II Audit
After receiving the SOC2 Type I Assurance Report for the RPKI service in October 2024, we are now working on the SOC2 Type II audit.
Status: In progress
Item 2: 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: In progress
Item 3: 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.
As presented at RIPE 90 we are now working on implementing support for ASPA in the test environment UI. We would like to invite any users who are interested in participating in UX/UI testing to contact Tim Bruijnzeels or Antonella de Bellis. We plan to release the UI to the production environment once it is well tested and feature complete, as we expect that there will be no more significant changes in the standard.
Status: In progress
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.
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 are still investigating the impact on the RPKI terms and conditions, but we will likely do a proof of concept implementation in the test environment when the BGPsec Router Certificate and ASPA UI support work items are done.
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 Q3 2025 plans will be archived once we publish the Q4 2025 planning.