<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> I should always double check the text before sending. this: "I'm not sure which policy proposal should be updated" should read "I'm not sure which policy should be updated" /elvis <div class="moz-cite-prefix">On 2/22/19 13:14, Elvis Daniel Velea wrote: </div> <blockquote type="cite" cite="mid:33ea2b53-a6fb-110f-f352-a4fc882d9a21@velea.eu"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> Hey Hans, thanks for following up on this. Before we start working on this, is a policy proposal really needed? I'm not sure which policy proposal should be updated. I would be happy to make a policy proposal - I will need your help or Marco's. @Denis - do you want to co-author? Elvis <div class="moz-cite-prefix">On 2/22/19 06:40, Hans Petter Holen via db-wg wrote: </div> <blockquote type="cite" cite="mid:CAJPAtr1VL52mfz=0Q2s7Vp714bLw+BYJpk6yJ-H-wbEEkBtUZg@mail.gmail.com"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <div dir="ltr"> Following Denis’s presentation at the last database working group meeting and Elvis’s messages to the RIPE NCC members list I think it is time to have a new discussion on the need for personal objects in the RIPE Database. <a href="https://ripe77.ripe.net/presentations/63-PERSONobjects.pdf" style="text-decoration-line:none" moz-do-not-send="true"><span style="font-size:11pt;font-family:Arial;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;text-decoration-line:underline;vertical-align:baseline;white-space:pre-wrap">https://ripe77.ripe.net/presentations/63-PERSONobjects.pdf</a> <a href="https://ripe77.ripe.net/archives/video/2298/" style="text-decoration-line:none" moz-do-not-send="true"><span style="font-size:11pt;font-family:Arial;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;text-decoration-line:underline;vertical-align:baseline;white-space:pre-wrap">https://ripe77.ripe.net/archives/video/2298/</a> <a href="https://www.ripe.net/ripe/mail/archives/members-discuss/2019-February/003295.html" style="text-decoration-line:none" moz-do-not-send="true"><span style="font-size:11pt;font-family:Arial;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;text-decoration-line:underline;vertical-align:baseline;white-space:pre-wrap">https://www.ripe.net/ripe/mail/archives/members-discuss/2019-February/003295.html</a> This is not questioning previous legal assessments of GDPR compliance, but taking a step back and looking at how would we do this if we were to design the RIPE Database with today's privacy requirements in mind. The ccTLD for .NO, Norid made an update to their service last year to completely remove person objects from their database. <a href="https://www.norid.no/uploads/2017/12/Datamodell-revidert-en-v2.pdf" style="text-decoration-line:none" moz-do-not-send="true"><span style="font-size:11pt;font-family:Arial;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;text-decoration-line:underline;vertical-align:baseline;white-space:pre-wrap">https://www.norid.no/uploads/2017/12/Datamodell-revidert-en-v2.pdf</a> In terms of the RIPE Database, that would mean that resources would refer to organisational objects and roles, not to personal objects. Perhaps Denis and/or Elvis would propose a policy change in this respect? Hans Petter </div> </blockquote> </blockquote> </body> </html>