[ripe-db-requirements-tf] Notes from 29 April 2021 Meeting

Dear all,

Here's the meeting notes from our last call.

Cheers,
Boris

*RIPE Requirements Database Task Force Meeting Notes*
29 April 2021 Meeting

Attendees: Nick Hilliard, James Kennedy, Shane Kerr, Peter Koch, Bijal Sanghani, Ed Shryane

Agenda:
1. PERSON Objects
The task force discussed how to deal with the great amount of PERSON objects stored in the RIPE Database and the problem it causes in terms of personal data. Ed mentioned that only a few LIRs are responsible for the creation of most of these objects. Bijal proposed to reach out to those LIRs and ask them why they are creating so many PERSON objects. Peter mentioned that it will be best to contact them via Ed on behalf of the task force. Ed agreed to contact these specific LIRs and to mention the task force in his email. In addition to this, Ed proposed to provide the task force with more statistics regarding PERSON and ROLE objects. He also mentioned that there are far more PERSON objects than ROLE objects in the RIPE Database.

Bijal mentioned that the task force should come up with a clear recommendation regarding how to deal with PERSON objects. The current recommendation is to make it harder for people to create PERSON objects by adding verification mechanisms. Ed added that this recommendation would be useful to slow down the creation of new objects but will not help to clean up old objects.

Peter mentioned that they could be personal data stored in both ROLE and PERSON objects and that even though it would help with data minimisation, it will not solve the concerns around personal data.

Nick shared that some of the data in the RIPE Database is being scraped for advertising purposes and that he and other LIRs were regularly receiving spam emails. Ed asked Nick to contact him directly, so that the RIPE NCC Database Team can look into this issue.

Nick added that it will be hard for the RIPE NCC to differentiate between a role address and a personal address.

Shane proposed to find a way to accelerate the clean-up of old PERSON objects by asking the RIPE NCC to step up its efforts in this area. Bijal proposed to first wait for the feedback of the LIRs creating the most PERSON objects.

The task force discussed how the move from PERSON to ROLE objects should be dealt with by the community. James mentioned that the task force’s recommendation should stay high level as engineering details are out of scope. He proposed to delegate this work to another body (WG or new task force). The task force agreed to discuss this recommendation at the upcoming BoF and wait to hear from the LIRs who are creating the most PERSON object before taking a decision on this topic.


2. rDNS
After agreeing that rDNS is a requirement of the RIPE Database, the task force decided that no recommendation was needed on this topic at this stage.

-------------- 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/20210512/c25e1b87/attachment.sig>