<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:102383925;
mso-list-template-ids:-1771679932;}
@list l0:level1
{mso-level-start-at:3;
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:492766083;
mso-list-template-ids:-1335059340;}
@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-number-format:alpha-lower;
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:541209341;
mso-list-template-ids:-1023224142;}
@list l2:level1
{mso-level-start-at:2;
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:1359744657;
mso-list-template-ids:593379228;}
@list l3:level1
{mso-level-start-at:5;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-number-format:alpha-lower;
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:1590042312;
mso-list-template-ids:1382063476;}
@list l4:level1
{mso-level-start-at:6;
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:1640111320;
mso-list-type:hybrid;
mso-list-template-ids:1573398234 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l5:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l5:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l5:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l6
{mso-list-id:1924800645;
mso-list-template-ids:-1092684648;}
@list l6:level1
{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-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-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@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;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">As a reminder, the next meeting will be on Monday, 7 March at 16:30 UTC. Please remember to registrar for ICANN73 in order to access the details for this session.<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">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>
<ol start="1" type="1">
<li class="MsoListParagraph" style="color:black;mso-list:l5 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In advance of the ICANN73 RDA Scoping Team Session on Monday at 16:30 UTC, RDA Scoping Team Members to review the Gap Analysis
Proposal Review. (https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit) Note: this document was compiled by Support Staff in an effort to distill the proposals made by Scoping Team Members, including upsides and downsides noted by either
the proposer or other team members in subsequent discussions. The document is not meant to restrict the group into choosing one proposal, but rather, the group should review all proposals and see which proposals provide a viable path to forward progress.<o:p></o:p></span></li></ol>
<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 #20</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 3 March 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:l6 level1 lfo2"><span style="font-size:11.0pt">Welcome & Chair Updates (10 minutes)<o:p></o:p></span>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="color:black;mso-list:l6 level2 lfo2"><span style="font-size:11.0pt">ICANN73 Working Session proposed agenda:<o:p></o:p></span></li></ol>
</li></ol>
<p class="MsoNormal" style="margin-left:85.05pt;text-indent:-14.15pt"><span style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> </span><span style="font-size:11.0pt;color:black">Brief
overview of background and current status<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:85.05pt;text-indent:-14.15pt"><span style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> </span><span style="font-size:11.0pt;color:black">Continue
deliberations (e.g., accuracy working definition, review of existing data sources)<o:p></o:p></span></p>
<ol start="1" type="1">
<ol start="1" type="a">
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Will go over table of pros, cons, etc.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Marc A. suggested this idea during the last meeting – to look through the input received by different groups regarding how
data could be obtained. Support Staff went through the input and distilled a number of specific proposals. In some cases, similar proposals are grouped together. When upsides and downsides were identified either in the proposal or in subsequent discussions,
these have been included. Staff has also proposed next steps in some instances. <o:p>
</o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Note: the document isn’t designed as a “choose one” – multiple proposals could be chosen; the team is now asked to look
at which proposal(s) could be viable<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Action item: RDA Scoping Team to review the document (<a href="https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit">https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit</a>)
in advance of Monday’s ICANN73 session.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This document is a good way of getting into the gap analysis.<o:p></o:p></span></li></ul>
</ol>
</ol>
<p class="MsoNormal" style="margin-left:85.05pt;text-indent:-14.15pt"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:85.05pt;text-indent:-14.15pt"><span style="font-size:11.0pt;font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> </span><span style="font-size:11.0pt;color:black">Q
& A session<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="2" type="1">
<li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo3"><span style="font-size:11.0pt">Measurement of accuracy (10 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 lfo3"><span style="font-size:11.0pt">Review remaining input received on <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit__;!!PtGJab4!tt60RLv9dTD650zoDH0T_jOfUStCLQ76hNSEpWSj5_RJndv9Kkz6AuQEzwJvpPjTnQpfaHTMKCI$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit__;!!PtGJab4!tt60RLv9dTD650zoDH0T_jOfUStCLQ76hNSEpWSj5_RJndv9Kkz6AuQEzwJvpPjTnQpfaHTMKCI$"><span style="color:#0563C1">google
doc</span><span style="color:#0563C1;text-decoration:none"> </span><span style="color:#0563C1">[docs.google.com]</span></a>, see page 25 - How and by whom can it be measured whether current goal(s) of existing accuracy requirements are met?<o:p></o:p></span></li></ol>
</li></ol>
<ol start="1" type="1">
<ol start="1" type="a">
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ISPCP –
<o:p></o:p></span>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l6 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RAA spells out accuracy requirements – build on this<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Build on third party reports on inaccurate data<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Could also collect and compare different data points with other registrars’ data points
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Some of this work is harmed by the lack of DPAs – ICANN will not be able to see the actual data, but the methodology can
be agreed upon and ICANN audits could confirm if the registrar is applying the correct methodology<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There is likely a joint controller situation b/w ICANN and CPs, and JCA could spell our roles and responsibilities with
respect to accuracy<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">When it comes to rectifying data, registrars have the largest pool of data to assist with this<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Role of resellers: probably have been one of the overlooked and unaccounted links in the domain name ecosystem<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level4 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Re: red herring – a lot can be done by drafting additional data processing agreements, but what are we trying to achieve?
During Phase 1 of EPDP, there is a recommendation for ICANN and CPs to come up with draft protection arrangements. For a DPA, you can allocate functional responsibilities for the joint controllers.<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:l2 level2 lfo3"><span style="font-size:11.0pt;color:windowtext">Confirm next steps</span><span style="font-size:11.0pt"><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="3" type="1">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4"><span style="font-size:11.0pt">Accuracy working definition / construct (30 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 lfo4"><span style="font-size:11.0pt;color:windowtext">Review</span><span style="font-size:11.0pt"> input received (see </span><span style="font-size:11.0pt;color:windowtext"><a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1JGdNLjOjhmJnj-iDaGvcVnv1gZ5tQu5C/edit__;!!PtGJab4!tt60RLv9dTD650zoDH0T_jOfUStCLQ76hNSEpWSj5_RJndv9Kkz6AuQEzwJvpPjTnQpfh1YQT5s$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1JGdNLjOjhmJnj-iDaGvcVnv1gZ5tQu5C/edit__;!!PtGJab4!tt60RLv9dTD650zoDH0T_jOfUStCLQ76hNSEpWSj5_RJndv9Kkz6AuQEzwJvpPjTnQpfh1YQT5s$"><span style="color:#0563C1">https://docs.google.com/document/d/1JGdNLjOjhmJnj-iDaGvcVnv1gZ5tQu5C/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">
<ol start="1" type="a">
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">For clarity, the 2013 RAA also includes all consensus policies</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">ICANN Compliance did respond to the draft construct; the response did not change the requirements, but
rather, explains when the requirements are tested</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Based upon the requirements set forth in 2013 RAA, what are potential changes or enhancements for the group
to consider?</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Thought team was asked to comment on the definition proposed by the RrSG – seems that now we are discussing
how the 2013 RAA is currently implemented. These are different things, and members may have responded differently based on what they thought the assignment was.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">There is an inherent confusion in the highlighted assignment: there is a difference b/w what is currently
required contractually and what is or what should be a working definition as a task of this accuracy scoping team</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Should consider using the term data quality instead of data accuracy – accuracy has a binary quality –
what this group is talking about is whether it is formatted correctly, updated in a reasonable timeframe, etc. This implies a role for ICANN that has yet to be defined in a DPA through the parties. ICANN has made progress in how it sees itself, but the details
of that are still muddy since the 2013 RAA was hatched without any regard to data protection law. Some issues are on the other side of the picket fence. If this were a negotiated policy, ICANN could argue that it is not a controller.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">The problem is when we talk about accuracy and requirements, these are not the same thing. To be accurate
to contactability – when Whois was started, the goal was contactability, so accuracy seems to be can someone be contacted. The requirements that have been put in place to achieve the accuracy are not accuracy in and of themselves. Are these contacts contactable?
Think what this question was intended to mean: Are there additional requirements that the RrSG did not include that ICANN org included in their comments?</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Thought working definition meant what the current definition is, not necessarily what it should be. Once
current definition is established, the team can review if changes are needed</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">The group has struggled with the use of working definition. Important to take note that reference to a
working definition is part of the first assignment – this gets to the understanding of the current situation – this allows the group to move to the second assignment – how is this currently measured? There needs to be agreement on what the current requirements
of enforcement are. Rrs came forward with current requirements; ICANN responded. Having looked at the proposals here, some are jumping ahead to what they would like the definition to be, but this is about what is currently required and enforced so that we
can use that as the benchmark over whether current requirements are being met.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">To facilitate and avoid confusion – refer to it as a current description of obligations</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">When this group started, the RrSG put forward a definition based upon interpretations of 2013 RAA requirements.
Yesterday, in a message, started with a presumption that this is a binary process. One definition of accuracy is binary – it is either accurate or inaccurate. Syntactical and operational accuracy of one element. Feedback from Compliance regarding its standard
operation procedures – this was not just limited to syntactical and operational accuracy. In response to Mickey Mouse, the term “patently false” was used. What this group needs to be focusing on – what is the grey area here? That is part of the gap analysis.
This analysis will help guide the group through assignments 3 and 4. The group is not excluding here; instead, taking the analysis and gathering what the current state is, see if there is a gap, and provide a path forward.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Current RAA has not been revised to look at whether requirements comply with the GDPR – when will that
be done and how? Is that within the scope of this team? Do not think so.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">For example, identity accuracy is a difficult term, it is not a requirement for registering a domain name.
Do not need identity accuracy to register a domain name. </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Main requirement for CPs is to accurately process data as it is inputted by the registrants.
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">There is no absolute bar against certainty about the identity of a registrant – that is a current decision
that has been made, and it’s a perfectly rational decision, but it’s also a perfectly rational position to make requirements regarding who, in fact, the registrant is. Trying to draw a very firm line that precludes stricter requirements is a policy discussion.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">This scoping team was not looking at what GDPR requires – what we have today is currently above GDPR
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">There appears to be a global platform that permits anyone to be anyone else without any preventative measures
taken – it’s as if a blind eye is turned to domain registration. Why should accuracy not include truth?
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Accuracy, in and of itself, is a registrant obligation. Registrars have to act upon inaccurate information
when there is evidence of this. No one is saying the information is accurate other than the registrant.
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">The purpose is contactability; now others are suggesting it’s contactability and identity. Accuracy today
is geared toward contactability. </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">The comment that ID accuracy would promote crime is incorrect – as recognized in early documents in 2000
and 2005 clearly dealt with identity validation – not sure where this got lost along the way. The fact is that everything has evolved since 2013 – criminals and cyber-squatters have evolved – there is a need for this policy to evolve to create preventive aspect
from filing fraudulent registration data.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">These comments should be discussed later and not here – some have noted that questions would have been
answered differently if they understood the assignment better.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">As the group goes forward, would be helpful if groups can update what their answer should have been.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l6 level3 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">RDA Scoping Team Members to update their answers based on the updated question: Based on the feedback from
ICANN org, what updates, if any, should be made to the RrSG proposed “current state” definition so that it accurately describes the current requirements and enforcements of these requirements. (Note: question was updated to clarify the original assignment.)</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li></ul>
</ol>
</ol>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="2" type="a">
<li class="MsoNormal" style="color:black;mso-list:l0 level2 lfo4"><span style="font-size:11.0pt;color:windowtext">Confirm next steps</span><span style="font-size:11.0pt"><o:p></o:p></span></li></ol>
</ol>
<p class="MsoNormal" style="margin-left:.5in"><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">Review of existing data sources (30 minutes)<o:p></o:p></span>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo5"><span style="font-size:11.0pt">See </span><span style="font-size:11.0pt;color:windowtext"><a href="https://community.icann.org/download/attachments/173703498/Gap%20analysis%20-%20data%20sources%20-%2028%20January%202022.docx?version=1&modificationDate=1645104154000&api=v2" title="https://community.icann.org/download/attachments/173703498/Gap%20analysis%20-%20data%20sources%20-%2028%20January%202022.docx?version=1&modificationDate=1645104154000&api=v2"><span style="color:#0563C1">compilation</span></a></span><span style="font-size:11.0pt"> developed
by Staff Support Team as well as overview of <a href="https://community.icann.org/download/attachments/173703498/From%20the%20Phase%202%20Cycle%206%20Report%20-%2024%20Feb%202022.docx?version=1&modificationDate=1646036997957&api=v2" title="https://community.icann.org/download/attachments/173703498/From%20the%20Phase%202%20Cycle%206%20Report%20-%2024%20Feb%202022.docx?version=1&modificationDate=1646036997957&api=v2"><span style="color:#0563C1">ARS
Cycle 6 findings</span></a><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo5"><span style="font-size:11.0pt">Team to consider these existing data sources and role in assessing existing current situation & identifying possible gaps<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo5"><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="5" type="1">
<li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo6"><span style="font-size:11.0pt">Additional questions for ICANN Compliance (10 minutes) (see <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit?pli=1__;!!PtGJab4!tt60RLv9dTD650zoDH0T_jOfUStCLQ76hNSEpWSj5_RJndv9Kkz6AuQEzwJvpPjTnQpfzCfzxoQ$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit?pli=1__;!!PtGJab4!tt60RLv9dTD650zoDH0T_jOfUStCLQ76hNSEpWSj5_RJndv9Kkz6AuQEzwJvpPjTnQpfzCfzxoQ$"><span style="color:#0563C1">https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit?pli=1
[docs.google.com]</span></a>)<o:p></o:p></span>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="color:black;mso-list:l3 level2 lfo6"><span style="font-size:11.0pt">Introduce questions (Alan, Michael)<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l3 level2 lfo6"><span style="font-size:11.0pt">EPDP Team input<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l3 level2 lfo6"><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="6" type="1">
<li class="MsoNormal" style="color:black;mso-list:l4 level1 lfo7"><span style="font-size:11.0pt">Confirm action items & next meeting (ICANN73 - Monday 7 March at 16.30 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>