<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=utf-8">
<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:"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:"Franklin Gothic Medium";
panose-1:2 11 6 3 2 1 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:144470301;
mso-list-template-ids:-1933951162;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:457798553;
mso-list-template-ids:-42959852;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:572201097;
mso-list-template-ids:-814464974;}
@list l2:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:629556481;
mso-list-template-ids:-636161238;}
@list l3:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:872037634;
mso-list-template-ids:1710778556;}
@list l4:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5
{mso-list-id:880090662;
mso-list-template-ids:-2091214462;}
@list l5:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6
{mso-list-id:985009856;
mso-list-template-ids:834585896;}
@list l6:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7
{mso-list-id:1071460793;
mso-list-template-ids:1892693962;}
@list l7:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8
{mso-list-id:1286809116;
mso-list-template-ids:-1860411750;}
@list l8:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9
{mso-list-id:1543520539;
mso-list-template-ids:-1117511302;}
@list l9:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10
{mso-list-id:1773167674;
mso-list-template-ids:-1137407650;}
@list l10:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Dear Michael, all,</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Thanks for your response and question. To confirm what Becky said, this is indeed an ICANN org response, but for those interested in how it came about, the concerns
were raised and shared by a cross-functional team within ICANN that coordinates on these topics that consists of reps from different departments including Policy, GDS, Legal, Compliance as well as other relevant SMEs as needed. Hope this helps clarify a bit,
and looking forward to hearing from others and continuing our work towards completing the assignments from Council together. </span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Best</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Brian</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-family:"Calibri",sans-serif;color:black">Becky Burr <BBurr@hwglaw.com><br>
<b>Date: </b>Tuesday, July 19, 2022 at 8:06 AM<br>
<b>To: </b>"michael palage.com" <michael@palage.com>, Brian Gutterman <brian.gutterman@icann.org>, "gnso-accuracy-st@icann.org" <gnso-accuracy-st@icann.org><br>
<b>Subject: </b>[Ext] Re: ICANN org concerns re "stress testing" proposals -Notes and action items - RDA Scoping Team Meeting #34 - 14 July 2022<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div id="divtagdefaultwrapper">
<p><span style="font-size:12.0pt;color:black">Hi Michael,<o:p></o:p></span></p>
<p><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p><span style="font-size:12.0pt;color:black">Didn't mean to get into an extended back and forth here, just sharing my personal views. <o:p></o:p></span></p>
<p><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p><span style="font-size:12.0pt;color:black">On issue 1, we disagree. Bottom line, if "Org" is wrong, Goran is accountable (and the Board to the extent that error reflects any oversight failure). <o:p></o:p></span></p>
<p><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p><span style="font-size:12.0pt;color:black">On point 2, when you register a domain name with GoDaddy, for example, you
<b>represent and warrant</b> that all information you submit when you create your account is accurate, current, and complete. If you are required to represent and warrant that you will not use gmail to send authorized, non-infringing emails that look like,
but are not spam to employees for the purpose of cybersecurity awareness and training, that is news to me. <o:p></o:p></span></p>
<p><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p><span style="font-size:12.0pt;color:black">b<o:p></o:p></span></p>
<p><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<div id="Signature">
<div id="divtagdefaultwrapper">
<p><b><span style="font-size:12.0pt;font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">J. Beckwith Burr</span></b><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p><span style="font-size:12.0pt;font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">HARRIS, WILTSHIRE & GRANNIS </span><span style="font-size:9.0pt;font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">LLP</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p><span style="font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">1919 M Street NW/8th Floor</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p><span style="font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">Washington DC 20036</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p><span style="font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">202.730.1316 (P) 202.352.6367 (M)</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<hr size="0" width="100%" align="center">
</span></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"> michael palage.com <michael@palage.com><br>
<b>Sent:</b> Tuesday, July 19, 2022 10:36:43 AM<br>
<b>To:</b> Becky Burr; Brian Gutterman; gnso-accuracy-st@icann.org<br>
<b>Subject:</b> RE: ICANN org concerns re "stress testing" proposals -Notes and action items - RDA Scoping Team Meeting #34 - 14 July 2022</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hello Becky,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks for your response. Respectfully, I disagree. Personally, I think the “who” is important. Because if you do not know the “who” and the “what” (considerable concerns)
how can there be accountability if the “who” was later found to be wrong. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regarding stress tests, many organizations regularly send fake spam messages to its employees to see if they will click on it as part of a broader cyber security and education
program.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Now as “we” are both aware there have been legal issues involving third parties that conduct these test when they use famous trademarks registered in the domain names sending
the fake spam. However, from what I heard from the proposals being discussed over the past couple of sessions, no one was proposing using the trademarks just manufactured identities so as to not involve PII.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If you could share any decisions regarding the legality of fake spam testing please share them to the list so that we can include them in our report.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Michael<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><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 0in 0in 0in">
<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"> Becky Burr <BBurr@hwglaw.com>
<br>
<b>Sent:</b> Tuesday, July 19, 2022 10:16 AM<br>
<b>To:</b> michael palage.com <michael@palage.com>; Brian Gutterman <brian.gutterman@icann.org>; gnso-accuracy-st@icann.org<br>
<b>Subject:</b> Re: ICANN org concerns re "stress testing" proposals -Notes and action items - RDA Scoping Team Meeting #34 - 14 July 2022<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div id="divtagdefaultwrapper">
<p><span style="color:black">FWIW - and speaking personally - I'm not sure why it matters "who" in Org was the source of this concern. It was presented as a view of the organization. <o:p></o:p></span></p>
<p><span style="color:black"><o:p> </o:p></span></p>
<p><span style="color:black">I understand the purpose of the stress test, but I too have to think about the ethics of attesting to the truth of information you know to be untruthful. <o:p></o:p></span></p>
<p><span style="color:black"><o:p> </o:p></span></p>
<div id="Signature">
<div id="divtagdefaultwrapper">
<p><b><span style="font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">J. Beckwith Burr</span></b><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">HARRIS, WILTSHIRE & GRANNIS </span><span style="font-size:9.0pt;font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">LLP</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">1919 M Street NW/8th Floor</span><span style="color:#006FC9"><o:p></o:p></span></p>
<p><span style="font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">Washington DC 20036</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-family:"Franklin Gothic Medium",sans-serif;color:#006FC9">202.730.1316 (P) 202.352.6367 (M)</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" 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.com <<a href="mailto:michael@palage.com">michael@palage.com</a>><br>
<b>Sent:</b> Tuesday, July 19, 2022 8:44:21 AM<br>
<b>To:</b> Brian Gutterman; <a href="mailto:gnso-accuracy-st@icann.org">gnso-accuracy-st@icann.org</a><br>
<b>Subject:</b> Re: [GNSO-Accuracy-ST] ICANN org concerns re "stress testing" proposals -Notes and action items - RDA Scoping Team Meeting #34 - 14 July 2022</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<table class="MsoNormalTable" border="0" cellspacing="3" cellpadding="0" style="max-height: 0px" id="mcpreviewzzyygg">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="mso-line-height-alt:0pt"><span style="font-size:1.0pt;color:white">Hello Brian, Thanks for the proactive response from ICANN Org. Could you please clarify who in ICANN Org has raised these “considerable concerns” and could you share
them in advance of Thursday’s call. The preamble to the WHOIS ACCURACY PROGRAM SPECIFICATION in the 2013 RAA state <o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="display:none"><o:p> </o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" id="mcalertwrapperzzyygg">
<tbody>
<tr>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><a href="https://urldefense.com/v3/__https:/us.report.cybergraph.mimecast.com/alert-details/?dep=yE5ebSAKbTFRMibvmZwTog*3D*3DSu10dhEECqc1RvnnJ9*2F94BeXvRwfLR5k35iUlDZ9e2zIlk1R5AJkrX4BkiXk3VunhcU23VD1JrWbAsjlztdAPWp*2Fjve8cr2*2BEfBYnhPD*2B9wngWteR1l8V92x7Zq1rNiKiWhv4Eyc0aSMglOqvmVKMEyApT216onesfHTI4GjkYGhK8cYAaJvJiaT9Uxr2DoMSARrvGjIAXSc20OLD*2BvQZ8Uu9xlhDGI80BH2G335NqzvtJnDJwBzBFou7f7izcWPmdGEZw9CYh8V8idqQRL4aCr5Do8G36pjwnqUoyzpVFz1Lmf5Z20h*2FpjNhhry*2BrINWguT2ZWCbYhux9ZDLIxdfHIy6Pw0uC*2BBV7Qj42nQvrlvLxB3HpAKIhZ0wfbQMXqnLRUofk4*2Fow45gh68aw63dPkQZfFMILTF1CYn9u9Hsdbm1v9*2BeOEMgqWV*2FOU*2FGQNonTcceVBUnDG06uJMLlY2lZ4o8qPihMgwBZBRBTjCDbCpcBB2*2Bko*2B1bvPEibYaaoLlwitxaErb5HrTQDwtOfDtWYSDuESwaydECa0iO12*2B2YeWRrHWg6bvYsV5pq9MefaQLcmhru56I9RTGuIOimNk1iipoPXWx9R1bKjATgtbDRXKGCLKwWbj3pvdFhaoN9RFRoo82gWbhmSAee7KVZZJHBhtlm4CMxRLSP0qRf27jYYoGRNsdi0ICcCVFNRLb3YEv2KsNPasO*2BgdqsGaMAV7oJiIk7wWezY03*2BlhOXGeLlqoUwUHYi4VtRXfy75wFdN*2BcuozQ4CvKswM*2FQQ87kfJq7gbaDL09CxrnDSMMT0zYjQ91M9ZFsLnSUcN6kYYhVYR3d*2FwxXOXv7OzlYc9f6j1A*3D*3D__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!PtGJab4!_vDw2JEGMSxojXKS2wVdR2szAvd2D32v70oZEt1sXISM4oWpm1zpu01in4nPL5zW02W2-4VF6BQf-QBjI2R0mQkQ$"><span style="text-decoration:none"><img border="0" id="_x0000_i1025" src="https://alert-dg01.redatatech.com/onprem_security_warning_fetch?r=1&dep=yE5ebSAKbTFRMibvmZwTog%3D%3DSu10dhEECqc1RvnnJ9%2F94BeXvRwfLR5k35iUlDZ9e2zIlk1R5AJkrX4BkiXk3VunhcU23VD1JrWbAsjlztdAPWp%2Fjve8cr2%2BEfBYnhPD%2B9wngWteR1l8V92x7Zq1rNiKiWhv4Eyc0aSMglOqvmVKMEyApT216onesfHTI4GjkYGhK8cYAaJvJiaT9Uxr2DoMSARrvGjIAXSc20OLD%2BvQZ8Uu9xlhDGI80BH2G335NqzvtJnDJwBzBFou7f7izcWPmdGEZw9CYh8V8idqQRL4aCr5Do8G36pjwnqUoyzpVFz1Lmf5Z20h%2FpjNhhry%2BrINWguT2ZWCbYhux9ZDLIxdfHIy6Pw0uC%2BBV7Qj42nQvrlvLxB3HpAKIhZ0wfbQMXqnLRUofk4%2Fow45gh68aw63dPkQZfFMILTF1CYn9u9Hsdbm1v9%2BeOEMgqWV%2FOU%2FGQNonTcceVBUnDG06uJMLlY2lZ4o8qPihMgwBZBRBTjCDbCpcBB2%2Bko%2B1bvPEibYaaoLlwitxaErb5HrTQDwtOfDtWYSDuESwaydECa0iO12%2B2YeWRrHWg6bvYsV5pq9MefaQLcmhru56I9RTGuIOimNk1iipoPXWx9R1bKjATgtbDRXKGCLKwWbj3pvdFhaoN9RFRoo82gWbhmSAee7KVZZJHBhtlm4CMxRLSP0qRf27jYYoGRNsdi0ICcCVFNRLb3YEv2KsNPasO%2BgdqsGaMAV7oJiIk7wWezY03%2BlhOXGeLlqoUwUHYi4VtRXfy75wFdN%2BcuozQ4CvKswM%2FQQ87kfJq7gbaDL09CxrnDSMMT0zYjQ91M9ZFsLnSUcN6kYYhVYR3d%2FwxXOXv7OzlYc9f6j1A%3D%3D"></span>[us.report.cybergraph.mimecast.com]</a><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:white">Hello Brian,</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Thanks for the proactive response from ICANN Org. Could you please clarify who in ICANN Org has raised these “considerable concerns” and could you
share them in advance of Thursday’s call.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">The preamble to the WHOIS ACCURACY PROGRAM SPECIFICATION in the 2013 RAA states that the“ Registrar shall implement and comply with the requirements
set forth in this Specification, as well as <b>any commercially practical updates</b> to this Specification that are developed by ICANN and the Registrar Stakeholder Group during the Term of the Registrar Accreditation Agreement.”<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">The “stress test” cited by several members of the Scoping Team seems “commercially practical” to me. Therefore, I think from a fact finding perspective
we need to document why this is not commercially practical and who is objecting, i.e. ICANN Org and/or the Registrars.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Further to our fact gather exercise, is anyone aware of any legal actions taken by a Contracting Party against a registrant/third party that had knowing
provided false and inaccurate information in connection with a domain name registration? For the avoidance of any doubt, I do not believe that any one has proposed that these “stress test” domain names be used in any type of DNS Abuse or illegal activity.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Michael<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st-bounces@icann.org">gnso-accuracy-st-bounces@icann.org</a>>
<b>On Behalf Of </b>Brian Gutterman<br>
<b>Sent:</b> Monday, July 18, 2022 1:47 PM<br>
<b>To:</b> <a href="mailto:gnso-accuracy-st@icann.org">gnso-accuracy-st@icann.org</a><br>
<b>Subject:</b> [GNSO-Accuracy-ST] ICANN org concerns re "stress testing" proposals -Notes and action items - RDA Scoping Team Meeting #34 - 14 July 2022<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt;color:black">Dear Accuracy Scoping Team Colleagues,</span><span style="font-size:10.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt;color:black">With respect to the proposal(s) related to “stress testing” that the group is currently considering and discussing, we wanted to flag
that ICANN Org has some considerable concerns about this. Any proposal that suggests that ICANN (or a proposal that ICANN org would ask a third party to do this on its behalf) would enter into domain name registration agreements fraudulently with fake contact
info, etc. raises a red flag. Carrying out a stress-test like this may violate many different laws. </span><span style="font-size:10.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt;color:black">While we do appreciate and support “outside the box” proposals as we carry out the GNSO instructions and assignments together, we wanted
to flag to the group that it may not be possible for ICANN to implement such a proposal, should there be support from the Scoping Team to include it in its write up.</span><span style="font-size:10.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt;color:black">Thanks and look forward to discussing more about this on Thursday.</span><span style="font-size:10.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt;color:black"><br>
Best,</span><span style="font-size:10.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt;color:black">Brian</span><span style="font-size:10.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="color:black">From:
</span></b><span style="color:black">GNSO-Accuracy-ST <</span><a href="mailto:gnso-accuracy-st-bounces@icann.org">gnso-accuracy-st-bounces@icann.org</a><span style="color:black">> on behalf of Caitlin Tubergen <</span><a href="mailto:caitlin.tubergen@icann.org">caitlin.tubergen@icann.org</a><span style="color:black">><br>
<b>Date: </b>Thursday, July 14, 2022 at 11:55 AM<br>
<b>To: </b>"</span><a href="mailto:gnso-accuracy-st@icann.org">gnso-accuracy-st@icann.org</a><span style="color:black">" <</span><a href="mailto:gnso-accuracy-st@icann.org">gnso-accuracy-st@icann.org</a><span style="color:black">><br>
<b>Subject: </b>[GNSO-Accuracy-ST] Notes and action items - RDA Scoping Team Meeting #34 - 14 July 2022<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><u><span style="font-size:11.0pt;color:black">Action Items<o:p></o:p></span></u></b></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Proponents of “stress testing” (ALAC, GAC, IPC, etc.) to provide further information into the dedicated
</span><a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit__;!!PtGJab4!-fyqNJe7qNx8ZYfQeUsk1nAqu2VgQFzA7dbFnFbAOUAvSYRpcv1eRuOQbvxpSNTUbwdyTR_QgObLpVGjFijiR5fH6bV7oXpDAh2WBA$"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">template
[docs.google.com]</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">, beginning on p. 20 by COB Tuesday, 19 July. The additional details and context will be discussed by the team during the next meeting.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Michael P. to provide questions coming out of today’s meeting, e.g., budget allocation for ARS and status of AFAV, to ICANN
org liaison in writing by COB Tuesday, 19 July.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">GAC members to provide additional context as to what “reliability of data” means in reference to their registrar audit proposal
(proposal 5) by COB Tuesday, 19 July.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Policy Support Staff to schedule an additional meeting for next week on Thursday, 21 July at 14:00 UTC.
<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:11.0pt;color:black">Registration Data Accuracy Scoping Team – Meeting #34</span></b><span style="font-size:11.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black">Thursday 14 July at 14.00 UTC <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l10 level1 lfo2">
<span style="font-size:11.0pt">Welcome & Chair Updates<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoListParagraph" style="color:black;mso-list:l10 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Review responses to the survey (at time of publication of agenda – 10 responses received, 70% is of the view that there
are no other proposals to consider, 20% have put forward an additional proposal for consideration (see hereunder) and 10% doesn’t have any additional proposals themselves but are willing to consider those of others)</span>
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li></ol>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="color:black;mso-list:l10 level3 lfo2"><span style="font-size:11.0pt">Review additional proposals put forward<o:p></o:p></span></li></ol>
</ol>
</ol>
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="color:black;mso-list:l7 level3 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Four proposals provide proposed enhancements to the registrar survey<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l7 level3 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There are some proposals regarding registrar audit/understanding of current accuracy requirements<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l7 level3 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There is a proposal about AFAV, ccTLD practices, other validation/verification requirements<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l7 level3 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Propose using the meeting time to go through the proposals that deal with additional suggestions from the registrar survey
– these appear to be additions to what is already suggested in the report. As you may recall, a small group effort worked on proposed questions that appear as an annex in the write-up.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l7 level3 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></li></ol>
</ol>
</ol>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="mso-list:l10 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The Accuracy Scoping Team needs to have a discussion about whether it makes sense to survey registrars on how they currently implement
the requirements of the RAA Whois Accuracy Specification. As it stands, we are unclear on how registrars implement the accuracy obligations. The results of the survey could be used to assist with measuring accuracy in the Annex D survey and provide more context
for what is meant by validation and verification. Please see draft survey attached to this email<span style="color:black;letter-spacing:.15pt;background:#F8F9FA">
</span></span><a href="https://mm.icann.org/pipermail/gnso-accuracy-st/2022-May/000459.html"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;letter-spacing:.15pt;background:#F8F9FA">https://mm.icann.org/pipermail/gnso-accuracy-st/2022-May/000459.html</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#202124;letter-spacing:.15pt;background:#F8F9FA">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> (Sophie Hey, RySG)<o:p></o:p></span></p>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoListParagraph" style="mso-list:l10 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The Accuracy Team should revisit the idea of a registrar survey and discuss whether it makes sense to survey registrars on how they
currently implement the requirements of the RAA Whois Accuracy Specification. We are unclear on how registrars implement the accuracy obligations.
<o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<p class="MsoListParagraph" style="margin-left:2.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(Elizabeth Bacon, RySG)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:2.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What kind of effort would this take, and by whom, to implement this proposal?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:2.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ICANN Org: have the survey translated into the 6 UN languages, create form for survey, distribute survey RrSG: work with ICANN Org to encourage
registrars to respond to the survey Scoping Team: Analyse the results of the survey and report to Council. This could be done after the survey has closed, or the Scoping Team could meet while the survey is open to discuss how the results of the survey should
be interpreted. <o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:2.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(Sophie Hey, RySG, Elizabeth Bacon, RySG)<o:p></o:p></span></p>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoListParagraph" style="mso-list:l10 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Registrar survey should include a measure of: a. Number of domains sponsored by the registrar; b. Number or percent of sponsored domains
that have had their email contacts operationally verified; c. Number or percent of sponsored domains that had had their phone contacts operationally verified. d. A statement of whether the registrar analyzes all bounces of other indications of possible delivery
failure or contact inaccuracy to rectify the situation. ii. Registrar survey should include a request for other (i.e .non-RAA) checks that they do related to accuracy and/or identity that they perform either voluntarily of to satisfy requirements for specific
gTLD registries or for ccTLDs. iii. Discussion should be initiated with ICANN Org to identify specific incentives to registrars for completing the survey (if too complicated with no incentive, results will be rather limited)<o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.75in">
<span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.75in">
<span style="font-size:11.0pt">The Scoping Team must work with ICANN Org to develop the survey. The team must meet to enable such interaction with ICANN Org (at whatever intervals are necessary to support the ICANN Org work). There would be no need to meet
which the survey is being carried out and until there is a preliminary analysis. However, there should be regular updates on the status and returns. ii. If there is any indication that the survey is not been met with reasonable enthusiasm resulting in significant
input, the Scoping Team should be re-convened to address this.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(Alan Greenberg, ALAC)<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black;letter-spacing:.15pt;background:#F8F9FA"><o:p> </o:p></span></p>
<ol start="1" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level3 lfo4">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Believe registrar survey has merit, and the output would be worth the group’s time<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level3 lfo4">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There is nothing preventing the group from completing the write-up to the Council, and, in the event the Council greenlights the registrar survey, what could be a proposed cadence of the group
to work on the survey? <o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level3 lfo4">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From a Support Staff perspective: the original proposal sets out detailed questions and the proposed approach to be taken. If the group is supportive of the questions, Support Staff could work
on a survey mockup and work with the group on finetuning the questions and format. One thing for the group to consider: the longer the survey, the more difficult it may be to get a response from registrars.
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level3 lfo4">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">With respect to meeting times, this is unlikely to be a weekly conversation. ICANN org is already planning for the next ICANN meeting, and a slot for this group has been tentatively reserved. The
group could consider enlisting a smaller team to work on this rather than the entire group. An intermediate step would be to share the write-up to the Council and see if they approve of the registrar survey.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level3 lfo4">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Group should be able to submit the write-up on Assignments 1 and 2 before the survey is complete.
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level3 lfo4">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">That’s correct, and that is the expectation between assignments 2 and 3.
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level3 lfo4">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Yes, the assignment for 1 and 2 should be submitted to the Council – it’s important to have the check-in with the GNSO Council as its ultimately the Council’s call to review the recommendations
and consider them.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level3 lfo4">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The implementation of the survey can be worked on after Council gives its green light to move forward with that approach<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level3 lfo4">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">One unknown is to what extent the current RAA requirements related to accuracy are being implemented. The RAA gives the registrar a number of options – multiple fields can be verified, for example.
It’s also unclear how many domain names are covered by the 2013 RAA. There may be other checks that are being carried out, not specified in the RAA, that the group should be made aware of. In terms of the survey being potentially too onerous – perhaps a consideration
would be to prioritize the questions (please answer x questions at a minimum) or providing an incentive for registrars to provide incentives.
<o:p></o:p></span></li></ol>
</ol>
</ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in">
<span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:2.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">4. ICANN CPHs AND NIS2 CONSIDERATIONS. The recently negotiated EU NIS2 initiative is expected to pass this Fall. The RDA could work together
to find solutions for implementation within ICANN's contract framework. NIS2 requires that internet service providers adopt and implement proportionate processes to verify registration data. ICANN should be adapting the Registrars survey to include questions
that establish what the best practices are among cc's and gTLDs and come up with our recommendations as to what would be proportionate. Such data would be useful as the NIS2 is adopted by the member states. It would be a real breakthrough for community efforts
come up with a joint agreement that could be socialized within ICANN and by jurisdictions that are proposing NI2 implementing language or similar laws outside of the EU. We can use this opportunity to stand together and demonstrate the strength of the MSM.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:#202124;letter-spacing:.15pt;background:white"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What kind of effort would this take, and by whom, to implement this proposal?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The registrar survey could be drafted to include specific questions to explain the verification procedures that registrars employ, if the verification
processes go beyond the minimum that ICANN requires within its contract, what percentage of domains are operationally verified, what the costs of such verification are to the Internet Service providers. There may not be any additional costs just rethinking
of questions. <o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(Lori Schulman, IPC)<o:p></o:p></span></p>
<ol start="1" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level3 lfo5">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Perhaps there could be an open question, such as: are there other things you do? Rather than guiding the registrars to respond from a ccTLD perspective.
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level3 lfo5">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This could provide some evidence to go and see what is out there. Because the group wants to make fact-based determinations, it would be helpful to understand current business practices.
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level3 lfo5">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ccTLDs may have valuable information for this group, such as .DK.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level3 lfo5">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The legal considerations that may differ ccTLDs from gTLDs are a factor when the group decides to recommend policy – however, if there are other accuracy-related checks that are financially viable,
whether they can applied universally or not, could be helpful to understand and analyze<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level3 lfo5">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Countries operate differently, and would not recommend this. Need to be extremely cautious in applying practices that go with ccTLDs that is a market reality in gTLDs. Would recommend seeking an
opinion from Bird & Bird.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level3 lfo5">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agree to ask; however, there are things to consider once responses come in – the scoping team will need to carefully analyze.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level3 lfo5">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">With respect to comments on .DK, not suggesting their methods should be blindly applied but could be considered.<o:p></o:p></span></li></ol>
</ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.5in">
<b><span style="font-size:11.0pt">Registrar Audit & understanding of current accuracy requirements<o:p></o:p></span></b></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoListParagraph" style="margin-left:2.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">5. Building on the ICANN74 Communique, the GAC encourages the team to explore additional and complementary work items, such as: - measuring
existing registrant data accuracy controls for new registrations, - testing accuracy controls in a manner that is not dependent upon access to personal data (i.e., data that relate to an identified or identifiable individual), - testing registrar safeguards/systems
to see how cases of inaccurate data are handled. etc. Moreover, on the separate topic of what further interim work may be done (separate and apart from the proposals for Registrars surveys and testing), we can discuss how current accuracy requirements are
understood and enforced. We note that these requirements are not limited to accurate but also to reliable data (also confirmed by the GNSO instructions when forming the accuracy scoping team). The team has not yet analyzed whether there are procedures in place
to ensure that the registration data are both accurate and reliable.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:2.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What kind of effort would this take, and by whom, to implement this proposal?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:2.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is something the Scoping Team should discuss in more detail in upcoming meetings. For instance, the following considerations should be
discussed: 1. Who should conduct the testing? (ICANN? Academic researcher? Open invite to parties who may wish to conduct the testing at their own expense?). 2. How many test registrations should be conducted per registrar? 3. How many registrars should be
tested and how should this sample be selected. 4. Cost considerations?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:2.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(Melina Stroungi, GAC)<o:p></o:p></span></p>
<ol start="4" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">An audit limits what this group can ask because as part of an audit, ICANN can only require registrars to respond to contractual requirements that the registrar is obligated to do<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Audit is probably the wrong word here<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Reliability – to some this means that the message is sent to the registrant and the registrant will acknowledge receipt and respond<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">One additional question – what would be the sequencing of the survey and the stress test – could there be questions for the survey that would inform the stress test?
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Confused as to what is being spoken about vs. what is on the screen – the trigger is updates to the contact information. The RAA has certain requirements and could be repeated if helpful. In terms
of reliability – what does this mean? <o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Could GAC provide an update as to what reliable means in advance of next week’s call?
<o:p></o:p></span></li></ol>
</ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="4" type="1">
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoListParagraph" style="mso-list:l1 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Stress-test the current RAA validation/verification rules by having ICANN Org contract for a study to register names with varying degrees
of inaccuracy (in all of its varied definitions) and report to what extent these were recognized during registration).<o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(Alan Greenberg, ALAC)<o:p></o:p></span></p>
<ol start="1" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l9 level3 lfo6">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">It may be helpful to know what ICANN previously spent on ARS to inform if there is budget for something like this<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l9 level3 lfo6">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Michael to put draft question to ICANN org in writing<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l9 level3 lfo6">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Concerns with this proposal: do not like that this team or ICANN is going to choose a specific registration provider or several and that provider gets business from this test. Then the chosen provider
gets more scrutiny than the providers who are not chosen. Buying a domain name with purposely incorrect information violates the registration agreement<o:p></o:p></span></li></ol>
</ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="4" type="1">
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoListParagraph" style="mso-list:l1 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">FINDING ACCURACY DATA ISSUES USING TEST CASES. ICANN could contract with a 3rd party (either a university or private vendor) to register
a statistically significant sample of domain names across gTLDs using a fictitious entity. The contractor would monitor the number of domains that were flagged as needed further verification during the initial registration period and then followed to determine
whether subsequent accuracy complaints are filed and how they are resolved.<o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What kind of effort would this take, and by whom, to implement this proposal<o:p></o:p></span></p>
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6 level2 lfo7">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This would take the scoping of an RFP and a bid for the work by ICANN staff with consultation from the RDA (probably a small working group) and would add an additional survey cost. However, the
results could solve a lot of our questions as to the nature and scope of existing accuracy problems. Issues of GDPR liability are eliminated under this scenario as no rights will be violated due to fictitious nature of registrant.<o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(Lori Schulman, IPC)<o:p></o:p></span></p>
<ol start="1" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level3 lfo8">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The registrar would not know that this is a fictitious registrant or entity and would not know that this could be treated differently, and if they do not know, that seems to defeat the purpose.
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level3 lfo8">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">More clarification would be helpful – getting to a number may not supply anything useful – what does this number mean for example.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level3 lfo8">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Helpful to follow the standard template<o:p></o:p></span></li></ol>
</ol>
</ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.75in">
<b><span style="font-size:11.0pt">Cross field validation study<o:p></o:p></span></b></p>
<ol style="margin-top:0in" start="4" type="1">
<ol style="margin-top:0in" start="4" type="1">
<li class="MsoListParagraph" style="mso-list:l1 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Contract for an independent study of the value of and feasibility of cross-filed verification (as required by the 2013 RAA but never
enforced).<o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(Alan Greenberg, ALAC)<o:p></o:p></span></p>
<ol start="1" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l8 level3 lfo9">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Cross-field validation, which is a 2013 RAA requirement, has never been implemented or enforced – largely b/c this was deemed not feasible. This warrants more investigation – looking at it in the
context of today’s technology, is may be more practical to implement and enforce today.
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l8 level3 lfo9">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Would recommend ICANN provide an update on the last time this was done.
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l8 level3 lfo9">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Michael to include a question about AFAV status in email to Brian (org liaison).<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l8 level3 lfo9">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">It should be possible for each registrar to have its own policy as to what validation and verification it does, but ICANN provides the minimum.<o:p></o:p></span></li></ol>
</ol>
</ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in">
<b><span style="font-size:11.0pt">Study of ccTLD practices<o:p></o:p></span></b></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<ol style="margin-top:0in" start="4" type="1">
<ol style="margin-top:0in" start="5" type="1">
<li class="MsoListParagraph" style="mso-list:l1 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ccTLDs should be surveyed to identify the level of accuracy and process that they undertake. This should be done with the support of
the ccNSO which will hopefully be supportive.<o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(Alan Greenberg, ALAC)<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in">
<b><span style="font-size:11.0pt">Development of other validation / verification requirements<o:p></o:p></span></b></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black;letter-spacing:.15pt;background:#F8F9FA"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="4" type="1">
<ol style="margin-top:0in" start="6" type="1">
<li class="MsoListParagraph" style="mso-list:l1 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There have been statements made by some team members that the current RAA requirements are not sufficient. The team should delve into
this and develop a list of possible (and practical) other validation/verifications/whatever-appropriate-descriptor should be considered for future RAA revisions. These should each include a rationale as to what the benefit would be. Such checks could be made
at the time of registration or at other specific times within the life of the registration<o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What kind of effort would this take, and by whom, to implement this proposal?<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in">
<span style="font-size:11.0pt">Item vii above is a Scoping Team effort and it must meet to carry out this task.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(Alan Greenberg, ALAC)<o:p></o:p></span></p>
<ol start="1" type="1">
<ol start="1" type="1">
<ol start="5" type="1">
<li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l8 level3 lfo9">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not know if this delves into assignments 3 and 4 – this is simply saying to put some new ideas on the table.
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l8 level3 lfo9">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This appears to be #4 - in #3, gaps are expected to be identified and then #4 should identify how those gaps can be addressed (through which process)<o:p></o:p></span></li></ol>
</ol>
</ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:92.15pt;text-indent:-21.25pt">
<span style="font-size:11.0pt;color:black">Confirm next steps<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo10">
<span style="font-size:11.0pt">Finalize write up for assignments #1 and #2 for delivery to GNSO Council – see</span><a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit__;!!PtGJab4!7BlUNWXnfgnY8AvtdY-t5IQIhkBd5hofl-TbXbYbrO8CKyzULNdsHB47JmFtFJy--38L03ZeWVwVmFw1t5CY63mKsEH2T-DLlCK2$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit__;!!PtGJab4!7BlUNWXnfgnY8AvtdY-t5IQIhkBd5hofl-TbXbYbrO8CKyzULNdsHB47JmFtFJy--38L03ZeWVwVmFw1t5CY63mKsEH2T-DLlCK2$"><span style="font-size:11.0pt">https://docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit [docs.google.com]</span></a>
<span style="font-size:11.0pt"><o:p></o:p></span></li></ol>
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo10">
<span style="font-size:11.0pt">Any outstanding items?<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo10">
<span style="font-size:11.0pt">Confirm deadline for final review<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo10">
<span style="font-size:11.0pt">Confirm next steps <o:p></o:p></span></li></ol>
</ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:justify">
<span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo11">
<span style="font-size:11.0pt">Confirm action items & next meeting (TBC)<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>