Archived Plans
You can find our completed plans from previous quarters, along with requests from the community. We are updating this page at the end of each quarter.
2024 Plans and Community Input
Item 1: RDAP RIR Search
The team is working on the implementation of the 'RIR Search' feature. We have implemented a new feature, 'Basic Search Features', and are working on the 'Relation Searches' feature, which will be included in a future Whois release.
Status: In progress
Item 2: Bulk Mail Sender Requirements
Description: We will make changes to comply with new requirements for bulk email senders. As part of the Whois 1.111 release, we will implement mail bounce detection (i.e. an outgoing message has permanently failed delivery) and also unsubscription (i.e. one-click unsubscribe from a mail client). You can find more information on the message we sent to the Database WG.
Status: Completed in Q2 2024
Item 3: Phase Out MD5
Description: Using MD5 hashed password authentication is a security risk, both for the RIPE NCC and the users of the RIPE database. We plan to implement alternative authentication mechanisms such as API keys (application passwords) and OAUTH 2.0 flows.
Status: In progress
Community input DB-2021#01: NWI-2 - Displaying history for database objects where available
DB-WG to define requirements for NWI-2.
Status: Under consideration.
In Q3 2024, our team documented the use of historical query commands for the DB-WG and published statistics.
Community input DB-2021#02: NWI-4 - role of status: field in multivalued status context
The team completed the impact analysis of the 'ALLOCATED-ASSIGNED PA' status. After the decision from the WG co-chairs on NWI-4 to proceed with the new ALLOCATED-ASSIGNED PA status proposal, our team deployed it into production.
Status: Completed in Q2 2024.
Community input DB-2021#04: NWI-12 -- NRTMv4
Proposed Solution Definition to DB-WG, based on draft NRTM v4 proposal by Sasha Romijn. We worked on the server-side implementation and are now working on the client-side implementation. More information can be found on GitHub.
Status: In progress.
In Q3 2024, our team implemented a key rollover in NRTMv4. We will continue with the remaining work to implement a second client (in addition to IRRd), and fix a race condition with signature files.
2023 Plans and Community Input
Item 1: Open Full Text Search API
We opened the Full Text Search API to end users.
Completed in Q2 2023.
Item 2: Formulating a framework with the community to determine the level of criticality of each RIPE NCC service, including the RIPE Database.
We engaged with the community to define requirements and planned how to proceed with potential cloud migration and infrastructure improvements. Read more about our service criticality rating.
Completed in Q2 2023.
Item 3: Database documentation
We migrated the RIPE Database documentation to a new interface. Initially, we moved the base documentation and then migratedInitially any other DB support docs to the new site.
Completed in Q4 2023.
Item 4: Open Source Web Application
As announced at RIPE 85, we planned to publish the source code to our web application. After setting up a security audit, we completed this activity by RIPE 87.
Completed in Q4 2023.
Community input DB-2021#03: NWI-13 - Geofeed
We implemented Geofeed attribute in the RIPE Database. For more information, please read RFC 9092.
Completed in Q4 2023.
Community input DB-2021#04: NWI-12 - NRTMv4
Proposed Solution Definition to DB-WG, based on draft NRTM v4 proposal by Sasha Romijn. We worked on the server-side implementation. More information can be found on GitHub.
Completed in Q2 2023.
2022 Plans and Community Input
Item 1: Usability improvements to the web search
We made improvements to the web search function of the RIPE Database. You can find more details in our RIPE Labs article.
Completed in Q2 2022.
Item 2: RDAP profile
We are implementing the RDAP cidr0 and NRO profiles to express CIDR notation, increase consistency in service offerings and simplify the development of client software that uses those services.
Completed in Q4 2022.
Community input DB-2021#05: Investigate implementing UTF-8 in the RIPE Database
We published a RIPE Labs article explaining the impact of this change.
Completed in Q2 2022.
Community input DB-2021#06: Deprecation of Whitepages
We depreciated the white pages after a community discussion on the topic.
Completed in Q1 2022.