[ripe-db-requirements-tf] Notes from 26 March 2021 Meeting
- Next message (by thread): [ripe-db-requirements-tf] Notes from 12 April 2021 Meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Boris Duval
bduval at ripe.net
Wed Apr 7 13:34:55 CEST 2021
Dear all, Here's the meeting notes from our last call. *RIPE Requirements Database Task Force Meeting Notes* 26 March 2021 Meeting Attendees: Boris Duval, Nick Hilliard, James Kennedy, Shane Kerr, Peter Koch, Bijal Sanghani, Maria Stafyla Agenda: 1. DBTF questionnaire review and next steps Maintaining an authoritative and accurate registry of Internet number resources C) Resources Registration Requirements The task force agreed on the following recommendation: “As resource holders have full responsibility over their allocation(s), they are free to make assignments or not. However, if a resource holder wants to sub-assign part of their resources to another entity, the task force strongly recommends to document this change in the RIPE Database. Parallel to that, making assignments should not be a prerequisite to get new Internet number resources.” Peter and Nick pointed out that it will be good to add data minimisation as part of the general data management principles in the draft. D) Historical Information The DBTF will wait for the BoF before taking a decision on how to deal with historical information. The main issue revolves around personal data being stored in historical information. Ed will check if it is technically possible to apply more filtering in order to minimise the risk of having returned personal data in historical queries. Facilitating Internet operations and coordination A) PERSON Objects The task force considered to keep PERSON objects but make it harder to create them by adding a disclaimer about personal data. This will help decrease the amount of unmaintained personal data. The task force will come up with a recommendation on this topic and will bring it for discussion at the BoF. 2. Document Structure Nick proposed to have two documents instead of one. One document with general principles (similar to the current draft) and one document with all recommendations and suggestions from the task force. The task force liked the idea and will discuss it further. 3. BoF Planning After reviewing the original timeline, the task force decided to organise a BoF early May. 4. Next meeting The next meeting will take place in April. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-db-requirements-tf/attachments/20210407/0f085482/attachment.html> -------------- 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/20210407/0f085482/attachment.sig>
- Next message (by thread): [ripe-db-requirements-tf] Notes from 12 April 2021 Meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]