<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8"> </head> <body><div style="font-family: sans-serif;"><div class="plaintext" style="white-space: normal;"><p dir="auto">Hello Harri,</p> <p dir="auto">Thanks for raising this. I am not too familiar with all the arguments for enforcing a matching public legal name, and the impact of a masking option. I think this also refers to a specific set of fields, particularly the org-name on an organisation holding resources?</p> <p dir="auto">It sounds at least like the NCC needs to improve process for individual name changes. It is insensitive to deny a person the use of their own name, and sounds like a possible violation of the GDPR right to rectification. I did at some point change legal name, at a time when I had no RIPE resources, and found some success in referring to that article when organisations were difficult.</p> <p dir="auto">Sasha</p> <br><p dir="auto">On 3 Dec 2023, at 12:49, Harry Cross via db-wg wrote:</p> </div><blockquote class="embedded" style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #5855D5; color: #5855D5;"><div id="89FF2A31-484C-48FE-8592-16C13BC3CB46"> <div dir="ltr"> <div dir="ltr">Dear all (copying this to both the Diversity list and the Database list),</div> <div dir="ltr">I hope you’re having a wonderful weekend and recovering from Rome. </div> <div dir="ltr"><br></div> <div dir="ltr">I’d like to begin thinking about a proposal for preferred names in the database/on resources. Some may have noticed this week (and for a bit prior), I have begun going by Harri instead of Harry. At the moment there is no correct way for me to represent this in the database, as an LIR the details have to match my legal name. I may think about going through the legal processes to change this soon (albeit in the UK this is easier than a lot of places).</div> <div dir="ltr"><span style="font-size: inherit;"><br></span></div> <div dir="ltr"><span style="font-size: inherit;">I know a few people hold their resources under a shell company for this purpose, (e.g I could incorporate Harri Cross Limited to hold the resources and be in the database). This applies to end users who hold PI or ASNs alongside LIRs.<br></span></div> <div dir="ltr"><span style="font-size: inherit;"><br></span></div> <div dir="ltr"><span style="font-size: inherit;">It would be good for us to think about a way for these preferred names (and pronouns?) to be shown in the database alongside the process for changing the name of an end user. I know the preferred way a lot of people in this situation would like this to be handled is to totally mask the legal name in the database. The NCC could still validate legal names to know who they are working with - and we will need some compromise here I suspect. A complete lack of verification is of course a bad thing. </span><br></div> <div dir="ltr"><br></div> <div dir="ltr">I have experienced talking to the NCC when handling end users in these situations who have legally name changed and the process seems to be incredibly hard with the lack of understanding on documentation for name changes. </div> <div dir="ltr"><br></div> <div dir="ltr">Responses from the Registry have included “How can we be sure that <oldName> and <newName> are not identical twins?” (Which in my mind, is rather disrespectful). I also have another name change in process that is being stonewalled by a lack of understanding of documents in different jurisdictions for this.</div> <div dir="ltr"><br></div> <div dir="ltr">Kind Regards,</div> <div dir="ltr"><br></div> <div dir="ltr">Harri</div> <div dir="ltr"><br></div> <div id="ms-outlook-mobile-signature">Sent from <a href="https://aka.ms/o0ukef">Outlook for iOS</a></div> </div></div></blockquote> <div class="plaintext" style="white-space: normal;"> <blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #5855D5; color: #5855D5;"><p dir="auto">-- </p> <p dir="auto">To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://lists.ripe.net/mailman/listinfo/db-wg">https://lists.ripe.net/mailman/listinfo/db-wg</a></p> </blockquote></div> </div> </body> </html>