Quarterly Planning
We have three objectives in publishing our quarterly planning:
- We want to be transparent about the work we are doing
- 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 the community on developments around the RIPE Database
We launched this initiative in Q4 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 RIPE Database 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 | Database documentation |
We are migrating the RIPE Database documentation to a new interface. We have moved the base documentation and are migrating any other DB support docs to the new site. |
In progress Work continues from Q3 2022. |
| 2 |
Formulating a framework with the community to determine the level of criticality of each RIPE NCC service, including the RIPE Database. |
We will engage with the community to define requirements and plan on how to proceed concerning potential cloud migration and infrastructure improvements. In December 2022, we published a proposed a completed criticality form to the DB WG. |
In progress Work continues from Q4 2021. |
| 3 | NWI-12: NRTMv4 | Working on server-side implementation. | In progress |
| 4 | Open Source Web Application | As announced at RIPE 85, we will publish the source code to our web application. | In progress |
| 5 | Open Full Text Search API | As previously announced, we will open the Full Text Search API to end users. | In progress |
|
Items completed in the last quarter |
|||
|
More information can be found on the archived plans page. |
|||
Community Input on Planning
We want the community to contribute to our plans and suggest additional work items. The Database Working Group (WG) employs a process called Numbered Work Items (NWIs) that allows anyone to suggest work the RIPE NCC should carry out to improve the RIPE Database. A lot of work takes place each quarter to investigate the feasibility of NWIs and plan for their implementation.
When an NWI is agreed and the RIPE NCC will schedule related work, it will be added to our quarterly planning.
Please share your comments with us or post them on the Database Working Group (WG) mailing list. And we will be monitoring all the other channels where people talk about the RIPE Database.
We will be adding your feedback on this page as we progress with our plans.
| Reference | Input | RIPE NCC Reaction |
|---|---|---|
| DB-2021-#01 | NWI-2: Displaying history for database objects where available |
Our legal team is reviewing this request. We first recorded this request in Q4 2021. |
| DB-2021-#02 | NWI-4: role of status: field in multivalued status context |
The RIPE Database team has been requested by the Database WG to prepare an impact analysis of the 'ALLOCATED-ASSIGNED PA' status. The team is preparing an impact analysis. We first recorded this request in Q4 2021. |
| DB-2021-#03 | NWI-13: Geofeed Implement the Geofeed attribute in the RIPE Database. For more information, please read RFC 9092. |
Our legal team provided an analysis of "geofeed:" validation at RIPE 84, and we have updated the Database WG by email. At RIPE 85, we presented the Geofeed implementation, and we are currently discussing the purpose with the Database WG. We first recorded this request in Q4 2021. |
| DB-2021-#04 | NWI-12: NRTM v4 Modernise Whois update notifications using NRTM |
Proposed Solution Definition to DB-WG, based on draft NRTM v4 proposal by Sasha Romijn. The item was added to the quarterly plans (item 3 above). We first recorded this request in Q4 2021. |
Archived Quarterly Plans
You can find our plans from the previous quarters on this page. The Q2 2023 plan will be archived once we publish the Q3 2023 planning.