<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:269092870;
mso-list-template-ids:59680896;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:"Times New Roman";}
@list 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:855579373;
mso-list-template-ids:1690487120;}
@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:2091810448;
mso-list-template-ids:1812227536;}
@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;}
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, 17 February 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"><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>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">1. Scoping Team to review the Support Staff
<a href="https://mm.icann.org/pipermail/gnso-accuracy-st/2022-February/000253.html">
list of data sources for accuracy</a> and confirm that nothing is missing.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">2. Scoping Team to work asynchronously via the email list to further discuss the definition of accuracy and what changes might be necessary. (For current working definition/construct, please refer
to p. 12 of this <a href="https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit">
Google Doc</a>.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">3. Still outstanding for BC, GAC, ISPCP, and SSAC reps: 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
<b>page 25</b> at https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?pli=1# [docs.google.com]. 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.<o:p></o:p></span></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 #17</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 10 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">Continuing the work of last week<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">Many stakeholder groups have completed their homework, still waiting BC, GAC, ISPCP, SSAC<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">If we finish this part of our work early today, we will discuss the potential of gathering UDRP decision data that has been
discussed on the list<o:p></o:p></span></li></ul>
</li></ol>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="color:black;mso-list:l2 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:l2 level2 lfo2"><span style="font-size:11.0pt">Review of existing data sources - role in existing current situation & identifying possible gaps (see<a href="https://mm.icann.org/pipermail/gnso-accuracy-st/2022-February/000253.html" title="https://mm.icann.org/pipermail/gnso-accuracy-st/2022-February/000253.html"><span style="color:#0563C1">https://mm.icann.org/pipermail/gnso-accuracy-st/2022-February/000253.html</span></a>) <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">Further to Support Staff’s action item, Support Staff has compiled a separate list of data sources that have been referenced.<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">Many (if not all) were included as part of the briefing materials; however, now all are included in a dedicated document.<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">Scoping Team to please review and ensure that this is complete.<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:l2 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!uJaV6KUncve1BDErycPCyopXZUt5EBA6qC7fZmPfQA6_WmwBqyL18YAuuD6vyk39owZns06afmk$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit__;!!PtGJab4!uJaV6KUncve1BDErycPCyopXZUt5EBA6qC7fZmPfQA6_WmwBqyL18YAuuD6vyk39owZns06afmk$"><span style="color:#0563C1">google
doc [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"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RySG</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: This assignment was a challenge because
Ry Reps are still struggling against which standard to measure accuracy against – there is no current agreed-upon definition.
<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 are different ways to ask Rrs to report on their accuracy rates, such as ask Rrs to track email bounces from WDRP
notices. One challenge here is that we, as an accuracy scoping team, do not have a way of compelling registrars to provide this 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">Could have a third-party audit of existing data, but DPAs would need to be in place. While this is possible, there are challenges
with cross-jurisdictional transfers of 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">With respect to third-party audits and the issue of DPAs, instead of doing a random sampling, would it be better to focus
on domains that show up in OCTO reports – that may, on its face, have a higher chance of passing the legitimate interest test<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">Disagree – rather than looking at names that are so-called bad is not a comprehensive look at the ecosystem. Important to
have a holistic look into the DNS and not just zero in on alleged bad actors.<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">Doing scoping on what has already been identified as bad isn’t going to get us very far. Think that there could be a carefully-crafted
and narrow DPA exclusively for this purpose.<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 is a DPA between registries and registrars. This should be doable.<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 purposes have to be defined narrowly and the DPA needs to be crafted carefully – hard to say if this would be OK without
seeing the DPA. Any transfer of data across borders (as seen in recent Google analytics decision) leaves some question as to how this could be organized. A third party should probably be used, rather than ICANN doing it. Ultimately, this will not be the easiest
task. <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 group has been looking at data on the number of complaints ICANN gets. There is a difference of opinion on why that
number has dropped between pre-GDPR and post-GDPR. As we’re looking at easy data sets to get to, if we are looking at illegal activity, that may give us a heightened legitimacy for access to the 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">What is the standard for measurement – unclear if this is about how to measure something or what thresholds exist for how
good something is or how bad something is. There are basically two kinds of numbers that stick out: (1) number of domains viewed as abusive vs. (2) percentage of registrations per registry that are being used for malicious purposes – these two are different
numbers. For new gTLDs, the set of registrations is relatively small, but the percentage for some is relatively high, rather than .com – which has a large number of abusive domains but a small percentage overall. Need to be careful about where we focus our
attention. The drop in complaints from ICANN Compliance does not translate into a positive signal that accuracy rates have changed for the better.
<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 discussion started way back when discussing voluntary contributions from registrars since ICANN cannot compel registrars
to provide data. A DPA that would need to be voluntarily signed by certain registrars has very little merit. It’s unlikely to be signed by bad actors. If there is no benefit to a registrar, why would they spend money doing this? ICANN could certainly decide
to do audits of various sorts. Many companies have set up data protection authorities in certain jurisdictions to avoid cross-border data flow. In terms of audits of just domains that have shown abuse -this is a fine idea. Why is it that we want data? No need
to contact all 200,000,000 people but may want to contact the ones that have some relevance. Targeting may not give us a holistic picture, but it could give us a view into accuracy vs. registrant data. It may be accurate as data, but not contact information
for that registrant. <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 scope of this group is not abusive domain names, but looking at domain names involved in illegal activity could the
safest and legally viable data sampling to do.<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">Do not see how abuse stats b/w TLDs relate to accuracy. Abuse is not what we are looking at regardless of what the domain
name is used for. New gTLDs are, in general, more regulated than legacy TLDs. If new gTLDs have high abuse whereas .com has a moderate number of abusive domain names, that leads to the conclusion that more regulation does not lead to less abuse, or, the more
regulation = greater abuse. <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 two most abused gTLDs, 2 account for over 40% of abuse<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">If it seems like we need to get more data, this is perhaps a way to do this. Suggest that Rys and Rrs put their heads together
and see what data we have, who could be the aggregator of data and come up with something that could be a light scope.
<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 looks like only 3% of abuse deals with trademark infringement – this deals with specific automated detection system,
and the detection system excludes malicious abuse. What does compromised mean? Does that go beyond malicious?
<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">CPs, during ICANN 73, will have a session about abuse and distinguish if it is about maliciously registered domain names
or compromised domain names.<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">Appreciate that this group of Rrs and Rys would go back and think about what could be done, but it’s the age-old problem
– the problem is usually not with the Rrs and Rys that participate in ICANN – especially not the registrars that are represented here. If all Rrs do not participate, the data would be skewed.<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">Just because something is abusive is very prejudicial – this makes the assumption that inaccurate data means abusive data
– this should be looked at more holistically. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">IPC</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Shares opinions submitted by others such
as ALAC – concerned about time to determine whether goals are met. In terms of AFAV, this would be helpful if this were enforced. GAC used the definition for domain name registration data for the ARS – this has been suspended, but its definition did also include
identity (not just operability and syntax). Identity verification should be considered. ICANN org should be the entity that audits compliance. There were previous references to the NORC group that was the prototype for ARS and it included validation and they
private and public sector validation experts. Perhaps we could use these experts again.
<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">When it comes to how to measure accuracy, there is a suggestion to have ICANN compliance do an audit that accuracy measures
are being followed. Is that correct? <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">Thought validation or verification experts from the public and private sector might be useful to assist ICANN in this exercise.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level2 lfo1"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ALAC</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> – This is a different question – confused
by how the scoping team is supposed to be running studies – if it is, the scoping team is short on time.
<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">If there are recommendations on what we are supposed to do, we can adjust the timeline accordingly.<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">Group seems to be conflating whether people are adhering to the RAA and whether information is accurate. The RAA is very
targeted and only looks at accuracy for some fields for new and updated names. We are not in a position to compel registrars to do a full audit of their own data. If there is a belief that this is out of scope and that ICANN does not have the right to do it,
we need to get clarity on that. <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">Most domain names fell under the 2013 RAA due because they were transferred or deleted. Only a small subset of domain names
remained under the grandfathered rules – also names registered a long time ago usually do not present an accuracy issue<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">If the group comes up with a mechanism for measuring accuracy, it is important to get the results of this to get to the
other parts of the assignment <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 would this look like from a process standpoint?<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">Procedurally, once this group has identified the guardrails or scope of any type of study, this would need to be documented
and presented to the GNSO Council first, and this would need to be approved by the Council – it would then be submitted to the Board or Org (this presumes that it would be a sizeable resource). Ultimately, that request would be evaluated by the Board and Org
to determine feasibility and funding. As it stands right now, this would be an unplanned expense – the planning and financing team would have to determine where the funding would come from. This may not be the exact process; this is how the process worked
for EPDP Phase 1 and 2.<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 third charge to the scoping team – undertake an analysis based on data from assignment 2 (the measurement of accuracy).
It’s critical to have good data that we can take concrete and actionable steps against.<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 could take over six months if we commission a study like the NORC study, assuming it’s all possible and viable to do
that, this would be a very significant amount of time. In terms of what RDS review team found, understanding is that there are still significant domain names that are not treated as new and not subject to 2013 RAA requirements.
<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">If we must pause and wait for results of a study in order to get important data, that would be worth it.<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">Have heard the argument that we need data to provide concrete and helpful recommendations. One option would be to stall
work. One problem is to check the magnitude of the problem. The fact that there is an inability to check whether there is an accuracy issue – for that, we do not need data – we need to think of ways to tackle this issue.<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">Group could work asynchronously on the definitional issue on the mailing list.
<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:l2 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:l1 level1 lfo3"><span style="font-size:11.0pt">Confirm action items & next meeting (Thursday 17 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>