[ripe-db-requirements-tf] Notes from 7 June 2021 Meeting

Dear all,

Here's the meeting notes from our last call.

Cheers,
Boris

*RIPE Requirements Database Task Force Meeting Notes*
7 June 2021 Meeting

Attendees: Boris Duval, Nick Hilliard, Shane Kerr, James Kennedy, Peter Koch, Bijal Sanghani, Ed Shryane, Maria Stafyla

1. Draft Document
A)  Data Management Principles
The task force agreed on four leading principles for the management of data in the RIPE Database:
-- Data accuracy
-- Data minimization
-- Data consistency
-- Data security

Nick suggested to add that all data stored in the RIPE Database should have a clearly defined purpose.
Boris and Maria said that it could fall under the Data Minimisation principle and proposed to edit the current text.

A) Document Structure
The task force reviewed a new document structure based on Daniel Karrenberg’s remarks. The new structure includes a clear separation between Purposes, Requirements and Recommendations. For each requirement, there is also information about the current status quo and the rationale that led to the recommendation. The task force also suggested to add another category called “other consideration” for requirements that were considered but not included as such in the document.

B)  Legal Address
The task force agreed on recommending to explore alternatives to publishing the legal address of RIPE NCC Members and End Users.

C)  PERSON Objects
The task force agreed to recommend the implementation of stricter checks and measures to limit the creation of PERSON objects and to encourage the creation of ROLE objects instead. Ed received feedback from one of the top 10 members with the most PERSON objects. He shared that this member is referencing most of its PERSON objects from assignments (with consent from users), hence the huge number of objects created. James commented that it looks like they are using the RIPE Database as their IPAM solution.

D)  IPv4 PA Assignment
The task force reviewed James’s recommendation regarding IPv4 assignment. This recommendation was presented during the AP-WG at RIPE 82. The task force agreed to include the following recommendation: “The task force recommends that as resource holders have full responsibility over their IPv4 PA assignment(s), they are free to make assignments or not. This means that IPv4 PA assignment(s) will stop being a policy requirement.” The task force also considered adding a disclaimer regarding previous assignments, as the intention of the task force is not to delete past assignments.

E)  Historical Data
The task force agreed to add historical data as a requirement of the RIPE Database and to further limit personal data exposure in historical queries. Shane will follow up with Erik Bais and Daniel Karrenberg to collect use cases related to historical data usage.


2. Publication of an intermediate draft
The task force agreed to publish an intermediate draft at the end of June to give the community an overview of its current work and get feedback.


3. Next Meeting
The next DBTF meeting will take place on 21 June 2021.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: </ripe/mail/archives/ripe-db-requirements-tf/attachments/20210614/a7e492a8/attachment.sig>