<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Dear all,</div><div class=""><div style="caret-color: rgba(0, 0, 0, 0.847); color: rgba(0, 0, 0, 0.847); font-family: -apple-system-font;" class=""><div class=""><font color="#000000" face="Helvetica" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class=""></span></font></div><div class=""><font color="#000000" face="Helvetica" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Here's the meeting notes from our last call.</span></font></div></div><div class=""><br class=""></div><font color="#000000" face="Helvetica" class="">*RIPE Requirements Database Task Force Meeting Notes*</font><br class="">26 March 2021 Meeting<br class=""><br class="">Attendees: Boris Duval, Nick Hilliard, James Kennedy, Shane Kerr, Peter Koch, Bijal Sanghani, Maria Stafyla<br class=""><br class="">Agenda:<br class="">1. DBTF questionnaire review and next steps<br class=""><br class="">Maintaining an authoritative and accurate registry of Internet number resources<br class=""><br class="">C) Resources Registration Requirements<br class="">The task force agreed on the following recommendation:<br class="">“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.”<br class=""><br class="">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. <br class=""><br class="">D) Historical Information<br class="">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 <font color="#000000" face="Helvetica" class="">filtering in order to minimise the risk of having returned personal data </font>in historical queries.</div><div class=""><br class="">Facilitating Internet operations and coordination<br class=""><br class="">A) PERSON Objects<br class="">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.<br class=""><br class=""><br class="">2. Document Structure<br class="">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.<br class=""><br class=""><br class="">3. BoF Planning<br class="">After reviewing the original timeline, the task force decided to organise a BoF early May. <br class=""><br class=""><br class="">4. Next meeting<br class="">The next meeting will take place in April.</div><div class=""><br class=""></div></body></html>