<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">I've added the questions shown below. In the google doc, they're numbered 16-18. Copying them into this email renumbered them 1-3.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">My purpose in this note is to flag a couple of points related to points that have come up in earlier discussion.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">The first question emphasizes there are many different data elements, each of which may -- and most likely will -- have its own validation level. Moreover, for purposes of this question, the V2 level, operational validation, is understood to be the same as agreed upon contractual clause that's currently under discussion.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">The second question addresses the point that some registrars and registries may impose higher levels of validation than is required under the RA and RAA.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">The third question asks for clarification as to whether the validation level is disclosed to the requester whenever the data element is provided in a response. Among other things, this question speaks to Alan's concern that a registrar might do operational validation of, say, the phone number but not the email address, but then provide the email address and not the phone number in response to a request.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">Thanks,</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">Steve</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br><br><table style="border:none;border-collapse:collapse"><tbody><tr style="height:0pt"><td style="border-width:0.5pt;border-style:solid;border-color:rgb(0,0,0);vertical-align:top;padding:0pt 5.4pt;overflow:hidden"><ol style="margin-top:0px;margin-bottom:0px"><li dir="ltr" style="margin-left:15px;list-style-type:decimal;font-size:11pt;font-family:Calibri,sans-serif;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><p dir="ltr" role="presentation" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline">What are the accuracy requirements for *each* of the data elements collected by the registrar? If possible, use the four level scale of V0, V1, V2, V3. </span></p></li></ol><p dir="ltr" style="line-height:1.2;margin-left:18pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Calibri,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">V0 = No validation required.</span></p><p dir="ltr" style="line-height:1.2;margin-left:18pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Calibri,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">V1 = Syntactic validation</span></p><p dir="ltr" style="line-height:1.2;margin-left:18pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Calibri,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">V2 = Operational validation</span></p><p dir="ltr" style="line-height:1.2;margin-left:18pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Calibri,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">V3 = Identity validation</span></p><br><p dir="ltr" style="line-height:1.2;margin-left:18pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Calibri,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">The expected answer is</span></p><p dir="ltr" style="line-height:1.2;margin-left:18pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Calibri,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">V2 for phone and/or email</span></p><p dir="ltr" style="line-height:1.2;margin-left:18pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Calibri,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">V1 for country code</span></p><p dir="ltr" style="line-height:1.2;margin-left:18pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Calibri,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">V0 for all other data elements</span></p></td></tr><tr style="height:0pt"><td style="border-width:0.5pt;border-style:solid;border-color:rgb(0,0,0);vertical-align:top;padding:0pt 5.4pt;overflow:hidden"><ol start="2" style="margin-top:0px;margin-bottom:0px"><li dir="ltr" style="margin-left:15px;list-style-type:decimal;font-size:11pt;font-family:Calibri,sans-serif;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><p dir="ltr" role="presentation" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline">Are registries and/or registrars permitted to perform or impose a higher level of validation?</span></p></li></ol><br><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Calibri,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">The expected answer is yes, but the documentation is not explicit.</span></p></td></tr><tr style="height:0pt"><td style="border-width:0.5pt;border-style:solid;border-color:rgb(0,0,0);vertical-align:top;padding:0pt 5.4pt;overflow:hidden"><ol start="3" style="margin-top:0px;margin-bottom:0px"><li dir="ltr" style="margin-left:15px;list-style-type:decimal;font-size:11pt;font-family:Calibri,sans-serif;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><p dir="ltr" role="presentation" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline">Are registrars required to provide the validation level along with the data element in their responses, either as part of the response or in their documentation?</span></p></li></ol><br><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Calibri,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">The expected answer is no, but the answer should be yes.</span></p></td></tr></tbody></table></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 1, 2021 at 10:06 AM Roger D Carney via GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st@icann.org">gnso-accuracy-st@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Good Morning,</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 Melina. In regards to the text that you highlighted, for clarity, my statement was point in time (Oct 21 and Oct 26), not since.</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="gmail-m_1186038705781919003appendonsend"></div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_1186038705781919003divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> STROUNGI Melina <<a href="mailto:Melina.STROUNGI@ec.europa.eu" target="_blank">Melina.STROUNGI@ec.europa.eu</a>><br>
<b>Sent:</b> Wednesday, December 1, 2021 8:42 AM<br>
<b>To:</b> Roger D Carney <<a href="mailto:rcarney@godaddy.com" target="_blank">rcarney@godaddy.com</a>>; <a href="mailto:gnso-accuracy-st@icann.org" target="_blank">gnso-accuracy-st@icann.org</a> <<a href="mailto:gnso-accuracy-st@icann.org" target="_blank">gnso-accuracy-st@icann.org</a>><br>
<b>Subject:</b> RE: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition</font>
<div> </div>
</div>
<div lang="EN-US">
<table border="0" cellspacing="0" cellpadding="0" width="100%" align="left" style="border:0px;display:table;width:100%;table-layout:fixed;float:none">
<tbody>
<tr>
<td valign="middle" width="1px" bgcolor="#A6A6A6" cellpadding="7px 2px 7px 2px" style="padding:7px 2px;background-color:rgb(166,166,166)">
</td>
<td valign="middle" width="100%" bgcolor="#EAEAEA" cellpadding="7px 5px 7px 15px" color="#212121" style="width:100%;background-color:rgb(234,234,234);padding:7px 5px 7px 15px;font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;font-size:12px;font-weight:normal;color:rgb(33,33,33);text-align:left">
<div>You don't often get email from <a href="mailto:melina.stroungi@ec.europa.eu" target="_blank">melina.stroungi@ec.europa.eu</a>. <a href="http://aka.ms/LearnAboutSenderIdentification" target="_blank">
Learn why this is important</a></div>
</td>
<td valign="middle" align="left" width="75px" bgcolor="#EAEAEA" cellpadding="7px 5px 7px 5px" color="#212121" style="width:75px;background-color:rgb(234,234,234);padding:7px 5px;font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;font-size:12px;font-weight:normal;color:rgb(33,33,33);text-align:left">
</td>
</tr>
</tbody>
</table>
<div>
<div style="background-color:rgb(242,222,222);padding-left:0.5cm;border-left:5px solid rgb(185,74,72)">
<span style="font-size:11pt;line-height:16pt;font-family:Tahoma,Verdana,Segoe,sans-serif;color:rgb(185,74,72)">Caution:</span>
<span style="font-size:11pt;line-height:16pt;font-family:Tahoma,Verdana,Segoe,sans-serif;color:rgb(185,74,72)">
This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@.</span></div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
</p>
<div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Dear all,</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Unfortunately, I was away on sick leave and have not managed to hear the recordings; so apologies in advance if I have missed important updates.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Just a first reaction in relation to the point below (in highlight) that no one initially spoke in objection to the working definition; this is not entirely… accurate
</span><span style="font-size:11pt;font-family:Wingdings;color:rgb(31,73,125)">J</span><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> I recall I had made certain remarks on the basis of Michael’s proposed wording – some orally
and some inserted in the google doc. So I personally used Michael’s reworded construct as baseline.
</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I am not aware if Michael’s proposed wording was entirely dismissed during the last discussions where I was not present, but for sure I had expressed my objections at the initially
proposed ‘working definition/construct’ – for instance I had stressed we should also encompass any related purposes – not re-invent or amend current purposes but simply state what already exists.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I understand there is confusion from many of us – including myself – as to what is the current status/starting basis, but hopefully we can all discuss about it in our upcoming meeting.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Best regards,</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Melina</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"> GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st-bounces@icann.org" target="_blank">gnso-accuracy-st-bounces@icann.org</a>>
<b>On Behalf Of </b>Roger D Carney via GNSO-Accuracy-ST<br>
<b>Sent:</b> Wednesday, December 1, 2021 3:13 PM<br>
<b>To:</b> <a href="mailto:gnso-accuracy-st@icann.org" target="_blank">gnso-accuracy-st@icann.org</a><br>
<b>Subject:</b> Re: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition</span></p>
</div>
</div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
</p>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black">Good Morning, </span>
</p>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black">Thank you for your note Michael, but I think it may be a bit misleading and the RrSG does not (and did not) agree with the suggested updates to the current working definition of accuracy.</span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black">As you have reviewed the call on Nov 4th several times, you will have noted that I objected to these changes around the 1 hour and 11 minute point. Specifically, around adding any mention of identity
requirements as that is just not the case in our contract or policy. I believe the reference to ICANN's report/memo below in your email, leaves off some important language/context. First, this report provides information on how ICANN Compliance operates, it
does not add requirements (that is only done in contracts or Policy). Second, as I have mentioned several times, the mention of "identity" here does not (and cannot, see first point) add any requirements on the CP, it only states that ICANN Compliance may
ask for "...further information concerning their findings...", it does not ask or even suggest that the Registrar do anything more than what they have already done in their investigation.</span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black">The one item I do believe we agreed to was around the "affirmative response" idea. I don't have the specifics on this one but I think Sarah brought up support on adding language around that idea.</span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black">Additionally, as I (and others) have mentioned many times we did not provide a proposed definition we provided the current working definition. I understand that people may want to update/expand that
definition and I believe that is why the GNSO Council formed this Scoping Team. </span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black">I will also point to prior calls, like the Oct 21st call where this working definition was presented, and we had agreement from several SGs, staff and the Chair that this was the baseline definition
that we would work from moving forward. <span style="background:yellow">I will note that I saw no chat nor anyone speak in objection to this working definition</span>. I once again brought this point of agreement up during our ICANN session (36 min) and once
again I did not see or hear any objections to this being the baseline. Obviously, some minor tweaks would occur, but the suggested changes were not minor and adds responsibilities that just do not exist today.</span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black">To be clear the RrSG does not agree with the suggested updates to the working definition. </span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black">Thanks</span></p>
</div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black">Roger</span></p>
</div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
<div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
<div align="center" style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif;text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="gmail-m_1186038705781919003x_divRplyFwdMsg">
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:black">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:black"> GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st-bounces@icann.org" target="_blank">gnso-accuracy-st-bounces@icann.org</a>>
on behalf of Michael Palage <<a href="mailto:michael@palage.com" target="_blank">michael@palage.com</a>><br>
<b>Sent:</b> Tuesday, November 30, 2021 1:57 PM<br>
<b>To:</b> 'Lori Schulman' <<a href="mailto:lschulman@inta.org" target="_blank">lschulman@inta.org</a>>; 'Sarah Wyld' <<a href="mailto:swyld@tucows.com" target="_blank">swyld@tucows.com</a>>;
<a href="mailto:gnso-accuracy-st@icann.org" target="_blank">gnso-accuracy-st@icann.org</a> <<a href="mailto:gnso-accuracy-st@icann.org" target="_blank">gnso-accuracy-st@icann.org</a>><br>
<b>Subject:</b> Re: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition</span>
</p>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
</p>
</div>
</div>
<div>
<div style="border-top:none;border-right:none;border-bottom:none;border-left:4.5pt solid rgb(185,74,72);padding:0cm 0cm 0cm 14pt">
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif;background:rgb(242,222,222)">
<span style="font-size:11pt;font-family:Tahoma,sans-serif;color:rgb(185,74,72)">Caution:</span>
<span style="font-size:11pt;font-family:Tahoma,sans-serif;color:rgb(185,74,72)">This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@.</span></p>
</div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
</p>
<div>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Hello All,</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">As someone that watched the video recording twice allow me to recount the events of Nov 4<sup>th</sup>.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">In advance of the call there had been two “definitions” (contractual construction / explanations) put forth for consideration. One by the Registrars and the one put forward by myself.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">In an effort to reconcile these two definitions, I opted to mark-up the Registrar’s “definition”. The first change was replacing the phrase “shall strictly” with “is.” Specifically I cited to
Background Briefing Assignment #1 which stated in relevant part that:</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt 36pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:black">However, if the
<b>complaint is about identity</b> (e.g., the registrant is not who they say they are), Contractual Compliance may ask the registrar to provide further information. (emphasis added).</span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">After the group acknowledged that this excerpt from the ICANN briefing document showed a larger remit than just syntactical and operational accuracy, the “shall strictly” phrase was redlined and
replaced with ‘is.”. Alan Greenburg from ALAC tired to propose an alternative wording but the redline stayed as “is”.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">The next proposed redline was inspired largely by the following excerpt from the ICANN72 GAC communique which states in relevant part:</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt 36pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">The GAC gives particular importance to the verification, validation and correction of all registration data by registrars,
<b>and certain registries</b>, in line with their contractual obligations, and supports rigorous monitoring and enforcement of such</span></p>
<p style="margin:0cm 0cm 0.0001pt 36pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">contractual obligations by ICANN. (emphasis added)</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">These changes again were made with no substantive opposition from the group.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">As I have stated previously these agreed upon changes where lost when the document was exited at the end of the call. I have consulted with ICANN Org and they are unaware of how these changes
were lost. However, I believe the video clearly shows that the deletion was NOT an intentional act because no one spoke to the text being removed, it just disappeared. Please review the video for yourself, I have provided the time stamp to help make everyone’s
review easier.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Now if the RySG and RsSG are going to maintain their objection to the previous redline “definition” and instead advocate for the RrSG “definition” we will address this topic AFTER the we conclude
the questions to ICANN Org, but before we begin our GAP analysis.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">I do have a specific request for Marc, Beth and Sofie. During the next RySG call could you seek clarification from the RySG on whether Registries believe they have a right under their Registry
Agreement to verify the accuracy of data elements that they process as part of domain name registrations in their respective TLDs. Additionally, what steps if any does ICANN Compliance take in connection with Registry Audits regarding this verification as
I do believe it is relevant to our discussion here in this Working Group.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Listed below are a non-exhaustive list of Registry Operators that involve some level of accuracy /registrant vetting beyond just email and phone accuracy (syntactical and operational) as part
of their registry operations:</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<ol type="1" style="margin-bottom:0cm;margin-top:0cm">
<li style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">From the original 2001 proof of concept round, .AERO was one of the first TLD that required the process of registrant data prior to being able to obtain a gTLD domain name registration. If you
look at the current .AERO registration website you will see the following requirement:</span></li></ol>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt 36pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Obtain your .aero ID, prior to registration of your chosen domain name through a .aero authorised registrar, this unique validity process screens potential domain registrants thus ensuring the
integrity and the exclusivity of the .aero domain.</span></p>
<p style="margin:0cm 0cm 0.0001pt 36pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">See <a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Finformation.aero%2Fregistration__%3B!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOB-UAlJdR%24&data=04%7C01%7Crcarney%40godaddy.com%7Ce9663d4bb92848d46f1708d9b4d8d81e%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637739666993892481%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=bzqgllRezmIrWzGz%2BaZdiKoClFr0d53LVkdrM%2Fhusuc%3D&reserved=0" target="_blank">
https://information.aero/registration</a> and <a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Finformation.aero%2Fnode%2Fadd%2Frequest-aero-id__%3B!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOB3ITCJxE%24&data=04%7C01%7Crcarney%40godaddy.com%7Ce9663d4bb92848d46f1708d9b4d8d81e%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637739666993902474%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=2PEaEvgf7KpCcOk9IWI4FAmVzcMjYumHet5PpflaBmc%3D&reserved=0" target="_blank">
https://information.aero/node/add/request-aero-id</a> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<ol start="2" type="1" style="margin-bottom:0cm;margin-top:0cm">
<li style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">From the 2004 Sponsored round perhaps the best example was .XXX which made the following representations:</span></li></ol>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt 36pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">5.0 PREVENTING ABUSIVE REGISTRATIONS</span></p>
<p style="margin:0cm 0cm 0.0001pt 36pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt 36pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">The Registry will authenticate members of the Sponsored Community, as part of the name registration process. As part of this process, the Registry will validate contact information for the Registrant,
secure the Registrant’s affirmative consent to the Registry-Registrant Agreement, and issue unique Membership Credentials. The Membership Application Process must be completed before a domain name is permitted to resolve in the TLD.</span></p>
<p style="margin:0cm 0cm 0.0001pt 36pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">See <a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fwww.icmregistry.com%2Fabout%2Fpolicies%2Flaunch%2F*general_aval__%3BIw!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOB3TI9E9h%24&data=04%7C01%7Crcarney%40godaddy.com%7Ce9663d4bb92848d46f1708d9b4d8d81e%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637739666993912474%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=HRGvEwyPJkzltdcM3Z5Rs%2BflZTLlQkKe8QriVsqPnJQ%3D&reserved=0" target="_blank">
https://www.icmregistry.com/about/policies/launch/#general_aval</a></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<ol start="3" type="1" style="margin-bottom:0cm;margin-top:0cm">
<li style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">fTLD submitted an approved RSEP to ICANN for the processing of Registrant information prior to registration. The name of this RSEP is Dynamic Registration Verification and is available here, see
<a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fwww.icann.org%2Fen%2Fsystem%2Ffiles%2Ffiles%2Frsep-2017039-bank-et-al-request-11dec17-en.pdf__%3B!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOB4HLTjfN%24&data=04%7C01%7Crcarney%40godaddy.com%7Ce9663d4bb92848d46f1708d9b4d8d81e%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637739666993912474%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=X03pz69aKr4V9vus8QGSFJ5baNq09HVw2AkM8rcqvfw%3D&reserved=0" target="_blank">
https://www.icann.org/en/system/files/files/rsep-2017039-bank-et-al-request-11dec17-en.pdf</a> This webpage shows the information that fTLD collects from prospective registrants as part of their verification process, see
<a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fwww.register.bank%2Fget-started%2F__%3B!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOBx2kcBfH%24&data=04%7C01%7Crcarney%40godaddy.com%7Ce9663d4bb92848d46f1708d9b4d8d81e%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637739666993922455%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=opfKI3l0A1Cbh%2FHnFLdf8zC1Y2RQhKx27dtBg94BeEU%3D&reserved=0" target="_blank">
https://www.register.bank/get-started/</a></span></li></ol>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<ol start="4" type="1" style="margin-bottom:0cm;margin-top:0cm">
<li style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">NABP, the Registry Operator of .PHARMACY, has also vetted prospective registrants as part of its registration process, see
<a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fnabp.pharmacy%2Fprograms%2Faccreditations-inspections%2Fdotpharmacy%2F*apply__%3BIw!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOB2DdoXPP%24&data=04%7C01%7Crcarney%40godaddy.com%7Ce9663d4bb92848d46f1708d9b4d8d81e%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637739666993922455%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=aZMtBH2NyWg0H64IABVIqqDk9aLm5q1Pc8zSbYI37Ug%3D&reserved=0" target="_blank">
https://nabp.pharmacy/programs/accreditations-inspections/dotpharmacy/#apply</a></span></li></ol>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<ol start="5" type="1" style="margin-bottom:0cm;margin-top:0cm">
<li style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">In addition, every .BRAND Registry Operator has a requirement to limit registrations in that TLD to either the Brand owner or “Trademark Licensee” so this would be a further example of where a
Registry Operator is processing data about a Registrant (e.g. Trademark Licensee) that may or may not appear in the Whois/RDDS output.</span></li></ol>
<p style="margin:0cm 0cm 0.0001pt 36pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<ol start="6" type="1" style="margin-bottom:0cm;margin-top:0cm">
<li style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">There are also numerous RSEPs filed by Registry Operators seeking “Registration Validation” which clearly go above just syntactical and operational validation, e.g. Chinese Real Name Verification.</span></li></ol>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">I hope this removes any ambiguity as to the events of Nov 4<sup>th</sup>. If, however, the RySG and RrSG maintain their objection we will revisit prior to our GAP analysis discussion as noted
above.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Best regards,</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Michael</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"> Lori Schulman <<a href="mailto:lschulman@inta.org" target="_blank">lschulman@inta.org</a>>
<br>
<b>Sent:</b> Tuesday, November 30, 2021 1:06 PM<br>
<b>To:</b> Sarah Wyld <<a href="mailto:swyld@tucows.com" target="_blank">swyld@tucows.com</a>>; <a href="mailto:michael@palage.com" target="_blank">
michael@palage.com</a>; <a href="mailto:gnso-accuracy-st@icann.org" target="_blank">gnso-accuracy-st@icann.org</a><br>
<b>Subject:</b> RE: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition</span></p>
</div>
</div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Hi,</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">The changes were definitely tracked. I was under the impression that we agreed to those changes. If so, then they should be reinserted as a compromise that we can live with for the purposes of
the scoping exercise. Any binding definitions will be negotiated by the eventual PDP.
</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">With kind regards,</span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Lori S. Schulman</span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Senior Director, Internet Policy</span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">International Trademark Association (INTA)</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">+1-202-704-0408, Skype: LSSchulman</span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"><a href="mailto:lschulman@inta.org" target="_blank">lschulman@inta.org</a><span style="color:rgb(31,73,125)">,
</span><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Fwww.inta.org__%3B!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOBycMdrw5%24&data=04%7C01%7Crcarney%40godaddy.com%7Ce9663d4bb92848d46f1708d9b4d8d81e%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637739666993932451%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Fo%2FAqvfJvW%2BZDyJCMeLP%2BDSNM86v4D3Gao%2BmBH8S0MQ%3D&reserved=0" target="_blank">www.inta.org</a></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
</div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"> GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st-bounces@icann.org" target="_blank">gnso-accuracy-st-bounces@icann.org</a>>
<b>On Behalf Of </b>Sarah Wyld<br>
<b>Sent:</b> Monday, November 29, 2021 3:27 PM<br>
<b>To:</b> <a href="mailto:michael@palage.com" target="_blank">michael@palage.com</a>; <a href="mailto:gnso-accuracy-st@icann.org" target="_blank">
gnso-accuracy-st@icann.org</a><br>
<b>Subject:</b> Re: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition</span></p>
</div>
</div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif">Hi team,</span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif"> </span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif">I (of course) can’t speak for the registries or answer this question, but I do want to say, I’m glad the text in the screenshot was not updated. The definition in that section of
the document should remain as we had proposed it back on Oct 29, and any changes should be tracked elsewhere. Maybe that’s why the changes were removed?<br>
<br>
See you tomorrow, thanks! </span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif"> </span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif">Sarah</span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif"> </span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<pre style="margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:"Courier New""><span lang="EN-CA"> </span></pre>
<pre style="margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:"Courier New""><span lang="EN-CA"> </span></pre>
<pre style="margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:"Courier New""><span lang="EN-CA" style="font-family:Verdana,sans-serif">-- </span></pre>
<pre style="margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:"Courier New""><b><span lang="EN-CA" style="font-family:Verdana,sans-serif">Sarah Wyld</span></b><span lang="EN-CA" style="font-family:Verdana,sans-serif">, CIPP/E</span></pre>
<pre style="margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:"Courier New""><span lang="EN-CA" style="font-family:Verdana,sans-serif"> </span></pre>
<pre style="margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:"Courier New""><span lang="EN-CA" style="font-family:Verdana,sans-serif">Policy & Privacy Manager</span></pre>
<pre style="margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:"Courier New""><span lang="EN-CA" style="font-family:Verdana,sans-serif">Pronouns: she/they</span></pre>
<pre style="margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:"Courier New""><span lang="EN-CA" style="font-family:Verdana,sans-serif"> </span></pre>
<pre style="margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:"Courier New""><a href="mailto:swyld@tucows.com" target="_blank"><span lang="EN-CA" style="font-family:Verdana,sans-serif">swyld@tucows.com</span></a><span style="font-family:Verdana,sans-serif"> </span></pre>
<pre style="margin:0cm 0cm 0.0001pt;font-size:10pt;font-family:"Courier New""><span lang="EN-CA" style="font-family:Verdana,sans-serif">+1.416 535 0123 Ext. 1392</span></pre>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-size:10pt;font-family:"Courier New""> </span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif"><img border="0" width="100" height="23" id="gmail-m_1186038705781919003x_x_Picture_x0020_3" style="width: 1.0416in; height: 0.2395in;" src="cid:17d7690e0f75b16b21"></span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif"> </span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<b><span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif">From:
</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"><a href="mailto:michael@palage.com" target="_blank"><span lang="EN-CA">Michael Palage</span></a></span><span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif"><br>
<b>Sent: </b>November 26, 2021 12:02 PM<br>
<b>To: </b></span><span style="font-size:11pt;font-family:Calibri,sans-serif"><a href="mailto:gnso-accuracy-st@icann.org" target="_blank"><span lang="EN-CA">gnso-accuracy-st@icann.org</span></a></span><span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif"><br>
<b>Subject: </b>[GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition</span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
</div>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-size:11pt;font-family:Calibri,sans-serif"> </span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Hello All,</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">For those colleagues that celebrated the Thanksgiving holiday yesterday, I hope you had an enjoyable time with your family and friends and did not eat too much. I would also like to thanks those
team members that showed up for our brief Administrative Call yesterday.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">In preparing for the call yesterday I noted some of the new additions added by the RySG to the questions for ICANN staff. Thank you for these additions Roger. This flagged a previous issue which
I had raised with our ICANN colleagues last weekend and it involves the current working contractual construct / definition.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">In the RySG questions they cited to the proposed RrSG accuracy “definition” (aka contractual construct):</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">"Accuracy shall be strictly defined as syntactical accuracy of the registration data elements provided by the Registered Name Holder as well as the operational accuracy of either the telephone
number or the email address."</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Last week when I was looking for the latest and greatest contractual construct/definition I noted that there was a technical glitch when reviewing the Zoom recording which I will summarize below.</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">If you go to the Zoom recording from the Nov 4<sup>th</sup> call you will see that the red lined version of the contractual construct/definition which was agreed to during the call and which is
reflected below. </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif"><img border="0" width="802" height="465" id="gmail-m_1186038705781919003x_x__x005f_x0000_i1026" style="width: 8.3541in; height: 4.8437in;"></span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> However, at the conclusion of the call as we were wrapping up the session, these edits were lost
</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-family:Calibri,sans-serif"><img border="0" width="809" height="455" id="gmail-m_1186038705781919003x_x__x005f_x0000_i1025" style="width: 8.427in; height: 4.7395in;"></span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Therefore, I would like clarification from the RySG do they wish to cite the group’s current working contractual construct/definition that was agreed to during the Nov 4<sup>th</sup> call, or
do they intend to cite to the RrSG pre November 4<sup>th</sup> call contractual construct/definition?</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">I know these technical glitches, e.g. delta in Google Doc, Alan receiving emails, and the unavailability email archives makes things a little more challenging. However, I know our ICANN colleagues
are working on the email issues, and I am sure we will be able to achieve most of our work asynchronously if we put our minds to it.
</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Best regards,</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif">Michael</span></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman",serif">
<span lang="EN-CA" style="font-family:Calibri,sans-serif"> </span><span style="font-size:11pt;font-family:Calibri,sans-serif"></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</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://mm.icann.org/mailman/listinfo/gnso-accuracy-st" 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://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" 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>