Skip to main content

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.

Q4 2023 Plans and Community Input

Plans
Item Activity Description
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.

2 Open Source Web Application

As announced at RIPE 85, we will publish the source code to our web application.

We are currently setting up a security audit and expect to have this activity completed by RIPE 87.

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

DB-WG to define requirements for NWI-2.

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 using the inetnum-status tuple as primary key.

We first recorded this request in Q4 2021.

DB-2021-#03 NWI-13: Geofeed

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

Completed in Q4 2023

Geolocation is now a purpose of the RIPE database.

DB-2023-#01

NWI-12: NRTMv4

More information can be found on GitHub.

Server-side implementation is complete. We are now collaborating on the client-side implementation.

Q3 2023 Plans and Community Input

Plans
Item Activity Description
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.

2 Open Source Web Application

As announced at RIPE 85, we will publish the source code to our web application.

We are currently setting up a security audit and expect to have this activity completed by RIPE 87.

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.

The team is preparing an impact analysis.

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

Q2 2023 Plans and Community Input

Plans
Item Activity Description
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.

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.

3 NWI-12: NRTMv4

Working on server-side implementation.

4 Open Source Web Application

As announced at RIPE 85, we will publish the source code to our web application.

5 Open Full Text Search API

As previously announced, we will open the Full Text Search API to end users.

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.

The team is preparing an impact analysis.

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

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

Q1 2023 Plans and Community Input

Plans
Item Activity Description
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.

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.

3 NWI-12: NRTMv4

Working on server-side implementation.

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.

The team is preparing an impact analysis.

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

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

Q4 2022 Plans and Community Input

Plans
Item Activity Description
1

RDAP profile

Work was completed in Q4 2022.

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.

2

Database documentation

Work started in Q3 2022.

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.

3

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

Work started in Q4 2021.

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.

4 NWI-10: Definition of country

This work item was not included in the initial planning. 

Populate the legal country for all End User organisations with resources.

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.

The team is preparing an impact analysis.

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

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.

Q3 2022 Plans and Community Input

Plans
Item Activity Description
1

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

Work started in Q4 2021 and continues in Q4 2022.

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

2 Database documentation

Work started in Q3 2022 and continues in Q4 2022.

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.

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.

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 started in Q4 2021 and continues in Q4 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 started in Q4 2021 and continues in Q4 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 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

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 criticality of each RIPE NCC service, including the RIPE Database.

Work started in Q4 2021 and continues in Q4 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 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 We are waiting on community discussion on this topic.