<html xmlns:v="urn:schemas-microsoft-com:vml" 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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:782918339;
mso-list-type:hybrid;
mso-list-template-ids:23472292 -1059917214 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:72.0pt;
text-indent:-36.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:90.0pt;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:126.0pt;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:162.0pt;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:198.0pt;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:234.0pt;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:270.0pt;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:306.0pt;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:342.0pt;
text-indent:-9.0pt;}
@list l1
{mso-list-id:988480777;
mso-list-type:hybrid;
mso-list-template-ids:355774806 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:18.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:54.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:90.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:126.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:162.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:198.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:234.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:270.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:306.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2
{mso-list-id:1278372920;
mso-list-type:hybrid;
mso-list-template-ids:-1037262240 476196436 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-33.5pt;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-US">Dear Keith, dear all<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">The BC is grateful for the ongoing correspondence between the Board and the GNSO Council</span><span lang="EN-US">
</span><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">about WHOIS data accuracy, proving the importance of this issue.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">The BC firmly believes that the EPDP team should continue its policy work on accuracy in Phase 2; indeed “Accuracy and WHOIS Accuracy Reporting System” is specifically referenced
on page 7 of the Phase 2 Initial Report as a Priority 2 Topic. The BC does not believe that anyone would countenance the amount of effort and resources that have so far been expended for both the Temporary Specification and the EPDP being wasted on management
of an inaccurate database.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">We note that:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:18.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo5">
<![if !supportLists]><span lang="EN-US" style="font-family:Symbol;color:black;mso-fareast-language:EN-US"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">As stated by the European Commission representative (Georgios Tselentis) on the EPDP call yesterday, the accuracy issue is a critical component of determining compliance
under the GDPR of the entire policy and the SSAD. This view was shared by the ALAC and other GAC representatives on that call.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:18.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo5">
<![if !supportLists]><span lang="EN-US" style="font-family:Symbol;color:black;mso-fareast-language:EN-US"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">Accuracy was included in the Temp Spec in multiple places. The EPDP was chartered to review the Temp Spec and make appropriate changes to comply with the GDPR.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:18.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo5">
<![if !supportLists]><span lang="EN-US" style="font-family:Symbol;color:black;mso-fareast-language:EN-US"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">The Phase 1 Final Report – as approved by the GNSO Council - addressed accuracy in Recommendation 6, and a footnote stated that:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><i><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">The topic of accuracy as related to GDPR compliance is
<u>expected to be considered further </u>as well as the WHOIS Accuracy Reporting System</span></i><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">Since the EPDP was expecting to do this work in Phase 2, and stated so in the Phase 1 Final Report, changing course now would go against the agreements they reached in Phase
1, that were adopted by the GNSO Council when it approved the Phase 1 recommendations.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">Further:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:18.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo5">
<![if !supportLists]><span lang="EN-US" style="font-family:Symbol;color:black;mso-fareast-language:EN-US"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">Bird & Bird submitted legal advice related to the accuracy requirements under GDPR. The <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pages_viewpage.action-3FpageId-3D105386422&d=DwMGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=_4XWSt8rUHZPiRG6CoP4Fnk_CCk4p550lffeMi3E1z8&m=-LdYts5hWjq8kN2q0InnZDRHDevQvAtMHmhze1YIQlI&s=OW-p5b-K4DZYDnz5ZuVUA83qvLWwKiKPh5mKFGlW2x0&e=" title="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pages_viewpage.action-3FpageId-3D105386422&d=DwMGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=_4XWSt8rUHZPiRG6CoP4Fnk_CCk4p550lffeMi3E1z8&m=-LdYts5hWjq8kN2q0InnZDRHDevQvAtMHmhze1YIQlI&s=OW-p5b-K4DZ">legal
advice given to ICANN by Bird & Bird</a> includes:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">
<b><i>A.</i></b> <b><i>Ensuring the accuracy of personal data provided by the data subject</i></b><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">1. At least under some circumstances,
<u>there is a positive obligation on the controller to ensure that the data is accurate</u>. However, the existence of such a positive obligation is contextual – it depends on the significance of the consequences for data subjects of processing inaccurate data
and the effort that would be required to verify accuracy.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">2. As explained in the ICO guidance, "<i>The more important it is that the personal data is accurate, the greater the effort you should put
into ensuring its accuracy. So if you are using the data to make decisions that may significantly affect the individual concerned or others, you need to put more effort into ensuring accuracy</i>".<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">3. The GDPR is not prescriptive in mandating the types of measures a party must put in place to meet this burden. The ICO guidance explains
that "<i>[w]hat is a ‘reasonable step’ will depend on the circumstances and, in particular, the nature of the personal data and what you will use it for</i>". As a general rule, the ICO guidance says it is usually reasonable to assume information given by
the data subject is accurate, "<i>unless inaccurate information could have serious consequences, or if common sense suggests there may be a mistake</i>".<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">4. A controller "<i>may have to get independent confirmation</i>" where the impact is particularly significant. For example, where an employer
engages employees needing essential qualifications to be able to fulfil the job description, it would be reasonable to independently verify an applicant's credentials. By contrast, where an individual completes a lifestyle survey, which will be used for research
and direct marketing, with information about interests, there is no obligation on the organisation to verify the accuracy of the information. <o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:18.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo5">
<![if !supportLists]><span lang="EN-US" style="font-family:Symbol;color:black;mso-fareast-language:EN-US"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">The EPDP has a subcommittee on legal issues that is currently proposing follow-up questions to Bird & Bird related to clarifying this legal analysis. This will
guide the EPDP develop any further policy recommendations related to accuracy.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">Finally, we shouldn’t be using an artificial deadline to stop work on a matter that is so important to several stakeholders. If funding is an issue, the GNSO Council can
ask for additional resources, and can grant the EPDP sufficient time to properly conclude its work. The Council can also ask the EPDP to create a sub-team to review this topic quickly, to enable this topic to be included in its Final Report.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">While we appreciate the work involved in rectifying historic inaccuracies in WHOIS data, the BC believes that at a minimum, accuracy could be revisited and if need be rectified
on renewal and that a clearer standard could be employed for new registrations. Again, we refer to the Initial Phase 2 Report: on page 20, under “implementation guidance”, it lays down examples of additional information that an Accreditation Authority or Identity
Provider could require from an applicant for accreditation, such as business registration numbers. Why can the same logic not be applied to new registrants?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">As ever, the BC thanks you for your consideration and stand ready to discuss this with you further.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">Best to all,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;mso-fareast-language:EN-US">Marie<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> council <council-bounces@gnso.icann.org>
<b>On Behalf Of </b>Drazek, Keith via council<br>
<b>Sent:</b> Thursday, March 12, 2020 11:34 PM<br>
<b>To:</b> council@gnso.icann.org<br>
<b>Cc:</b> gnso-secs@icann.org<br>
<b>Subject:</b> Re: [council] Seeking guidance for EPDP - Follow up from Council Meeting and Next Steps<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Hi all,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">As a follow-up to Rafik’s 6 March email (below) and our brief discussion during yesterday’s Council meeting, I’d like to share my current thinking and propose a path forward. If anyone has views to share, please do so
now; the EPDP Phase 2 Team needs our guidance in short order. I’ve done some additional homework since yesterday’s call, so I hope I’ve captured everything here accurately.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:67.0pt;text-indent:-33.5pt;mso-list:l2 level1 lfo2">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">The issue of registrant data accuracy is an important topic that deserves full and thorough consideration, including its impact on GNSO policy, contracted party agreements, and other ICANN processes such as
ARS. As such, it is not only a policy issue, and there are likely non-GDPR-specific factors that will need to be considered.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:31.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:67.0pt;text-indent:-33.5pt;mso-list:l2 level1 lfo2">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">The EPDP Team Phase 1 Final Report Recommendation #4 said, “The EPDP Team recommends that requirements related to the accuracy of registration data under the current ICANN contracts and consensus policies shall
not be affected by this policy.” The ICANN Board approved this recommendation without further guidance or comment.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:31.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:67.0pt;text-indent:-33.5pt;mso-list:l2 level1 lfo2">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">There is not agreement within the EPDP on the meaning of “data accuracy” in the context of GDPR. There is disagreement over whether it is only from the perspective of the data subject or also third parties?
There was a legal memo received during Phase 1 on the topic of data accuracy and a legal question was developed during Phase 2 to help clarify the meaning, but it has not been submitted.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:31.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:67.0pt;text-indent:-33.5pt;mso-list:l2 level1 lfo2">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">The charter for the EPDP did not specify or identify the topic of data accuracy as within scope, but the EPDP Phase 1 final report included a reference to data accuracy in footnote #24. That footnote said: “The
topic of accuracy as related to GDPR compliance is expected to be considered further as well as the WHOIS Accuracy Reporting System.” This footnote did not specify that such further consideration take place in Phase 2, but the issue was included in the Phase
2 work plan that was approved by the GNSO Council.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:31.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:67.0pt;text-indent:-33.5pt;mso-list:l2 level1 lfo2">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">During Phase 1, the EPDP Team requested external legal counsel guidance on the topic of accuracy in the context of GDPR, and received the following summary answer: “In sum, because compliance with the Accuracy
Principle is based on a reasonableness standard, ICANN and the relevant parties will be better placed to evaluate whether these procedures are sufficient. From our vantage point, as the procedures do require affirmative steps that will help confirm accuracy,
unless there is reason to believe these are insufficient, we see no clear requirement to review them.”<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:31.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:67.0pt;text-indent:-33.5pt;mso-list:l2 level1 lfo2">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">There is not sufficient clarity at this time on how existing accuracy requirements have been impacted by GDPR. As such, in order to properly consider and scope further work on registrant data accuracy, more
discussion is needed among interested/impacted parties, including ICANN Org.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:31.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:67.0pt;text-indent:-33.5pt;mso-list:l2 level1 lfo2">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">7.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">The EPDP is scheduled to conclude its Phase 2 work in June with its deliberations on priority 2 items, of which accuracy is one, needing to complete by 24 March at the latest to be included in the Final Report.
Furthermore, and there is no FY21 budget assigned for its continuation beyond that time. Under these constraints (time, resources, complexity), our ability to reach a policy solution in a couple of months is highly unlikely if not impossible and could delay
delivery of the Final Report on SSAD which has been identified by basically everyone as priority #1.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:33.5pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">In light of the above, my recommended path forward for the Council and EPDP is as follows:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt;text-indent:-36.0pt;mso-list:l0 level1 lfo4">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">Council acknowledge the importance and complexity of the topic, but also the time and resource constraints noted above.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt;text-indent:-36.0pt;mso-list:l0 level1 lfo4">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">Council will discuss and consider possible next steps, including establishing a small group/scoping team to establish a framework to address the issue of registrant data accuracy across policy/contracts/procedures.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt;text-indent:-36.0pt;mso-list:l0 level1 lfo4">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">Council to acknowledge the possible impact of the data accuracy issue in the context of SSAD implementation and RDDS, and recognize the need to prioritize accordingly.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt;text-indent:-36.0pt;mso-list:l0 level1 lfo4">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">Encourage the EPDP team to submit the pending legal memo to help inform the work of any future scoping team.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I hope that strikes the right balance to ensure the work will be done, while giving the community space and time to approach the issue holistically and to carefully develop any needed policy recommendations.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I shared this with Rafik and Pam and we are in agreement.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">We were asked to respond by Friday the 13<sup>th,
</sup>but that doesn’t leave much time for feedback, so please respond by 11:59 UTC on Monday 16 March. This will allow us to deliver our reply to the EPDP Team prior to their Tuesday call.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Keith<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> council <<a href="mailto:council-bounces@gnso.icann.org">council-bounces@gnso.icann.org</a>>
<b>On Behalf Of </b>Rafik Dammak<br>
<b>Sent:</b> Friday, March 6, 2020 6:32 PM<br>
<b>To:</b> Council GNSO <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br>
<b>Subject:</b> [EXTERNAL] [council] Seeking guidance for EPDP<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi all,<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I am sending a request from EPDP team chair asking guidance from GNSO council regarding WHOIS accuracy. There was disagreement within the EPDP team if the topic is within scope or not. So we would like to get from council
guidance regarding its expectations on WHOIS accuracy issue in phase 2 and if the EPDP team is expected to deliberate on it or not asap, taking into account the GNSO council and ICANN org ongoing
<a href="https://www.icann.org/en/system/files/correspondence/marby-to-drazek-05dec19-en.pdf">
correspondence</a> on the matter. <o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">The EPDP team chair asked that GNSO council can provide guidance by Friday 13th march so that the EPDP team will have time to receive further guidance from the external legal council (if applicable). The time constraint
can be also explained that EPDP team is currently deliberating priority 2 topics during the initial report public comment period.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Best Regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Rafik<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>