You are here: Home > Manage IPs and ASNs > RIPE Database > Quarterly Planning > Archived Plans

Archived Plans

You can find our plans from previous quarters along with requests from the community on this page. We are updating this page at the end of each quarter.


Q2 2022 Plans and Community Input

Plans
Item Activity Description
1

Formulating a framework with the community to determine the level of crtiticality of each RIPE NCC service, including the RIPE Database.

Work continues in Q3 2022.

We will engage with the community to define requirements and plan on how to proceed concerning potential cloud migration and infrastructure improvements.

2 Usability improvements to the web search

Work took place from Q4 2021 until Q2 2022.

We made improvements to the web search function of the RIPE Database. We plan a phase two later in 2022 or 2023 to work on adding full text search features to the query page, and opening the full text search API.

You can find more details in our RIPE Labs article.

Community Input
Reference Input RIPE NCC Reaction
DB-2021-#01 NWI-2: Displaying history for database objects where available Our legal team is reviewing this request.
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.
DB-2021-#03 NWI-13: Geofeed

Implement 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 will update the Database WG by email. The RIPE Database team will reply with an impact analysis.

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.
DB-2021-#05 UTF-8: Investigate implementing UTF-8 in the RIPE Database

Completed

We published a RIPE Labs article explaining the impact of this change.


Q1 2022 Plans and Community Input

Plans
Item Activity Description
1

Formulating a framework with the community to determine the level of crtiticality of each RIPE NCC service, including the RIPE Database.

Work continued in Q2 2022.

We will engage with the community to define requirements and plan on how to proceed concerning potential cloud migration and infrastructure improvements.

2 Usability improvements to the web search

Work continued in Q2 2022.

We are making improvements to the web search function of the RIPE Database.

You can find more details in our RIPE Labs article.

Community Input
Reference Input RIPE NCC Reaction
DB-2021-#01 NWI-2: Displaying history for database objects where available

Our legal team is reviewing this request.

DB-2021-#02 NWI-4: role of status: field in multivalued status context

Our team has investigated the tuple (prefix and status) proposal and have found it infeasible to implement. We are waiting on further community discussion on this topic.

DB-2021-#03 NWI-13: Geofeed

Implement Geofeed attribute in the RIPE Database. For more information, please read RFC 9092.

Our legal team is reviewing the restriction on prefix size.

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.

DB-2021-#05 UTF-8: Investigate implementing UTF-8 in the RIPE Database

We are working on a RIPE Labs article explaining the impact of this change.

DB-2021-#06 Deprecation of Whitepages

For more information, please refer to this document.

Whitepages are now deprecated.


Q4 2021 Plans and Community Input

Plans
Item Activity Description
1

Formulating a framework with the community to determine the level of crtiticality of each RIPE NCC service, including the RIPE Database.

Work continued in Q1 2022.

We will engage with the community to define requirements and plan on how to proceed concerning potential cloud migration and infrastructure improvements.

2 Usability improvements to the web search

Work continued in Q1 2022.

We are making improvements to the web search function of the RIPE Database.

You can find more details in our RIPE Labs article.

Community Input
Reference Input RIPE NCC Reaction
DB-2021-#01 NWI-2: Displaying history for database objects where available Our legal team is reviewing this request.
DB-2021-#02 NWI-4: role of status: field in multivalued status context Our team has investigated the tuple (prefix and status) proposal and have found it infeasible to implement. We are waiting on further community discussion on this topic.
DB-2021-#03 NWI-13: Geofeed

Implement Geofeed attribute in the RIPE Database. For more information, please read RFC 9092.

Our legal team is reviewing the restriction on prefix size.

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.
DB-2021-#05 UTF-8: Investigate implementing UTF-8 in the RIPE Database We are working on a RIPE Labs article explaining the impact of this change.
DB-2021-#06 Deprecation of Whitepages

For more information, please refer to this document.
We are waiting on community discussion on this topic.