The RIPE Database Requirements Task Force

Rationale

The RIPE Database is now almost 30 years old [ripe-013].
During all this time, the community has developed the functionality of the Database incrementally. Today some new frictions have emerged such as changing privacy requirements and the use of the RIPE Database by parties outside the traditional community, specifically law enforcement. Because of these frictions and changing needs, the community consensus about the functionality of the RIPE Database has become less obvious. Therefore it is now time to take stock and to establish a clear consensus about what functionality the RIPE Database should provide in the future.

Charter

The RIPE Database Requirements Task Force shall develop a RIPE document listing all the requirements for the RIPE Database and their rationales. The task force is a small and focused drafting team of up to six persons and not a representative body. The task force will consult the RIPE community and other interested parties. Consensus building will take place in the appropriate RIPE working groups and possibly specific BoFs. The task force will regularly publish draft versions of the document.

Document Scope

The purpose of the document is to establish community consensus at the general level. The document will be the new requirements specification for the RIPE Database. It shall provide clear guidance for the evolution of RIPE Database functionality, including the removal of current functionality that is no longer required.

The document will prioritise requirements as much as possible. The document shall list the purpose of each RIPE Database function and consider the relevant privacy aspects, making the document useful in the context of privacy regulations such as GDPR. The document shall allow easy updates as community needs change.

Software development, deployment and other implementation details are out of scope. Despite being scoped as a requirements document, the document shall not prescribe a specific engineering methodology for subsequent steps in the process.

Methodology

The RIPE Chair shall appoint the task force after a call for volunteers. Volunteers are expected to contribute significant amounts of text and to collect community feedback. The task force will regularly publish revised drafts based on this feedback. The task force may conduct BoF sessions to discuss drafts with the community.

Final Report

The task force published its final report ahead of RIPE 83.

Draft Reports

• First draft (May 2020)
• Second draft (October 2020)
• Third draft (July 2021)

Timeline*

The task force will start its work at [RIPE 79] and produce the first draft document for community discussion before RIPE 80. After RIPE 81, the task force will incorporate feedback gathered from all user groups and will deliver a document for last-call. If the community does not achieve consensus, the task force will give a report listing the open issues and propose a plan to resolve them no later than RIPE 83. 

*Timeline updated May 2021 in consultation with RIPE Chair.

BoFs

On 6 May 2020, the RIPE Database Requirements Task Force held its first BoF session. The minutes and recording of the session are available online. 

On 26 October 2020, the task force held its second BoF as part of RIPE 81. The recording is available online.

On 5 May 2021, the task force held its third BoF. The minutes and recording of the session are available online.

Task Force Members

• Peter Koch
• Shane Kerr (Vice Chair)
• Nick Hilliard
• Bijal Sanghani (Chair)
• Sara Marcolla (left the task force in February 2021)
• James Kennedy (co-Chair)

RIPE NCC Staff Support

• Boris Duval
• Maria Stafyla
• Edward Shryane

Mailing List Archives

Emails to the RIPE Database Requirement Task Force mailing list are publicly archived.