<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Good Afternoon,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">This ICANN compliance enforcement process </span><span style="color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">does not assign
identity verification responsibility to the Registrar, it only stipulates that ICANN (when considering an identity complaint) may request the Registrar to "...provide further information concerning their findings and the results of their investigation...".
This is not asking for more work to be done, just more data on what has already been done by the registrar.</span><span style="color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;"> If a Registrar does do identity verification
like Volker suggests, that is above and beyond what is required and is not part of accuracy as it is defined today.</span><br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Roger</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> on behalf of Volker Greimann <volker.greimann@centralnic.com><br>
<b>Sent:</b> Friday, October 22, 2021 6:18 AM<br>
<b>To:</b> michael@palage.com <michael@palage.com><br>
<b>Cc:</b> gnso-accuracy-st@icann.org <gnso-accuracy-st@icann.org><br>
<b>Subject:</b> Re: [GNSO-Accuracy-ST] Identity Proofing Clarity - Follow Up Homework</font>
<div> </div>
</div>
<div>
<div>
<div dir="ltr">
<div>Hi Michael,</div>
<div><br>
</div>
<div>all such investigations are based on a substantiated whois inaccuracy complaint where the complainant states that the registrant has provided false details. As this regards a potential violation of our registration agreement with the registrant we will
investigate the identity of the registrant in this specific case only. The usual complaint is from the party listed in the registration record that they did not register the domain name in the first place or sold it a while ago and now found that the record
was never updated by the old registrant. <br>
</div>
<div><br>
</div>
<div>That said, aside from the investigation following a substantiated inaccuracy complaint, identity of the registrant is not required under current policies. These cases are rather rare and are usually detected when the listed registrant contact receives
their annual WDRP mail. In these cases we contact our customer and ask that they reach out to the registrant with the request to update the registration details.
<br>
</div>
<div><br>
</div>
<div>Sincerely,<br>
</div>
<div>
<div>
<div dir="ltr" class="x_gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr"><span lang="EN-US">-- <br>
Volker A. Greimann<br>
General Counsel and Policy Manager<br>
<b>KEY-SYSTEMS GMBH</b><br>
<br>
T: +49 6894 9396901<br>
M: +49 6894 9396851<br>
F: +49 6894 9396851<br>
W: </span><a href="https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.key-systems.net%2F&data=04%7C01%7Crcarney%40godaddy.com%7C39658ab1f5b7471cf59108d9954dcea5%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637704984430875349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=pHrw4CLOqNkpfSVZfKMuoPJ4sY9X893u9QcNOGz%2FMHk%3D&reserved=0" originalsrc="http://www.key-systems.net/" shash="Wc1OSurUL8y/yVB4IKibI+R7qIpT99V5XsXsKohCUnr127RW82SsIs+BhwPGbX8JE2vBfU9RnT5AZX6K8cxXbGpBMu+40yJaJJoC/NuOJ+WlK5whq4MVefmYPaUBQjt0gc/pCM49Tj4CFpjiPVb7FKDWUPUHYNU6yLakmfDdjP0=" target="_blank" style="color:rgb(17,85,204)"><span lang="EN-US">www.key-systems.net</span></a><span lang="EN-US"><br>
<br>
Key-Systems GmbH is a company registered at the local court of Saarbruecken, Germany with the registration no. HR B 18835<br>
CEO: Oliver Fries and Robert Birkner<br>
<br>
Part of the CentralNic Group PLC (LON: CNIC) a company registered in England and Wales with company number 8576358.<br>
<br>
</span><span style="font-family:Roboto,sans-serif; font-size:14px; white-space:pre-wrap; background-color:rgb(248,249,250)">This email and any files transmitted are confidential and intended only for the person(s) directly addressed. If you are not the intended
recipient, any use, copying, transmission, distribution, or other forms of dissemination is strictly prohibited. If you have received this email in error, please notify the sender immediately and permanently delete this email with any files that may be attached.</span></div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
<br>
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Fri, Oct 22, 2021 at 12:39 PM Michael Palage <<a href="mailto:michael@palage.com">michael@palage.com</a>> wrote:<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
<div lang="EN-US" style="">
<div class="x_gmail-m_-5186636878310832454WordSection1">
<p class="x_MsoNormal">Hello All,<u></u><u></u></p>
<p class="x_MsoNormal"><u></u> <u></u></p>
<p class="x_MsoNormal">I was reviewing my notes from yesterday’s meeting as well as reviewing some of the previous email list exchanges between and I was hoping that my Registrar colleagues could provide a little clarity, especially Volker given his participation
in the 2013 RAA negotiations.<u></u><u></u></p>
<p class="x_MsoNormal">
<u></u><u></u></p>
<p class="x_MsoNormal">I believe what I have heard and read from my Registrar colleagues is that there is no “identity proofing” requirements in their contracts – accuracy is merely syntactical and operational. I apologizes in advance if I am mischaracterizing
this and welcome any corrections. However, in Assignment #1, the follow excerpt from ICANN Organization Enforcement of Registration Data Accuracy Obligations Before and After GDPR states:<u></u><u></u></p>
<p class="x_MsoNormal"><u></u> <u></u></p>
<p class="x_MsoNormal"><span style="color:black">[I]f the complaint is about identity (e.g., the registrant is not who they say they are), Contractual Compliance may ask the registrar to provide further information concerning their findings and the results
of their investigation specific to the facts of the complaint.<u></u><u></u></span></p>
<p class="x_MsoNormal"><span style="color:black"><u></u> <u></u></span></p>
<p class="x_MsoNormal"><span style="color:black">So it appears based on this excerpt that ICANN Contractual Compliance does reserve some right to inquiry about the “identity” of the Registrant. Therefore, I believe potential clarifying questions to ICANN Org
could might include: does ICANN Compliance believe that it has the ability to inquiry about the “identity” of a registrant? If so, what is the contractual basis of this authority. Finally, what are the numbers associated with these types of inquiries, e.g.
percentage of overall accuracy complaints and raw numbers.<u></u><u></u></span></p>
<p class="x_MsoNormal"><span style="color:black"><u></u> <u></u></span></p>
<p class="x_MsoNormal"><span style="color:black">Thoughts? Comments?<u></u><u></u></span></p>
<p class="x_MsoNormal"><span style="color:black"><u></u> <u></u></span></p>
<p class="x_MsoNormal"><span style="color:black">Best regards,<u></u><u></u></span></p>
<p class="x_MsoNormal"><span style="color:black"><u></u> <u></u></span></p>
<p class="x_MsoNormal"><span style="color:black">Michael</span><u></u><u></u></p>
<p class="x_MsoNormal"><u></u> <u></u></p>
<p class="x_MsoNormal"><u></u><u></u></p>
<p class="x_MsoNormal"><u></u> <u></u></p>
<p class="x_MsoNormal"><u></u> <u></u></p>
<p class="x_MsoNormal"><u></u> <u></u></p>
<p class="x_MsoNormal"><u></u> <u></u></p>
<p class="x_MsoNormal"><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
GNSO-Accuracy-ST mailing list<br>
<a href="mailto:GNSO-Accuracy-ST@icann.org" target="_blank">GNSO-Accuracy-ST@icann.org</a><br>
<a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fgnso-accuracy-st&data=04%7C01%7Crcarney%40godaddy.com%7C39658ab1f5b7471cf59108d9954dcea5%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637704984430885348%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YUaSIpJqu3TKV9jmT9rMREIxAOWIpMp4OB%2FVyfo2e6M%3D&reserved=0" originalsrc="https://mm.icann.org/mailman/listinfo/gnso-accuracy-st" shash="Bf1KgOOKyicg6dGJiBqEh7Ako07cx5Vwnx/9/ou3vqiqkoO4K89zHvJ+RVY6CKOrbGQSuKBlJK2pcOsdwJAfl462TxTWr6nkUioM1hCB9J6Ll9zM7ooqonZEM5LQ/Kb/xvFBjS86c1HAhF/miaOBwjWAF6cxyi9xpZi0KAxkzpQ=" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-accuracy-st</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fprivacy%2Fpolicy&data=04%7C01%7Crcarney%40godaddy.com%7C39658ab1f5b7471cf59108d9954dcea5%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637704984430895335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1D6PJTyexx1jqrIf3TWyUSRI0wAlPcvYJTjYXegL4ds%3D&reserved=0" originalsrc="https://www.icann.org/privacy/policy" shash="nSxV0tXi9KcYkvU5lN+q2XYAHV17cnv7S1W5ktWibV0swzBZ0C9mXISfTEQjeuG7XH7nnGlb0pT98nZ3gDoUQtqPFlD96jjYBHPepweGkVUHJV/KU8wBOzv9t26eiRFfWrMWPhpm0FACjwVrloWcH3DcCEdLhdgViTokJ7Eefao=" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fprivacy%2Ftos&data=04%7C01%7Crcarney%40godaddy.com%7C39658ab1f5b7471cf59108d9954dcea5%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637704984430895335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Q0ahadxRLFsTcttb%2F6oFUwM%2Fszxll%2FTeEcJyXiDbXtU%3D&reserved=0" originalsrc="https://www.icann.org/privacy/tos" shash="HDz2vsX9NON0HzH/K8thGC3/Q7rAyohSnFTpIPHZHeSebB4J92bMcjoNf+04E10znjrVhmEton5LSxTgmSOrzJJ9w3IWIrFmL7TmYvEhEke5MC/PhHmSPZaRgkt1ARWNB5/lnJ6469C3Ie0+kAobs/6ow8tpveXnFeY/Mn/T3UU=" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>).
You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>