<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.xmsolistparagraph, li.xmsolistparagraph, div.xmsolistparagraph
{mso-style-name:x_msolistparagraph;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:401684063;
mso-list-template-ids:588661808;}
@list l0:level1
{mso-level-start-at:2;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:599459917;
mso-list-template-ids:788797114;}
@list l2
{mso-list-id:912423865;
mso-list-template-ids:1822951700;}
@list l2:level1
{mso-level-start-at:3;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l3
{mso-list-id:1069619983;
mso-list-template-ids:1821302884;}
@list l3:level1
{mso-level-start-at:4;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l4
{mso-list-id:1360351948;
mso-list-template-ids:1085671210;}
@list l4:level1
{mso-level-start-at:6;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l5
{mso-list-id:2120560498;
mso-list-template-ids:-651661442;}
@list l5:level1
{mso-level-start-at:5;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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:11.0pt;font-family:Wingdings;color:#1F497D">J</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> 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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Melina<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org>
<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> gnso-accuracy-st@icann.org<br>
<b>Subject:</b> Re: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Good Morning,
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><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. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><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;mso-highlight: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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><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. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Thanks<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Roger<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st-bounces@icann.org">gnso-accuracy-st-bounces@icann.org</a>>
on behalf of Michael Palage <<a href="mailto:michael@palage.com">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">lschulman@inta.org</a>>; 'Sarah Wyld' <<a href="mailto:swyld@tucows.com">swyld@tucows.com</a>>;
<a href="mailto:gnso-accuracy-st@icann.org">gnso-accuracy-st@icann.org</a> <<a href="mailto:gnso-accuracy-st@icann.org">gnso-accuracy-st@icann.org</a>><br>
<b>Subject:</b> Re: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div style="border:none;border-left:solid #B94A48 4.5pt;padding:0cm 0cm 0cm 14.0pt">
<p class="MsoNormal" style="background:#F2DEDE"><span style="font-size:11.0pt;font-family:"Tahoma",sans-serif;color:#B94A48">Caution:</span>
<span style="font-size:11.0pt;font-family:"Tahoma",sans-serif;color:#B94A48">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><o:p></o:p></p>
</div>
<p> <o:p></o:p></p>
<div>
<div>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hello All,<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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>.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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:<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;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:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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”.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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:<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;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<o:p></o:p></span></p>
<p class="xmsonormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">contractual obligations by ICANN. (emphasis added)<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">These changes again were made with no substantive opposition from the group.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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:<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo1"><span style="font-size:11.0pt;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:<o:p></o:p></span></li></ol>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;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.<o:p></o:p></span></p>
<p class="xmsonormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">See
<a href="https://urldefense.com/v3/__https:/information.aero/registration__;!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOB-UAlJdR$">
https://information.aero/registration</a> and <a href="https://urldefense.com/v3/__https:/information.aero/node/add/request-aero-id__;!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOB3ITCJxE$">
https://information.aero/node/add/request-aero-id</a> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<ol style="margin-top:0cm" start="2" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From the 2004 Sponsored round perhaps the best example was .XXX which made the following representations:<o:p></o:p></span></li></ol>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">5.0 PREVENTING ABUSIVE REGISTRATIONS<o:p></o:p></span></p>
<p class="xmsonormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;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.<o:p></o:p></span></p>
<p class="xmsonormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">See
<a href="https://urldefense.com/v3/__https:/www.icmregistry.com/about/policies/launch/*general_aval__;Iw!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOB3TI9E9h$">
https://www.icmregistry.com/about/policies/launch/#general_aval</a><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<ol style="margin-top:0cm" start="3" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;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://urldefense.com/v3/__https:/www.icann.org/en/system/files/files/rsep-2017039-bank-et-al-request-11dec17-en.pdf__;!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOB4HLTjfN$">
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://urldefense.com/v3/__https:/www.register.bank/get-started/__;!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOBx2kcBfH$">
https://www.register.bank/get-started/</a><o:p></o:p></span></li></ol>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<ol style="margin-top:0cm" start="4" type="1">
<li class="MsoNormal" style="mso-list:l3 level1 lfo4"><span style="font-size:11.0pt;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://urldefense.com/v3/__https:/nabp.pharmacy/programs/accreditations-inspections/dotpharmacy/*apply__;Iw!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOB2DdoXPP$">
https://nabp.pharmacy/programs/accreditations-inspections/dotpharmacy/#apply</a><o:p></o:p></span></li></ol>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<ol style="margin-top:0cm" start="5" type="1">
<li class="MsoNormal" style="mso-list:l5 level1 lfo5"><span style="font-size:11.0pt;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.<o:p></o:p></span></li></ol>
<p class="xmsolistparagraph" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<ol style="margin-top:0cm" start="6" type="1">
<li class="MsoNormal" style="mso-list:l4 level1 lfo6"><span style="font-size:11.0pt;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.<o:p></o:p></span></li></ol>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Michael<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="xmsonormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Lori Schulman <<a href="mailto:lschulman@inta.org">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">swyld@tucows.com</a>>; <a href="mailto:michael@palage.com">
michael@palage.com</a>; <a href="mailto:gnso-accuracy-st@icann.org">gnso-accuracy-st@icann.org</a><br>
<b>Subject:</b> RE: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition<o:p></o:p></span></p>
</div>
</div>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi,<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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.
<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<div>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">With kind regards,</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Lori S. Schulman</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Senior Director, Internet Policy</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">International Trademark Association (INTA)</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">+1-202-704-0408, Skype: LSSchulman</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:lschulman@inta.org">lschulman@inta.org</a><span style="color:#1F497D">,
</span><a href="https://urldefense.com/v3/__http:/www.inta.org__;!!DOxrgLBm!SlIPgOHk4NUnDgEMMf0nXcx1obQx41WYLv5aA_ETG0vREgw_a_nVQgvECCSTz8HOBycMdrw5$">www.inta.org</a><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="xmsonormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st-bounces@icann.org">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">michael@palage.com</a>; <a href="mailto:gnso-accuracy-st@icann.org">
gnso-accuracy-st@icann.org</a><br>
<b>Subject:</b> Re: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition<o:p></o:p></span></p>
</div>
</div>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi team,</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-CA" style="font-size:11.0pt;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:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sarah</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<pre><span lang="EN-CA"> </span><o:p></o:p></pre>
<pre><span lang="EN-CA"> </span><o:p></o:p></pre>
<pre><span lang="EN-CA" style="font-family:"Verdana",sans-serif">-- </span><o:p></o:p></pre>
<pre><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><o:p></o:p></pre>
<pre><span lang="EN-CA" style="font-family:"Verdana",sans-serif"> </span><o:p></o:p></pre>
<pre><span lang="EN-CA" style="font-family:"Verdana",sans-serif">Policy & Privacy Manager</span><o:p></o:p></pre>
<pre><span lang="EN-CA" style="font-family:"Verdana",sans-serif">Pronouns: she/they</span><o:p></o:p></pre>
<pre><span lang="EN-CA" style="font-family:"Verdana",sans-serif"> </span><o:p></o:p></pre>
<pre><a href="mailto:swyld@tucows.com"><span lang="EN-CA" style="font-family:"Verdana",sans-serif">swyld@tucows.com</span></a><span style="font-family:"Verdana",sans-serif"> </span><o:p></o:p></pre>
<pre><span lang="EN-CA" style="font-family:"Verdana",sans-serif">+1.416 535 0123 Ext. 1392</span><o:p></o:p></pre>
<p class="xmsonormal"><span lang="EN-CA" style="font-size:10.0pt;font-family:"Courier New""> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><img border="0" width="100" height="23" style="width:1.0416in;height:.2395in" id="x_Picture_x0020_3" src="cid:image002.png@01D7E6CA.14D0CED0"></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="xmsonormal"><b><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:michael@palage.com"><span lang="EN-CA">Michael Palage</span></a></span><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Sent: </b>November 26, 2021 12:02 PM<br>
<b>To: </b></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:gnso-accuracy-st@icann.org"><span lang="EN-CA">gnso-accuracy-st@icann.org</span></a></span><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Subject: </b>[GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<p class="xmsonormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hello All,<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In the RySG questions they cited to the proposed RrSG accuracy “definition” (aka contractual construct):<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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."<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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.<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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. <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-family:"Calibri",sans-serif"><img border="0" width="802" height="465" style="width:8.3541in;height:4.8437in" id="x__x005f_x0000_i1026" src="cid:image001.png@01D7E2BD.34B4CF00"></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> However, at the conclusion of the call as we were wrapping up the session, these edits were lost
<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-family:"Calibri",sans-serif"><img border="0" width="809" height="455" style="width:8.427in;height:4.7395in" id="x__x005f_x0000_i1025" src="cid:image002.png@01D7E2BD.34B4CF00"></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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?<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;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.
<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="xmsonormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Michael<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-CA" style="font-family:"Calibri",sans-serif"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>