Quarterly Planning
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 want to be transparent about the work we are doing with RPKI
- We want your input on that work and our planning, and we want to document that input, and let you know if and when we can add your suggestions to our planning
- We want an open dialogue with members and community on developments around RPKI
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.
Q4 2024 Plans
Last updated: 27 September 2024
Item 1: 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.
We made good progress and started beta testing at the beginning of Q3 2024. We expect to go live before the RIPE 89 Meeting.
Status: In progress
Item 2: Improve ROA history
Description: After the delivery of the RPKI Dashboard improvements (item #2), we plan to improve ROA history insights that allow users to review and revert past changes more easily.
Status: Planned
Item 3: Support ASPA
Description: 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. 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 want to await formal consensus before implementing this.
Status: On hold (pending IETF consensus)
Item 4: Support BGPsec Router Certificates in API
Description: 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
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-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.
Archived Quarterly Plans
You can find our plans from previous quarters on this page. The Q4 2024 plans will be archived once we publish the Q1 2025 planning.