<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:161507374;
mso-list-template-ids:-389020996;}
@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:292098915;
mso-list-template-ids:-490703504;}
@list l1:level1
{mso-level-start-at:3;
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:815806577;
mso-list-template-ids:632598622;}
@list l2:level1
{mso-level-start-at:5;
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:1025714621;
mso-list-type:hybrid;
mso-list-template-ids:1847599138 858710670 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l3:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;}
@list l3:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l3:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l3:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l4
{mso-list-id:1091970913;
mso-list-template-ids:2012259020;}
@list l4:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level3
{mso-level-start-at:2;
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 l4:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@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:1500348374;
mso-list-template-ids:703608002;}
@list l5:level1
{mso-level-start-at:4;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level2
{mso-level-number-format:alpha-lower;
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:1627587834;
mso-list-template-ids:-1509808286;}
@list l6:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level3
{mso-level-start-at:13;
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 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;}
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">Dear RDA Scoping Team members,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The next RDA Scoping Team meeting will be Thursday, 11 November at 14:00 UTC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Marika, Berry, and Caitlin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></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 start="1" type="1">
<li class="MsoListParagraph" style="color:black;mso-list:l3 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RDA Policy Support Team to distribute call for volunteers for alternates to SO/AC/C leadership. (complete)<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RDA Scoping Team members to review the most recent working definition for accuracy (<a href="https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit">p.
12 of the Assignment 1 background briefing doc</a>) and provide proposed edits or alternate definitions by COB
<b><u>Wednesday, 10 November</u></b>. Once the Team agrees to the baseline working definition, groups can begin working on their proposed “aspirational” or “desired future state” definitions.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l3 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RDA Scoping Team members to populate questions to ICANN org in the
<a href="https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit">
dedicated Google Doc</a> over the coming weeks with a goal to finalize questions by Friday, 27 November.
<b><o:p></o:p></b></span></li></ol>
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:black">Registration Data Accuracy Scoping Team – Meeting #4</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 4 November at 13.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:l4 level1 lfo2"><span style="font-size:11.0pt">Welcome & Chair Updates<o:p></o:p></span>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="color:black;mso-list:l4 level2 lfo2"><span style="font-size:11.0pt">Council non-objection to appointing alternates and vice-chair<o:p></o:p></span>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Groups can notify GNSO Support Staff if they intend to appoint an alternate<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">At this point in time, not going to undertake appointment of a vice-chair, but this has been approved<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l4 level2 lfo2"><span style="font-size:11.0pt">Appointment of Council liaison<o:p></o:p></span>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Olga Cavalli has been appointed as the GNSO Council Liaison to the Scoping Team<o:p></o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l4 level2 lfo2"><span style="font-size:11.0pt">Adjustment of call time & duration from next week onwards to accommodate for DST<o:p></o:p></span>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Going forward, the meetings will take place on Thursdays at 14:00 UTC for 90 minutes, with the intent to end meetings after
60 minutes. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This schedule does include Thursday, Nov 25 (U.S. Thanksgiving)<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Over the next couple of weeks, here is the plan:<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Today – hope to reach rough consensus on the current definition of accuracy<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Pending success on that, the Team will have
<b><u>four weeks</u></b> to go back to their respective groups and produce what is called an “aspirational definition” on where they think the definition of accuracy should evolve to.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">During these four weeks, the Team will use that intervening time to produce questions to ICANN org.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">These questions need to be vetted before the ICANN org presentation, so please submit them by the last week of November<o:p></o:p></span></li></ul>
</li></ol>
</li></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="2" type="1">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">Proposed Work plan & timeline<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">Review proposed work plan & timeline<o:p></o:p></span></li></ol>
</li></ol>
<ol start="1" type="1">
<ol start="3" type="a">
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Many on this team are familiar with the PDP 3.0 principles for project management, i.e., defining and measuring the work
ahead of us. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The Leadership Team was leaning toward an aspirational delivery of a report to the GNSO Council by ICANN75 (mid-September).<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The Leadership Team will forward the project plan to the GNSO Council on Monday, 8 November (the motions and documents deadline).
It will be an AOB item for the Council meeting.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Each month, we will produce a project package, including the dashboard currently shown on screen, the project plan, and
the elements/topics the Team is discussing.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There are four assignments in front of the Team, per the Council’s instructions. The Team will work assignments 1 and 2
before working 3 and 4. Assignments 1 and 2 will be worked in parallel for 12 business weeks (roughly through the end of January).
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">One challenge in putting this plan together is that it is nebulous what the scope of work will look like; accordingly, February
is planned to scope Assignment 3. The Council instructions provide a general direction, but the Team needs to drill own on defining the scope of Assignment 3 (for example, is a survey needed?)<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The output of the deep dive into Assignment 3 will result in an update to the Council re: the sizing of the work ahead of
the Team.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If necessary, the Team can communicate back to the Council if more or less time is needed.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If the group is on track after ICANN73, the Team will endeavor to deliver the report to the Council by September 2022.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The previous talking points will be included in the provision of the project plan to the Council.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The Group expressed concerns with how to account for the unknowns in Assignment 3, so the current plan includes some caveats
and flexibility.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Scoping Team Input:<o:p></o:p></span>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l4 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In looking at the whole process, there is a lot of emphasis regarding the criteria and measurement of accuracy. What are
the purposes that are intended to be satisfied? In other words, if these requirements are satisfied, are the requirements fit for purpose? Does the group have an explicit and direct address to that issue?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">As a Scoping Team, the Team is afforded latitude; however, the Team should be cautious about relitigating other aspects
such as access. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If you called a phone number and it rang, is that accurate data? Most judges would probably say no. Is there a correlation?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">For the purpose of today’s conversation, are there any concerns with the timeline?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question about the tasks: different ideas of what we are putting out from this group. The Scoping Team is not something
a PDP is doing. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l4 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Getting back to the timeline, what we have proposed here – over the next three months, the Team will be working concurrently
on assignments 1 and 2. Today, the group will begin a substantive discussion on what the definition is today and get rough consensus on what that definition is today. From there, the Team will spend the next four weeks discussing within their groups on what
the aspirational definition is. <o:p></o:p></span></li></ul>
</li></ul>
</ol>
</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">Confirm next steps<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:l1 level1 lfo4"><span style="font-size:11.0pt">Working definition of accuracy<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;color:black">From assignment #1: “<i>The Scoping Team shall, with reference to the resources that will be included in the index of relevant resources cited below, consider whether there
is an agreed definition of registration data accuracy and, if not, consider what working definitions should be used in the context of the Scoping Team's deliberations. Particular attention should be given to the definition that ICANN Compliance employs for
“accuracy” in ICANN’s contracts. Note, this does not preclude any subsequent effort from formalising the definition(s) that should be applied in the context of any existing and/or new accuracy requirements that may be developed”.</i><o:p></o:p></span></p>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="color:black;mso-list:l6 level2 lfo5"><span style="font-size:11.0pt">Review input received on definition (see page 12 - <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit__;!!PtGJab4!rMGjD3pg-FDGYtdust0YxFxfqtVJwh4GuKXuq74OJ87lh9_-siC744JSZefaN-aTx7sMrBbigtQ$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit__;!!PtGJab4!rMGjD3pg-FDGYtdust0YxFxfqtVJwh4GuKXuq74OJ87lh9_-siC744JSZefaN-aTx7sMrBbigtQ$"><span style="color:#0563C1">https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit
[docs.google.com]</span></a>)<o:p></o:p></span>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sarah and Michael had an exchange on the definition
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The latest definition proposed by Sarah appears on p. 12<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The group’s task is to determine if contractual data accuracy obligations are effective at ensuring accuracy levels. The
definition is one part of this and even if the definition is perfect, this does not address effectiveness or scope.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Subpart f of the Whois Accuracy Program Specification – there is a difference in technical and legal speak. Affirmative
response means more than operational validation. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The requirements for operational validation discussed affirmative response; do not think the phone just ringing would not
meet the current requirements.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not understand where the example of the phone just ringing comes from. Not sure what an affirmative response actually
is – that is determined b/w ICANN compliance and the relevant registrar. The verification method is included in the RAA definition. Have hesitation about incorporating the specific examples because a definition should stand on its own without examples. Agree
that it is important to have a common understanding of the difference between validation and verification.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Where is the relationship between the requirement and whether it serves the purpose?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agree that it’s important to have a good foundation to begin on. Here is the definition, here is current enforcement, here
is the scope of where the PDP will lie. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question 3 could be reviewed before 1 and 2.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If there is a problem, that is what assignment 4 accounts for. One reason the group has been given some strong suggestive
guidance is that after the analysis is undertaken, that will drive #4. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">It is not just ensuring that the phone is ringing, it is communicating with the RNH.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What is the standard implementation of this requirement for operational accuracy. It is hard to answer that because have
not done a survey of all registrars. Email verification is likely more common than a phone verification. Familiar with a text with a link to a webpage. It is, however, difficult to answer the standard overall method for registrars. If that is something the
group determines is needed, this could be done via a survey of providers, but this may be out of scope.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is there anyone who would like to update the definition as it appears now?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In the current definition, it may be helpful to reference the purpose of the definition by citing the relevant portion of
the ICANN Bylaws. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In the group’s preparatory meeting, two of three elements of the definition are included. The third element (verification
that there is a person at the end and that person is the RNH) is not – there is a third element that should be included. The third prong is not recognized anywhere; this should not be discarded.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The above appears to be identify verification – such as RNH being required to send in a photo ID and that being verified.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Text from ICANN org enforcement of accuracy pre and post-GDPR: “However, if the complaint is about identity (e.g., the registrant
is not who they say they are), Contractual Compliance may ask the registrar to provide further information concerning their findings and the results of their investigation specific to the facts of the complaint.”<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Registrars have been doing a lot of visible heavy lifting. Proposal to strike “<s>shall strictly be defined</s>” Instead,
accuracy “is” syntactical accuracy of the registration data elements processed by Registrars. Also, in line with the text from the GAC Communique, proposal to add “and registries”. In other words, “Accuracy is syntactical accuracy of the registration data
elements processed by Registrars and certain Registry Operators” provided by the Registered Name Holder or Account Holder as well as the operational accuracy of either the telephone number or the email address.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What is ICANN org’s authority for doing an identity check?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is a question to address to compliance as this is confusing, even to registrars<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Important to ensure this is a stable and clear definition
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Text from ICANN72 GAC Communique: The GAC considers that assignments iii) and iv) are particularly important for the purpose
of assessing possible improvements of accuracy of registration data. The GAC is looking forward to exchanging with other constituencies not only on the definition and measurement of accuracy but also on solutions on how to enhance accuracy. The GAC gives particular
importance to the verification, validation and correction of all registration data by registrars, and certain registries, in line with their contractual obligations, and supports rigorous monitoring and enforcement of such contractual obligations by ICANN.
The GAC stresses the importance of delivering on all four tasks in a timely and effective manner.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ICANN Compliance may ask for further information on the registrar’s findings – this is not asking the registrar to do something
new <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Compliance will see if registrar has taken reasonable steps
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">When the Team considers an aspirational definition, consider this as a future state/future solution. It is important not
just to focus on the text of the aspirational definition, but also to accompany the text with (i) the problem or concern the aspirational definition is intended to address; and (ii) how that problem can be measured / confirmed. This can be included in clear
bullet points. For example, some have suggested that identify verification needs to be included.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l6 level2 lfo5"><span style="font-size:11.0pt">Consider whether in addition to working definition focused on current application, input should be requested on aspirational definitions to identify perceived gap
between current definition and aspirational definition<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l6 level2 lfo5"><span style="font-size:11.0pt">Scoping team input<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l6 level2 lfo5"><span style="font-size:11.0pt">Confirm next steps<o:p></o:p></span></li></ol>
</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:l5 level1 lfo6"><span style="font-size:11.0pt">Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System<o:p></o:p></span>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="color:black;mso-list:l5 level2 lfo6"><span style="font-size:11.0pt">Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level2 lfo6"><span style="font-size:11.0pt">Input received from scoping team to date: <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit__;!!PtGJab4!rMGjD3pg-FDGYtdust0YxFxfqtVJwh4GuKXuq74OJ87lh9_-siC744JSZefaN-aTx7sMyhpiS3Y$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit__;!!PtGJab4!rMGjD3pg-FDGYtdust0YxFxfqtVJwh4GuKXuq74OJ87lh9_-siC744JSZefaN-aTx7sMyhpiS3Y$"><span style="color:#0563C1">https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit
[docs.google.com]</span></a><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level2 lfo6"><span style="font-size:11.0pt">Scoping team input<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l5 level2 lfo6"><span style="font-size:11.0pt">Confirm deadline for submission of questions<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="5" type="1">
<li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo7"><span style="font-size:11.0pt">Confirm action items & next meeting (Thursday 11 November <b>at 14.00 UTC</b>)<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>