<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;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.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:386299635;
mso-list-template-ids:-2023302018;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-start-at:0;
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 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:513808326;
mso-list-template-ids:-1889093758;}
@list l1:level1
{mso-level-start-at:2;
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:1315838445;
mso-list-template-ids:-1604935290;}
@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-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;}
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 meeting will be Thursday, 10 February, 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"><u><span style="font-size:11.0pt;color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></p>
<p class="MsoNormal"><u><span style="font-size:11.0pt;color:black">Action Items: <o:p>
</o:p></span></u></p>
<p class="MsoNormal"><u><span style="font-size:11.0pt;color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">1. Still Outstanding: By Wednesday,<span class="apple-converted-space"> </span>9 February, Scoping Team members who have not yet completed the assignment to consider what is needed and from whom
to obtain information identified as necessary to measure whether current goals are met. Additionally, scoping team members to begin identifying specific ways in which measurement can be undertaken. (see<span class="apple-converted-space"> </span></span><span style="font-size:11.0pt;color:#FEFEFE"><a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?pli=1__;!!PtGJab4!vZAQj7dGAJ_P1Wm4CJGChelMHIKPNhd86K9-r-2Dj1qQXvbZQSNjpJ42GLLaouEFy29-akBzMQ$" title="https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?pli=1__;!!PtGJab4!vZAQj7dGAJ_P1Wm4CJGChelMHIKPNhd86K9-r-2Dj1qQXvbZQSNjpJ42GLLaouEFy29-akBzMQ$"><span style="color:#6EB5FB">https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?pli=1#</span><span class="apple-converted-space"><span style="color:#6EB5FB;text-decoration:none"> </span></span><span style="color:#6EB5FB">[docs.google.com]</span></a></span><span style="font-size:11.0pt;color:black">.
*For groups that referenced ARS, please consider ICANN org’s recent memo in your response: https://mm.icann.org/pipermail/gnso-accuracy-st/2022-January/000236.html.*</span><u><span style="font-size:11.0pt;color:black"><o:p></o:p></span></u></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 #16</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 February 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:l0 level1 lfo1"><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:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There are some groups that have yet to complete the assignments. Thus far, only Rrs and Rys have completed the assignment
in advance of today’s meeting. Please complete the assignment as soon as possible if you have not.<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:l1 level1 lfo2"><span style="font-size:11.0pt">Measurement of accuracy (60 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 lfo2"><span style="font-size:11.0pt">Review of existing data sources - role in assessing current situation & identifying possible gaps<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:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">A lot of what was provided in the gap analysis were broad statements or requests to incorporate different parts of the RAA.
In short, some input was fact-based, and that input was the core of what problems exist related to accuracy. Would it be possible for the staff support team to group the fact-based input into a document for the group to review?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The only objective data is some of the reports from the UDRP panelists who have cited inaccurate data.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Support Staff picked out references from the gap analysis and identified five different pieces, all of which were referenced
in the index of resources, the most recent being the InterIsle report. A question from staff – what would the group like to do next with this information?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">It is important to understand the current landscape. If no group has provided factual information, it’s unclear what the
group is doing or how it can productively move forward. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Confused that CPs are asking for other constituencies to provide data on inaccuracy, but how can these groups go about doing
so when very little data, if any, is public. The most recent report seems to be the NORC study. How are these groups realistically expected to provide the requested factual data?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The homework assignment is about having this conversation: everyone identified what they believed the current accuracy requirements
are, and how accuracy can be measured with the current requirements. Rrs and Rys have provided additional ideas. Other groups have suggested that ARS should be restarted, but it would be helpful if the groups that suggested this would look at this suggestion
in the context of the memo ICANN org recently provided. If it should be done, what hurdles would need to be overcome? Then the next step would be to identify gaps. Many members mention problems, but the problems need to be documented and then suggestions of
how to move forward need to be suggested – for example, is further policy work necessary? Is there an approach to get data to show that current accuracy requirements are being met or not being met.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not aware of post-2018 data, but some are asserting that there is a problem. Is there, for example, a tracking of how many
times you have unsuccessfully contacted someone and could not because of inaccurate data. The problem needs to be quantified rather than a general feeling that Whois data is inaccurate.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There have been a number of instances in UDRP decisions where the panelist has cited inaccurate data. If we show data points,
is that enough? There is data that shows that there were issues prior to GDPR. That data became inaccessible, and prior to GDPR, ICANN compliance reported inaccuracy being the number one source of complaints. It is a heavy lift to discover inaccurate data.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is a classic chicken/egg scenario. INTA or IPC members may provide reports of inaccuracy, but other members have expressed
that anecdotal evidence is unwelcome in this group. Additionally, some parties do not want to disclose their identities publicly due to exposure. This is a very finite, targeted problem that we have.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is an accuracy scoping team, but getting access to data is very hard. There is an inextricable link b/w access and
accuracy. There is a three-part process. If someone has a problem and needs to make contact with someone, can they get access to information. Yes or no? If yes, and they receive no response, is it b/c someone chooses not to respond or b/c the data is inaccurate?
What percentage of the challenges to reach someone are b/c you cannot get any access to info? What percentage of non-response is because of no response vs. inaccurate data? Some partitioning of this data would be helpful.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What homework have certain groups not completed?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Cannot demonstrate that there are certain problems because the data is no longer publicly available – not sure how this
can be proven. In terms of the reasons why someone may not respond – there is an InterIsle study that demonstrates that in a significant number of cases, there is contact information problems. Asking these groups to verify that there is a problem sounds like
a Catch-22.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sympathize with other members – the task of a scoping team is to identify a problem, and if there is a problem, a PDP can
be launched to address the issue. It’s impossible to create a solution to a problem that may or may not exist based on outdated data. Without data that corroborates that there is a problem, we cannot move forward.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">May be helpful to provide examples without identifying companies. Can you provide dates that you requested the info, did
the CP respond, was there a bounce back, etc. This would help understand the scope of the problem on the requester side. This is private personal data, and CPs are complying with the Temp Spec and the law.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The disconnect here is that fraudulent data is being labelled as accurate. Facts of many UDRP cases center around fraud,
phishing, etc. The system currently allows fraudulent registration of inaccurate data. The system encourages the submission of fraudulent data.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Cannot readily assume that fraudulent information that is technically accurate has gone away post-GDPR. Whois is no longer
public – there is no Whois. Saying there is no problem because it can’t be proven when it was problem prior to GDPR is a problem. The company that does provide proof is often dismissed.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">All action items are posted on the wiki and available for the group to review – these are sent out on in the notes and agenda
reminders. On p. 25 of the gap analysis doc, on the left-hand side, Support Staff has filled in the group’s responses to Q2. Groups now need to drill down on the previous suggestions they made and provide this info in the right-hand column. Please also review
the memo provided by ICANN org on ARS and consider this in your response. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The question should be asked re: controllership to have an answer that is useful to the team.
<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:l1 level2 lfo2"><span style="font-size:11.0pt">Review input received on <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit__;!!PtGJab4!vEtbz9rM3harxSjAzgHhoYhB_4_wtukXveuNAYdmKZn0Q4RbVoGq2WwDL_iJwQlRWUZKiwjGyzI$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit__;!!PtGJab4!vEtbz9rM3harxSjAzgHhoYhB_4_wtukXveuNAYdmKZn0Q4RbVoGq2WwDL_iJwQlRWUZKiwjGyzI$"><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>
</ol>
<ol start="1" type="1">
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RrSG: Registrars could report on accuracy measurements – difficulties – there is no requirement for registrars to track
this and put the data together in this kind of manner. Will this group accept data provided by registrars? Another option could be to have a third party measure data, but this would necessitate a data protection agreement. Could also look at number of complaints
processed by ICANN compliance, but based on others’ comments, it appears these complaints are not submitted.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Even if RAA provisions are followed scrupulously, there is a still a substantial amount of inaccurate data.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hope to see the evidence supporting this claim in the homework response.
<o:p></o:p></span></li></ul>
</ol>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="3" type="a">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2"><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:l2 level1 lfo3"><span style="font-size:11.0pt">Confirm action items & next meeting (Thursday 10 February at 14.00 UTC)<o:p></o:p></span></li></ol>
<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>