Archived Plans

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.

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.

Working on server-side implementation.

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.

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.

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

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.

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.

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.

This work item was not included in the initial planning. 

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

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.

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.

Proposed Solution Definition to DB-WG, based on draft NRTM v4 proposal by Sasha Romijn.

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.

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.

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.

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.

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.

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.

Completed

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

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.

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.

Our legal team is reviewing this request.

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.

Our legal team is reviewing the restriction on prefix size.

Proposed Solution Definition to DB-WG, based on draft NRTM v4 proposal by Sasha Romijn.

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

Whitepages are now deprecated.

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.

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.

Our legal team is reviewing the restriction on prefix size.