Quarterly Planning
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.
Q2 2023 Plans
Last Updated: 21 March 2023
| Item | Activity | Description | Status |
|---|---|---|---|
| 1 |
RPKI compliance project (ISAE3000) |
We needed a well-recognised audit framework that both encompasses all important IT security elements and can be tailored towards the design principals and RFCs of RPKI. For this purpose, we want to develop an RPKI audit framework that can potentially also be used by other Trust Anchors. This is now an ISAE3000/SOC 2 Type II audit framework. We are now in the process of gathering evidence for our audit. In 2023, we will first start with an assessment of the framework by a third party. Because ISAE3000/SOC 2 Type II frameworks are free-form by nature, we want to ensure that we have the right controls and evidence in place. |
In progress |
| 2 |
RPKI Dashboard improvements |
We will work on the RPKI dashboard to improve its usability and extend its functionality with new object types. | Work will start in Q2 |
| 3 |
rsync repository capability |
We are aware of the capacity limitations of our rsync repositories. The rsync repositories are mainly used as a fallback during issues with RRDP. This quarter, we will work on increasing their capacity and resiliency. | Work will start in Q2 |
| 4 | New online HSMs | We have received new online Hardware Security Modules (HSMs). After our vendor does the prerequisite work, we will work on migrating to these new HSMs. | Work will start later in 2023 |
|
Items completed in the last quarter |
|||
|
|||
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 are investigating possibilities here and will add a reaction when ready. |
| 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 are investigating possibilities here and will add a reaction when ready. |
| RPKI-2021-#05 |
Suggestion to allow 3rd party access to the LIR Portal to make RPKI changes. |
We are waiting for an internal SSO project to be completed, and we will add a reaction when ready. |
| RPKI-2023-#01 |
Suggestion to add RSC support |
We are aware of multiple use cases for RSC (e.g. proof of ownership of an ASN). |
Archived Quarterly Plans
You can find our plans from previous quarters on this page. The Q2 2023 plan will be archived once we publish the Q3 2023 planning.