Skip to main content

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.

Q1 2026 Plans

Last Updated: 16 December 2025

Item 1: 2025-02 Automatic Revocation of Persistently Non-functional Delegated RPKI CAs

The policy proposal 2025-02 “Revocation of Persistently Non-functional Delegated RPKI CAs” was accepted on 15 October 2025. Work on an implementation will start in Q1 2026.

Status: Planned

Item 2: Resource Signed Checklists

The community requested (RPKI-2024#01) that we add support for Resource Signed Checklists (RSC, RFC 9323). The terms and conditions of the RPKI service have been updated recently to support this, and we are planning to implement API support for RSC in Q1. A user interface can be added later if we find that there is demand for this.

Status: Planned

Item 3: ISO 27001 Audit

In addition to the Soc2 Type II audit that was concluded in Q4 of 2025 for RPKI-related services, the RPKI Team is also involved in an organisation-wide ISO 27001 audit.

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 Q1 2026 plans will be archived once we publish the Q2 2026 planning.