<html 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)">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
@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:763763306;
mso-list-template-ids:498633570;}
@list l0:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
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:1367681422;
mso-list-template-ids:-773682422;}
@list l1:level1
{mso-level-start-at:4;
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:1597859501;
mso-list-template-ids:-1552362876;}
@list l2:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
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:1640648111;
mso-list-template-ids:-1978367726;}
@list l3:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:"Times New Roman";}
@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:2097632616;
mso-list-template-ids:1451517368;}
@list l4:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;}
@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;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Dear RDA Scoping Team Members,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Please find below the notes and action items from today’s meeting.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">The next RDA Scoping Team meeting will be on Thursday, 9 December at 14:00 UTC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><br>
Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Marika, Berry, and Caitlin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">--<o:p></o:p></span></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></b></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;color:black">Action Items<o:p></o:p></span></u></b></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></b></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="color:black;mso-list:l4 level1 lfo1"><b><span style="font-size:11.0pt">Still open: </span></b><span style="font-size:11.0pt">Team to add any additional proposed questions for ICANN org to the <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit__;!!PtGJab4!u-wHvYML5zhCk8ZgpzCmNNvcyFLcdXXoS5VXHaIgkRBKVYdrhgade1EhAfriJYm9BEO3v4z4Aw$" title="https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit__;!!PtGJab4!u-wHvYML5zhCk8ZgpzCmNNvcyFLcdXXoS5VXHaIgkRBKVYdrhgade1EhAfriJYm9BEO3v4z4Aw$">google
doc [docs.google.com]</a> as soon as possible, but no later than Wednesday 1 December to allow for finalization during next week’s meeting.
<b>*NOTE: if your group has not submitted questions yet, please do so ASAP as the deadline has already passed.*<o:p></o:p></b></span></li><li class="MsoNormal" style="color:black;mso-list:l4 level1 lfo1"><b><span style="font-size:11.0pt">Still open:
</span></b><span style="font-size:11.0pt">Team to complete the <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?pli=1__;!!PtGJab4!u-wHvYML5zhCk8ZgpzCmNNvcyFLcdXXoS5VXHaIgkRBKVYdrhgade1EhAfriJYm9BEPWEnx8ZQ$" title="https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?pli=1__;!!PtGJab4!u-wHvYML5zhCk8ZgpzCmNNvcyFLcdXXoS5VXHaIgkRBKVYdrhgade1EhAfriJYm9BEPWEnx8ZQ$">gap
analysis document [docs.google.com]</a> prior to the next meeting on <b>Thursday, 9 December</b>.
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l4 level1 lfo1"><span style="font-size:11.0pt">RDA Support Staff to circulate a doodle poll for alternate meetings time for the week of 13 December.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l4 level1 lfo1"><span style="font-size:11.0pt">Individuals or groups that proposed
<a href="https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit">
<span style="color:windowtext">questions for ICANN org</span></a> to review questions and determine if updates are necessary in light of the team’s discussions by
<b>Wednesday, 8 December</b>.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:black">Registration Data Accuracy Scoping Team – Meeting #8</span></b><span style="font-size:11.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Thursday 2 December at 14.00 UTC<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt">Welcome & Chair Updates (5 minutes)<o:p></o:p></span>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The Thursday, 16 December meeting conflicts with a GNSO Council meeting; there are a few options available for alternate
times.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The options are: Wednesday, 15 December at 14:00 UTC, Thursday, 16 December 13:00UTC, or Thursday, 16 December at 16:00
UTC.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Following the call, ICANN Support Staff to send a doodle poll to the Team so that members may indicate preferences. Leadership
will make the decision following the doodle poll results.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Most of mailing list archive issues seem to have been resolved; some members, Michael included, occasionally do not receive
emails. Members should periodically check the archive list to ensure no emails are missed.<o:p></o:p></span></li></ul>
</li></ol>
<p class="MsoNormal"><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="MsoNormal" style="color:black;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System (60 minutes)<o:p></o:p></span>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="color:black;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">Input received from scoping team to date: </span><span style="font-size:11.0pt;color:windowtext"><a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit__;!!PtGJab4!r3KYPSUnxXxCgiSX4_hbeMBpmIRV-S1iG6x_nPjdaqcZloxfKGrEej5wMDqTtPZV5eueF6Bprg$" title="https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit__;!!PtGJab4!r3KYPSUnxXxCgiSX4_hbeMBpmIRV-S1iG6x_nPjdaqcZloxfKGrEej5wMDqTtPZV5eueF6Bprg$"><span style="color:#0563C1">https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit[docs.google.com]</span></a></span><span style="font-size:11.0pt"><o:p></o:p></span></li></ol>
</li></ol>
<ol start="1" type="1">
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What does the team believe should be the threshold for having questions included on this list going forward?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">During the previous call, Alan G. noted he would make updates to certain questions. Additionally, in response to Question
4, Support Staff noted that it would be up to the contracted party whether to disclose all or part of the information in a request.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">These are not questions from the entire team; individual stakeholder groups are called out in these questions. However,
it will be important to assess whether these questions have already been answered (in the briefing documents, for example). Also, team members may have suggestions on how to clarify or improve the questions, but if the questions get submitted should ultimately
fall to the submitter of the question. In other words, the barrier to entry should be low.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The questions note they are put forward by a specific stakeholder group; will leave it up to individuals if the question
has the sign-off of the stakeholder group or if it should be submitted on behalf of an individual. Support Staff will organize the questions and group them, which the team can review before submission to ICANN org.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Previously Whois accuracy complaints were clear, but what kind of complaints is Compliance seeing now? – this would be helpful
to understand in light of GDPR <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What is the main cause for complaints being rejected before being passed on to registrars? – this would also be helpful
to understand since contracted parties have no visibility into this<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RySG believes it would be important to understand ICANN org’s interpretation of the difference between verification and
validation requirements<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RySG – Question 10 – get at answering the question from GNSO Council – does ICANN compliance agree with the definition put
forward by the registrars?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There are multiple levels of accuracy, so the term accuracy unadorned is not sufficient – for example, is it operational
accuracy, is it syntactic accuracy, or is it something else?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In terms of Rr definition re: what is currently monitored under the RAA, RySG is not disputing what Rrs have previously
noted. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There are many ifs, buts, and ands in the Whois Accuracy Program Specification description of accuracy that are not included
here. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There is an open issue on the definition.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Would prefer to use contractual construct rather than definition. Do not understand the value of asking ICANN compliance
if they agree with this definition. What would the impact be of a yes or a no reply from ICANN compliance?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Assignments 3 and 4 will look at where potential changes or shortcomings may be identified.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RrSG is not proposing any definition; the RrSG just described what registrars are contractually obligated to do. If other
members don’t like it as a definition, it’s irrelevant.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In terms of operational accuracy, this is very important under the UDRP to provide proper notice to the complainant and
respondent. The postal address is very important in terms of providing proper notice. Is there a reason the postal address is specifically omitted from this list?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The answer to this question is that postal address is part of the syntactical accuracy requirement, but not the operational
accuracy requirement. There is no requirement to verify a registrant’s postal address.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not asking if someone is actually there, but does this address exist?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Some of this concern is addressed in the across field address validation work from ICANN org.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In listening to the feedback, one thing that could make sense – when registrars submitted this, they included additional
context around it. It may be helpful to also include the additional context with this definition to quell some of the concerns. Registrars proposed the definition to capture what the current state is. It’s important to understand the current accuracy situation
before recommending new requirements.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Discussing data quality here – this is important to keep in mind. The 2013 RAA was not constructed with data protection
in mind. This needs to be reviewed along with the new policy. Some of the accuracy requirements may not be justifiable anymore. Cannot turn back to an archaic contract that needs to be revised to ensure requirements are lawful under a data protection lens.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This may be more relevant for the next assignment, i.e., the gap analysis.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This requires a paper, not just a paragraph. Analyze the contract, the new policy and if it passes legal scrutiny. After
finding out what can stand in the RAA, then start from scratch in terms of what ICANN compliance can do in terms of accuracy review.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is what this group using as its current understanding of what accuracy is corresponding properly to ICANN Compliance’s view?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This group is not here to make up things that would be nice; the group is to look at current requirements and purposes and
see if purposes match the current requirements. The second question re: what ICANN Compliance thinks presumes ICANN Compliance is the ultimate arbiter of the contract and policy; they are not and are not infallible – they have stood corrected in their interpretation
of the policy.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The real world is showing this group that changes need to be made. For UDRP respondents, DHL couriers are rarely able to
send notice to postal addresses b/c so many are inaccurate. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If there is a concern with postal addresses, it is important to pursue that in the gap analysis along with any supporting
references that could be documented.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question 12 – the term “usually” should be quantified into a percentage.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question 13 – there are multiple terms that almost say the same thing – for example – reasonable and commercially practicable,
commercially reasonable, etc. Is there a standard that this is being judged against?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is an interesting question, but what is the connection to the accuracy scoping team’s work? This question should be
adjusted to include this.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The RAA notes that AFAV is subject to technical and commercial feasibility – knowing how ICANN interprets that is relevant
to this group’s work. Support Staff pointed to a document that says “we hope to come to an agreement on what that means”, and that document is four years old – that does not bode well for this group’s work.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not think the question is relevant at all because it does not speak to accuracy, it talks about pre-conditions for accuracy
requirements; this is irrelevant for the team’s work.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What is the upside of not asking the question now and asking it later?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Should address questions 1 and 2 first, which deal with the current status quo. The status quo does not include across field
address validation.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">It is important to see this exercise as holistically as possible. The commercial reasonable phrase is very important because
it appears in multiple instances in multiple documents.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not object to the question, but it should be asked in the right phase. Also, have concerns with trying to define generic
contractual terms.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not trying to determine what reasonableness is in a philosophical way. The team has been asked to put together definitions
– need to look at this holistically. What are the things that affect accuracy? There are many moving parts, including commercially practicable and commercially reasonable.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There are currently 20 questions in this document; it’s not possible to go through the remaining 7 questions in the remaining
time. Hope to conclude the questions during the next call.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ISPCP does not anticipate submitting any questions.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">BC is unsure if it will submit questions.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">NCSG will get back to the group soon on if it will submit questions.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">GAC needs additional time to coordinate questions.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level2 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">It appears the group is falling behind its stated objective. Have advocated for asynchronous activity on the list; however,
thus far, the group has only made progress on plenary calls. At a certain point, the team may have to start increasing the cadence if the work continues to fall behind.
<o:p></o:p></span></li></ul>
</ol>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="2" type="a">
<li class="MsoNormal" style="color:black;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">Scoping team input<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">Confirm final questions for submission to ICANN org<o:p></o:p></span></li></ol>
</ol>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo4"><span style="font-size:11.0pt">Gap Analysis (25 minutes)<o:p></o:p></span>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="color:black;mso-list:l2 level2 lfo4"><span style="font-size:11.0pt">Review input received from scoping team: </span><span style="font-size:11.0pt;color:windowtext"><a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit__;!!PtGJab4!r3KYPSUnxXxCgiSX4_hbeMBpmIRV-S1iG6x_nPjdaqcZloxfKGrEej5wMDqTtPZV5evYLFE7NQ$" title="https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit__;!!PtGJab4!r3KYPSUnxXxCgiSX4_hbeMBpmIRV-S1iG6x_nPjdaqcZloxfKGrEej5wMDqTtPZV5evYLFE7NQ$"><span style="color:#0563C1">https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit[docs.google.com]</span></a></span><span style="font-size:11.0pt"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l2 level2 lfo4"><span style="font-size:11.0pt">Scoping team input<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l2 level2 lfo4"><span style="font-size:11.0pt">Confirm next steps<o:p></o:p></span></li></ol>
</li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<ol style="margin-top:0in" start="4" type="1">
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo5"><span style="font-size:11.0pt">Confirm action items & next meeting (Thursday 9 December at 14.00 UTC)<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</body>
</html>