<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:614217004;
mso-list-template-ids:1038486422;}
@list l0:level1
{mso-level-start-at:4;
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:1109351128;
mso-list-template-ids:-957848166;}
@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:1845977753;
mso-list-template-ids:-810773360;}
@list l2:level1
{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-start-at:16;
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 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:2044164985;
mso-list-template-ids:944278486;}
@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-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;}
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">As a reminder, the next meeting will be Thursday, 24 March 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><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">1. Brian Gutterman (ICANN org liaison) to transmit questions 3 - 7 (https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit?pli=1) to internal ICANN org colleagues for further
guidance. <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">2. Support Staff to provide further information on where the RDS WHOIS-2 Review Team recommendations listed in the Data Analysis Proposals (e.g., R 4.2, R 5.1, LE.1, CC.1) stand. (https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit)<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">3. RDA Scoping Team members to suggest further edits to the current accuracy description, based on the discussion from today's meeting, including, for example, updated language regarding Spec.
13: https://docs.google.com/document/d/1e5rUm-AFFDgNOU3OcT7ABu4InGwPiUyb/edit by Wednesday, 23 March.
<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">4. Still open: In advance of the next meeting on Thursday, 24 March, RDA Scoping Team Members to review the Gap Analysis Proposal Review. 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. Note: IPC Reps: please respond to the comments directed to you in Proposal H.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">(https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit)
<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"><span style="font-size:11.0pt;color:black">--------<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 #21</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 17 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:l2 level1 lfo1"><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:l2 level2 lfo1"><span style="font-size:11.0pt">Brief recap from <a href="https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/05G-ap9lx75HHcPzgmIPTqc1CIrv8ZN_46c1KaxsOiB61ogBluz1wZhCAty1m_kD.u6sX1oEqxYh8USQE?startTime=1646670626000__;!!PtGJab4!pOS0uF31xMk9s_3xYU8rPD6uMv2JqiKElyuG0l0ITiIusc4Gog3znyZDtWAt1jaIfU8NhSAjw2E$" title="https://urldefense.com/v3/__https://icann.zoom.us/rec/share/05G-ap9lx75HHcPzgmIPTqc1CIrv8ZN_46c1KaxsOiB61ogBluz1wZhCAty1m_kD.u6sX1oEqxYh8USQE?startTime=1646670626000__;!!PtGJab4!pOS0uF31xMk9s_3xYU8rPD6uMv2JqiKElyuG0l0ITiIusc4Gog3znyZDtWAt1jaIfU8NhSAjw2E$"><span style="font-size:12.0pt;color:#0563C1">ICANN73
session [icann.zoom.us]</span></a> – see also <a href="https://mm.icann.org/pipermail/gnso-accuracy-st/2022-March/000336.html" title="https://mm.icann.org/pipermail/gnso-accuracy-st/2022-March/000336.html"><span style="font-size:12.0pt;color:#0563C1">https://mm.icann.org/pipermail/gnso-accuracy-st/2022-March/000336.html</span></a><o:p></o:p></span>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Becky Burr, board liaison, shared information about ICANN org reaching out to the EDPB to gain clarity on what data could
be processed in conjunction with accuracy<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There will be a variety of scenarios that will most likely be shared with this group; however, one consideration is how
this can be done without prolonging the process. If scoping team members have specific scenarios in mind, they can consider proactively sharing them. An example of a scenario: ICANN engages an independent third-party analyst who has access to the full dataset
to see what kind of inaccuracies are present in the dataset and how prevalent these issues are. Another scenario could be that ICANN org conducts this study using the ARS or something similar. Another scenario: ICANN engages a professional statistician to
understand what portion of the data set would need to be analyzed to get meaningful numbers.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is the Board going to be involved in this, or is this done through ICANN org? Specifically, should scenarios and questions
be funneled through the board liaison or the org liaison?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The group is welcome to come up with scenarios and send them to org liaison<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Two different questions: with regard to accuracy, some fraction of the people who need the data need high levels of assurance
of the data – how will that be taken into account with accuracy? Second question – GDPR is only one privacy regime among a growing number of privacy regimes. Is the inquiry structured in a way that considers the existing regulations or also other privacy regimes?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Can ICANN do a proactive ARS rather than a reactive ARS – always helpful to start with the data and getting the baseline
of what can we look at and when will benefit from this. <o:p></o:p></span></li></ul>
</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="2" type="1">
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2"><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:l1 level2 lfo2"><span style="font-size:11.0pt">See staff support team proposal (see <a href="https://mm.icann.org/pipermail/gnso-accuracy-st/2022-March/000354.html" title="https://mm.icann.org/pipermail/gnso-accuracy-st/2022-March/000354.html"><span style="font-size:12.0pt;color:#0563C1">https://mm.icann.org/pipermail/gnso-accuracy-st/2022-March/000354.html</span></a>) <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:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This was circulated earlier in the week, and has one minor redline proposed by Lori<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Support staff looked at the input provided by the Rrs, ICANN Compliance, and the subsequent discussions that flowed therefrom.
This definition is about what current requirements and enforcement looks like so that everyone is clear what that means in practice. This does not preclude changes to the requirements or enforcement in the future – this is about describing the here and now.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">With respect to the last paragraph (beginning with furthermore) – the call out to specific registry operators is concerning
to registries. The specific contractual language is set out in the base registry agreement in section 2.19. Also disagree that .brand Spec 13 operators count as verified TLDs – Spec 13 operates to restrict eligibility and restricts how many registrars can
be used by an RO and it’s not about making these names available to others. It’s about having an internal resource. In terms of measurement, how can we determine how to measure based on this definition? We are looking at saying something is accurate – but
accurate compared to what? These are really the standard against which we judge accuracy – this is what it means for a data element to be accurate against a certain standard.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Each year, ROs need to make certain certifications to ICANN – the RO, its affiliates, or trademark licensees. If trademark
licensees are permitted to register under Spec 13, it’s more than an internal registration in the company.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The latitude that is implied in checking either the email or telephone number – it needs to be clear to the requestor which
data element was verified – in other words, if the phone number is verified, the phone number needs to be provided (rather than the unverified email)<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In talking about accuracy, it is not sufficient to only discuss syntactical and operational accuracy. According to Compliance,
this group has heard that accuracy is not limited to syntactical and operational accuracy – identity could be “patently inaccurate”.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In Spec 13, there can’t be registrations done by licensees for the primary purpose – this should be looked at as different
categories. Recommend looking at Spec 3 that mentions the different niche verification requirements<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hoping this write-up gets to closing out Assignment 1. Suggest taking this one step further. Take this text and put it in
a response to the GNSO Council on Assignment #1. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Support Staff has already been working on a write-up on assignments 1 and 2, which will obviously be updated. Regarding
a previous point, there is no current requirement regarding noting which field was verified – that could be an identified gap, but it is not a current requirement. There is also a note about when further checks are applied – as provided by compliance. Regarding
the last paragraph, if there are certain contractional provisions that should be added, please provide examples to Support Staff.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In most cases, it’s not a check of accuracy, it is a check of eligibility. It does not matter if the data is accurate, it
is whether the registrant is eligible for a Spec 13 registration.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Support removing last paragraph entirely or accepting edits from Rys. Rr needs to keep logs of how the verification was
completed, but this does not need to be disclosed to a third party. Processes which arise after an inaccuracy is identified is not properly within the definition of accuracy. It is also difficult to respond to comments that do not propose concrete changes.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This may be helpful to consider in the policy discussion: When storing the data for the first time, the person responsible
must check with the usual care whether there are any arguments against the correctness of the data collected. If inaccuracies become known later, the data must be corrected. If there are indications of inaccuracy, the person responsible must not turn a blind
eye but must investigate them. In addition, Art. 5 Para. 1 lit. d GDPR (and Art. 4 Para. 1 lit takes notice. – think it will be helpful to further study the legal literature on this topic<o:p></o:p></span></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:l1 level2 lfo2"><span style="font-size:11.0pt;color:windowtext">If staff proposal is not supported under a), 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!pOS0uF31xMk9s_3xYU8rPD6uMv2JqiKElyuG0l0ITiIusc4Gog3znyZDtWAt1jaIfU8NA8jR5UQ$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1JGdNLjOjhmJnj-iDaGvcVnv1gZ5tQu5C/edit__;!!PtGJab4!pOS0uF31xMk9s_3xYU8rPD6uMv2JqiKElyuG0l0ITiIusc4Gog3znyZDtWAt1jaIfU8NA8jR5UQ$"><span style="font-size:12.0pt;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><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2"><span style="font-size:11.0pt;color:windowtext">Review survey responses (see <a href="https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLSdL-R4Tk7pP86bMIRMX1tH1IA9-UgbHFYVJyznlBcQjch99Pg/viewform__;!!PtGJab4!pOS0uF31xMk9s_3xYU8rPD6uMv2JqiKElyuG0l0ITiIusc4Gog3znyZDtWAt1jaIfU8NAuaXPvQ$" title="https://urldefense.com/v3/__https://docs.google.com/forms/d/e/1FAIpQLSdL-R4Tk7pP86bMIRMX1tH1IA9-UgbHFYVJyznlBcQjch99Pg/viewform__;!!PtGJab4!pOS0uF31xMk9s_3xYU8rPD6uMv2JqiKElyuG0l0ITiIusc4Gog3znyZDtWAt1jaIfU8NAuaXPvQ$"><span style="font-size:12.0pt;color:#0563C1">https://docs.google.com/forms/d/e/1FAIpQLSdL-R4Tk7pP86bMIRMX1tH1IA9-UgbHFYVJyznlBcQjch99Pg/viewform
[docs.google.com]</span></a>)</span><span style="font-size:11.0pt"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list: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>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-17.85pt"><span style="font-size:11.0pt;color:black">3.</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
review of Gap Analysis Data Collection Proposals (30 minutes)(see </span><span style="font-size:11.0pt;color:#172B4D"><a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit__;!!PtGJab4!pOS0uF31xMk9s_3xYU8rPD6uMv2JqiKElyuG0l0ITiIusc4Gog3znyZDtWAt1jaIfU8NmoqzMtw$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit__;!!PtGJab4!pOS0uF31xMk9s_3xYU8rPD6uMv2JqiKElyuG0l0ITiIusc4Gog3znyZDtWAt1jaIfU8NmoqzMtw$"><span style="font-size:12.0pt;color:#0052CC">https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit</span><span style="font-size:12.0pt;color:#0563C1"> [docs.google.com]</span></a>)</span><span style="font-size:11.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in;text-align:justify;text-indent:-17.85pt">
<span style="font-size:11.0pt;color:black">a.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> </span><span style="font-size:11.0pt;color:black">Review Scoping Team input on proposals (upside, downside and possible
next steps)<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:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">As a reminder, there were proposals made as part of a gap analysis – in terms of how informative data could be gathered
– upsides and downsides were also added<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Also, the discussion from ICANN73 was added to this document.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is more time needed to review what is here, or, alternatively, is the group ready to discuss next steps and how to move
forward on these?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Made a reference to implemented RDS review team recommendations – it was requested that the specific recommendations be
included. For background, the recommendations from RDS review team would have provided helpful data had these recommendations be implemented – even after the GDPR went into effect.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The CC1 recommendation refers to the GNSO Council, and the Council still has it on its list to consider – it may be helpful
to see where all of these recommendations stand. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Would be helpful to hear from groups other than registrars on the survey – if it’s ultimately just registrars asking themselves
a handful of questions – it may not be beneficial – would be helpful to hear from other groups.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There are other questions not listed here – such as many registrars are obliged to verify email or telephone numbers, but
some registrars verify both – it would be helpful to know this. Also, could ask questions about tracking bounced emails. The survey has merit; the real question is will we receive answers from a significant number of registrars.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There seems to be a concern about registrars not doing what they’re supposed to.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Because the accuracy spec makes reference to a bounce being a reason to recheck, other registrars have said that bounce
tracking is difficult and they do not do it. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There is a difference b/w an email bouncing as part of a WDRP notice and a bouncing notification from a requestor<o:p></o:p></span></li></ul>
</ol>
</ol>
<p class="MsoNormal" style="margin-left:1.0in;text-align:justify;text-indent:-17.85pt">
<span style="font-size:11.0pt;color:black">b.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> </span><span style="font-size:11.0pt;color:black">Confirm next steps<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><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:l0 level1 lfo3"><span style="font-size:11.0pt">Additional questions for ICANN Compliance (20 minutes) (see </span><span style="font-size:11.0pt;color:windowtext"><a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit?pli=1__;!!PtGJab4!pOS0uF31xMk9s_3xYU8rPD6uMv2JqiKElyuG0l0ITiIusc4Gog3znyZDtWAt1jaIfU8NHj-Fouc$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit?pli=1__;!!PtGJab4!pOS0uF31xMk9s_3xYU8rPD6uMv2JqiKElyuG0l0ITiIusc4Gog3znyZDtWAt1jaIfU8NHj-Fouc$"><span style="font-size:12.0pt;color:#0563C1">https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit?pli=1 [docs.google.com]</span></a></span><span style="font-size:11.0pt">) <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">Introduce questions (Alan, Michael)<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:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Are any of the questions concerning or confusing to the team?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level3 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ICANN org liaison can take questions 3-7 back to ICANN org colleagues for a response<o:p></o:p></span></li></ul>
</ol>
</ol>
<ol style="margin-top:0in" start="4" 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">EPDP Team input<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">Confirm 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="5" type="1">
<li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo4"><span style="font-size:11.0pt">Confirm action items & next meeting (Thursday 24 March at 14.00 UTC)<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</body>
</html>