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:

  1. We want to be transparent about the work we are doing with RPKI
  2. 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
  3. 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 2022 Plans

Last Updated: 26 September 2022

Item Activity Description Status
1 Support a Red Team security exercise In 2022, we will perform a Red Team security exercise for RPKI. A Red Team assessment is an ultimate test by an external party trying to access our systems and data through different means, such as phishing or getting physical access to our data. The exact timeline for this exercise is confidential by nature, but this is an important step towards improving security for RPKI and the RIPE NCC.

In progress

Work continues from Q1 2022.

2 Create multiple parallel internal test environments for RPKI

Currently, the RPKI team shares one environment used for Quality Assurance. This shared environment leads to longer release cycles as we can not independently evaluate multiple features in parallel. We will set up multiple independent environments (with one environment per feature if possible). Having more environments available will allow us to evaluate features independently and improve our Q&A and release process.

In progress

Work continues from Q1 2022.



3 Pilot ASPA support

Autonomous System Provider Authorization (ASPA) is an active draft (a current proposal) in the IETF sidrops working group. ASPA objects describe the provider relations for an AS number. We will provide input to the discussion by producing some code on a testbed.

In progress

Work continues from Q1 2022.

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. And we will be monitoring all the other channels where people talk RPKI.

We will be adding your feedback on this page as we progress with our plans.

Reference Input RIPE NCC Reaction
RPKI-2021-#02

Request to add BGPsec support in Hosted RPKI.

For more information, check the Routing WG mailing list archives.

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q1 2022.

RPKI-2021-#03

Request to implement "Publish in Parent" RFC 8181 support.

For more information, check the Routing WG mailing list archives.

Currently on hold due to pending approval of new terms and conditions and further technical work.

We first recorded this request in Q1 2022.

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).

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q1 2022.

RPKI-2021-#05

Suggestion to allow 3rd party access to the LIR Portal to make RPKI changes.

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q1 2022.

Archived Quarterly Plans

You can find our plans from previous quarters on this page. The Q4 2022 plan will be archived once we publish the Q1 2023 planning.

Please contact us if you need more information.

Stay up to date!

Follow the #RPKI hashtag on Twitter.