<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 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Cambria;
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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"open sans";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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
{mso-style-priority:99;
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.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
--></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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Yes Ayden<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Ayden Férdeline [mailto:icann@ferdeline.com]
<br>
<b>Sent:</b> Thursday, February 07, 2019 3:59 PM<br>
<b>To:</b> Hadia Abdelsalam Mokhtar EL miniawi<br>
<b>Cc:</b> Alan Woods; Margie Milam; gnso-epdp-team@icann.org<br>
<b>Subject:</b> Re: [Gnso-epdp-team] Comments on Final Report & Additional Topics- Part 1<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Hadia,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Am I understanding your email correctly; when you state, "I am with keeping the recommendation as agreed upon during the call and see no disadvantage to any of the stakeholders with that in place," do you refer to the language that was
discussed and agreed to during Tuesday's call? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best wishes,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">Ayden <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Cambria Math","serif"">‐‐‐‐‐‐‐</span> Original Message
<span style="font-family:"Cambria Math","serif"">‐‐‐‐‐‐‐</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On Thursday, February 7, 2019 8:52 AM, Hadia Abdelsalam Mokhtar EL miniawi <Hadia@tra.gov.eg> wrote:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">All,</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">First off we are not
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">living in the land of 'What Ifs'.
<span style="color:#1F497D">The truth of the matter ICANN research and Analytics which belongs to the CTO has a goal to providing trusted information to the Internet community regarding the Internet's system of Unique identifiers <a href="https://www.icann.org/octo-research">https://www.icann.org/octo-research</a>
. The research purpose if you all recall was introduced a day or two before the posting of the initial report for public comments and therefore could not be discussed at this very late stage.</span></span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Also the situation with ICANN org research is very different than that of a registry or a registrar that decides to do his own research because the registry/registrar does not
operate in a multistakeholder model and does not need the community to develop or approve its policies/decisions. What is currently being proposed is not a research purpose but is merely a recommendation that would allow us to investigate further if such
a purpose is required or not furthermore, this proposal certainly falls within the remit of the EPDP work because it is a processing of the Registration Data. Again we are just opening the door and making it possible to pursue such a purpose if deemed necessary.
Finally we cannot get into these controller/processor discussions now because the roles are not entirely finalized yet, which would be another reason to keeping the recommendation.</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">keeping the recommendation does not mean that we are going to have the research purpose it is just to make sure that this matter is not overlooked and if deemed necessary we
could add the purpose rather than regretting it later. To this end I am with keeping the recommendation as agreed upon during the call and see no disadvantage to any of the stakeholders with that in place.</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hadia</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Alan Woods [mailto:alan@donuts.email]
<br>
<b>Sent:</b> Thursday, February 07, 2019 2:29 PM<br>
<b>To:</b> Margie Milam<br>
<b>Cc:</b> Anderson, Marc; marika.konings@icann.org; Hadia Abdelsalam Mokhtar EL miniawi; gnso-epdp-team@icann.org<br>
<b>Subject:</b> Re: [Gnso-epdp-team] Comments on Final Report & Additional Topics- Part 1</span><o:p></o:p></p>
<p> <o:p></o:p></p>
<div>
<p>All, <o:p></o:p></p>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>We need to stop living in the land of 'What Ifs'. If the SSAC needs the data from ICANN ORG, SSAC and ICANN org can figure this out and do a DPAI as Controller - this is none of our concern. <o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>If ICANN ORG (OCTO) wants to use the data for statistical or historical research or even assuming the have the prerequisite basis to do so, research in the 'public interest' ... then it is for ICANN as the controller in this instance to figure it out, not
the ePDP. This is along the same lines as a registry or registrar who, as a business, may wish do their own research and don't need nor want the ePDP to spoon feed them a ready made 'purpose'. Again it's not necessary, and out of our sphere of influence. Any
responsible business processing data for research ought to do an assessment, as controller, of the legal risks associated with the research, the data used, the compatibility of the methods of collection, the compatibility with the purposes, the legal basis,
and implementation of safeguards as expected by Art 89- they then do such research at their own risk. <o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Again, to be clear, processing for the purposes of research, is processing by the CONTROLLER. If the controller wishes a 3rd party to do such research on their behalf, then they enter into an appropriate services contract with them, with a iron clad DPA.
Simple. And be it on both their heads if their processing doesn't come up to par! <o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>I therefore echo Marc and Ayden. We have need to move on! <o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Alan<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:0in 5.25pt 0in 0in">
<p style="mso-margin-top-alt:7.5pt;margin-right:0in;margin-bottom:7.5pt;margin-left:0in">
<a href="http://donuts.domains" target="_blank"><span style="border:solid windowtext 1.0pt;padding:0in;text-decoration:none"><img border="0" width="75" height="75" id="_x0000_i1025" src="cid:image001.jpg@01D4BEFF.45469AE0" alt="Image removed by sender. Donuts Inc."></span></a><o:p></o:p></p>
</td>
<td style="padding:0in 5.25pt 0in 0in">
<div>
<p style="mso-margin-top-alt:7.5pt;margin-right:0in;margin-bottom:7.5pt;margin-left:0in;line-height:12.75pt">
<b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">Alan Woods</span></b><o:p></o:p></p>
</div>
<div>
<p style="mso-margin-top-alt:7.5pt;margin-right:0in;margin-bottom:7.5pt;margin-left:0in">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">Senior Compliance & Policy Manager, Donuts Inc.</span><o:p></o:p></p>
<div style="margin-top:7.5pt;margin-bottom:7.5pt">
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal" align="center" style="text-align:center"><o:p> </o:p></p>
</div>
<p style="mso-margin-top-alt:7.5pt;margin-right:0in;margin-bottom:7.5pt;margin-left:0in">
<span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#333333">The Victorians, </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#333333">15-18 Earlsfort Terrace<br>
Dublin 2, County Dublin</span><span style="font-size:9.0pt;font-family:"open sans","serif";color:#D6D6D6"><br>
</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#333333">Ireland</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://www.facebook.com/donutstlds" target="_blank"><span style="border:solid windowtext 1.0pt;padding:0in;text-decoration:none"><img border="0" width="100" height="100" id="_x0000_i1027" src="cid:image002.jpg@01D4BEFF.45469AE0" alt="Image removed by sender."></span></a> <a href="https://twitter.com/DonutsInc" target="_blank"><span style="border:solid windowtext 1.0pt;padding:0in;text-decoration:none"><img border="0" width="100" height="100" id="_x0000_i1028" src="cid:image002.jpg@01D4BEFF.45469AE0" alt="Image removed by sender."></span></a> <a href="https://www.linkedin.com/company/donuts-inc" target="_blank"><span style="font-size:10.5pt;text-decoration:none"><img border="0" width="100" height="100" id="_x0000_i1029" src="cid:image002.jpg@01D4BEFF.45469AE0" alt="Image removed by sender."></span></a><o:p></o:p></p>
</div>
</div>
</td>
</tr>
</tbody>
</table>
<p> <o:p></o:p></p>
</div>
<div>
<p><span style="font-family:"Cambria","serif"">Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Donuts Inc. . Any distribution or use of this communication by anyone other
than the intended recipient(s) is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then delete it from your system. Thank you.</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p> <o:p></o:p></p>
</div>
</div>
<p> <o:p></o:p></p>
<div>
<div>
<p>On Wed, Feb 6, 2019 at 8:28 PM Margie Milam <<a href="mailto:margiemilam@fb.com">margiemilam@fb.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p>Hi All-<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>Hadia’s language makes sense to us. I also wanted to share some additional information related to why this should continue to be discussed in Phase 2.<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>ICANN ORG staff – including the CTO’s office - supports and participates in SSAC. SSAC conducts very valuable research on issues that touch upon and analyze WHOIS records as it relates to the security issues for which they make recommendations. Look for
example at these reports: SSAC 40 - Measures to Protect Domain Registration Services Against Exploitation or Misuse, SSAC 23 – Is the WHOIS Service a source for email addresses for spammers? SSAC 024, Report on Domain Name Front-Running, to name a few. <o:p></o:p></p>
<p> <o:p></o:p></p>
<p>Are we not willing to recognize the value of these research activities? Are we intending to limit the issues that SSAC might need to explore to address future work? <o:p></o:p></p>
<p> <o:p></o:p></p>
<p>The recommendation is simply to explore this in Phase 2 further- which is reasonable in our view.<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>All the best,<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>Margie<o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p><b><span style="color:black">From: </span></b><span style="color:black">"Anderson, Marc" <<a href="mailto:mcanderson@verisign.com" target="_blank">mcanderson@verisign.com</a>><br>
<b>Date: </b>Wednesday, February 6, 2019 at 11:27 AM<br>
<b>To: </b>"<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>" <<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>>, "<a href="mailto:Hadia@tra.gov.eg" target="_blank">Hadia@tra.gov.eg</a>"
<<a href="mailto:Hadia@tra.gov.eg" target="_blank">Hadia@tra.gov.eg</a>>, Margie Milam <<a href="mailto:margiemilam@fb.com" target="_blank">margiemilam@fb.com</a>>, "<a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a>" <<a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a>><br>
<b>Subject: </b>RE: [Gnso-epdp-team] Comments on Final Report & Additional Topics- Part 1</span><o:p></o:p></p>
</div>
<div>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<p><span style="font-size:11.0pt">All,</span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt">Registries are NOT supportive of this as an agreement or recommendation.</span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt">We have on multiple occasions discussed a possible purpose for OCTO with the same result. ICANN has indicated that OCTO does not use personal data in their work and have not identified a need or purpose for them to do so.
Our task is to identify processing activities necessary for domain registrations and ensure those processing activities can be done in a manner compatible with GDPR. We haven’t identified a processing activity for personal data related to OCTO so we can stop
and move on.</span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt">It is beyond the scope of our PDP to create new requirements, obligations or purposes where currently none exist. </span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt">Best,</span><o:p></o:p></p>
<p><span style="font-size:11.0pt">Marc</span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank">gnso-epdp-team-bounces@icann.org</a>>
<b>On Behalf Of </b>Marika Konings<br>
<b>Sent:</b> Wednesday, February 06, 2019 7:44 AM<br>
<b>To:</b> Hadia Abdelsalam Mokhtar EL miniawi <<a href="mailto:Hadia@tra.gov.eg" target="_blank">Hadia@tra.gov.eg</a>>; Margie Milam <<a href="mailto:margiemilam@fb.com" target="_blank">margiemilam@fb.com</a>>;
<a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> [EXTERNAL] Re: [Gnso-epdp-team] Comments on Final Report & Additional Topics- Part 1</span><o:p></o:p></p>
</div>
</div>
<p> <o:p></o:p></p>
<p><span style="font-size:11.0pt">Hadia, all,</span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt">Please note that per yesterday’s agreement, the recommendation has been updated as follows:</span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><i><span style="font-size:11.0pt">The EPDP Team commits to considering in Phase 2 of its work whether additional purposes should be considered to facilitate ICANN’s Office of the Chief Technology Officer (OCTO) to carry out its mission (see
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_octo&d=DwMGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=_4XWSt8rUHZPiRG6CoP4Fnk_CCk4p550lffeMi3E1z8&m=s4rjm6aG5YuV7KcK-ax-sww3LdbGi-8kAfe2reTCpVA&s=6xX7SbLunQSJCojMv5NTNDNgQ2bQ6Iw6CnBERorRZFw&e=" target="_blank">
https://www.icann.org/octo</a>). This consideration should be informed by legal guidance on if/how provisions in the GDPR concerning research apply to ICANN Org and the expression for the need of such pseudonymized data by ICANN. </span></i><o:p></o:p></p>
<p><i><span style="font-size:11.0pt"> </span></i><o:p></o:p></p>
<p><span style="font-size:11.0pt">Best regards,</span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt">Caitlin, Berry and Marika</span><o:p></o:p></p>
<p> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p><b><span style="color:black">From: </span></b><span style="color:black">Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank">gnso-epdp-team-bounces@icann.org</a>> on behalf of Hadia Abdelsalam Mokhtar EL miniawi <<a href="mailto:Hadia@tra.gov.eg" target="_blank">Hadia@tra.gov.eg</a>><br>
<b>Date: </b>Wednesday, February 6, 2019 at 06:38<br>
<b>To: </b>Margie Milam <<a href="mailto:margiemilam@fb.com" target="_blank">margiemilam@fb.com</a>>, "<a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a>" <<a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a>><br>
<b>Subject: </b>Re: [Gnso-epdp-team] Comments on Final Report & Additional Topics- Part 1</span><o:p></o:p></p>
</div>
<div>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<p><span style="font-size:11.0pt;color:#1F497D">Hi all</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt;color:#1F497D">Thank you Margie for your edits I would suggest a minor edit to the research purpose to read (my edits are in orange)</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p><span style="color:black">"The EPDP Team commits to considering in Phase 2 of its work whether additional purposes should be considered to facilitate research ADD:<span style="background:yellow"> [ and threat response</span>] carried out by ICANN’s Office
of the Chief Technology Officer (OCTO). This consideration should be informed by legal guidance on if/how provisions in the GDPR concerning research apply to ICANN Org and
</span><span style="color:#F79646">the need for the research purpose by ICANN org in accordance with the mission of ICANN’s Office of the Chief Technology Officer."</span><o:p></o:p></p>
<p><span style="color:#F79646"> </span><o:p></o:p></p>
<p>The reason for my edits is that we don't know yet the kind of data that would be required nor the means of implementation the whole purpose/idea is yet to be explored.<o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt;color:#1F497D">Hadia</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Gnso-epdp-team [<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank">mailto:gnso-epdp-team-bounces@icann.org</a>]
<b>On Behalf Of </b>Margie Milam<br>
<b>Sent:</b> Tuesday, February 05, 2019 4:03 AM<br>
<b>To:</b> <a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> [Gnso-epdp-team] Comments on Final Report & Additional Topics- Part 1</span><o:p></o:p></p>
</div>
</div>
<p> <o:p></o:p></p>
<p><span style="color:black">Hi-</span><o:p></o:p></p>
<p><span style="color:black">Per Marika’s request, here are some language clarifications for your consideration, as well as additional topic submitted on behalf of the BC, and developed in collaboration with the IPC. New Text is in yellow highlight.<b><br>
_________</b></span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black"> </span></b><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black">Rec 1</span></b><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black">Purpose 1(b):</span></b><span style="color:black"> Subject to the Registry and Registry Terms Conditions and Policies, and ICANN Consensus Policies – please
ADD: { <span style="background:yellow">and relevant registry agreements and registrar accreditation agreements</span>]</span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black">Purpose 2:</span></b><span style="color:black"> Footnote 6 needs to be moved to be linked to Purpose 2, not Rec 2.</span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black"> </span></b><o:p></o:p></p>
<p><b><span style="color:black">Research purpose:</span></b><span style="color:black"> The EPDP Team commits to considering in Phase 2 of its work whether additional purposes should be considered to facilitate research ADD:<span style="background:yellow">
[ and threat response</span>] carried out by ICANN’s Office of the Chief Technology Officer (OCTO). This consideration should be informed by legal guidance on if/how provisions in the GDPR concerning research apply to ICANN Org and the expression 426for the
need of such data by ICANN</span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black">Footnote 7/8</span></b><span style="color:black"> should not be a footnote but moved up to the body of the report. These footnotes are substantive recommendations
and commitments that should not be buried in a footnote.</span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p><b><span style="color:black">Rec 7:</span></b><span style="color:black"> Replace “ICANN Compliance”with ”ICANN Organization” to be consistent with other recommendations. </span><o:p></o:p></p>
<p><span style="color:black">Delete the quote in Footnote 12 on page 24, since this is inconsistent with Purpose 5.</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><u><span style="color:black">Additional Topics:</span></u></b><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p><b><span style="color:black">INFORMATION TO BE PROVIDED TO THE REGISTRANT:</span></b><o:p></o:p></p>
<p><span style="color:black">Page 16- where there is the quote from the EDPB:</span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> <i>It should therefore be made clear, as part of the registration process, that the registrant is free to (1) designate the same person as the registrant (or its
representative) as the administrative or technical contact; or (2) provide contact information which does not directly identify the administrative or technical contact person concerned (e.g. <a href="mailto:admin@company.com" target="_blank"><span style="color:#954F72">admin@company.com</span></a>).
For the avoidance of doubt, the EDPB recommends explicitly clarifying this within future updates of the Temporary Specification</i>”.</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p><span style="color:black">We believe it is important to follow the EDPB’s advice and propose including a recommendation regarding informed consent, in light of the legal advice received, as follows:</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black;background:yellow">The EPDP recommends that as part of the registration process, the Registrar shall offer the registered name holder the option to (1) designate
the same person as the registrant or its representative as the technical contact; or (2) provide contact information which does not directly identify the technical contact person, but instead uses a generic or role-based email (e.g.<a href="mailto:admin@company.com" target="_blank"><span style="color:#954F72">admin@company.com</span></a>).</span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p><b><span style="color:black">OPTIONAL TECH CONTACT DISCUSSION:</span></b><span style="color:black"> We do not support making the Tech Contact optional at the registrar level or registry level and believe that more discussion is needed. For example, we
have not discussed what happens to existing Tech contacts in the legacy registrations. Shouldn’t there be a similar transitional process to what has been developed for the ORGANIZATION field? In any event, this obligation must be requieeed for the registries
since they should receive the tech contact data for those registrants who have provided consent.</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black">RECOMMENTATION REGARDING CONSENT</span></b><span style="color:black"> Page 19 – Line 549 please delete “as soon as commercially reasonable”. Instead, this
recommendation should track the dates for implementation under the transition plan that James and the registrars proposed in Toronto.</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black">Rec 4:</span></b><span style="color:black"> THICK WHOIS: we do not support the deletion of THICK WHOIS as a consensus policy, and believe that this goes beyond
the scope of this EPDP.</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black">Rec 8:</span></b><span style="color:black"> GLOBAL REDACTION vs. OPTIONAL AT THE REGISTRAR--- We do not agree with global application of the REDACTION, and
believe that this recommendation goes well beyond the Temp Spec, which at a minimum allows the registrars/registries to CHOOSE a different application, especially because of differing legal regimes. Our policy needs to be flexible enough to account for laws
beyond GDRP, such as the possible US legislation related to WHOIS. Similarly, we do not believe that the redaction should apply to legal persons. We recall James suggesting that we could consider an approach similar to the approach taken for the ORGANIZATION
Field, and thus we would like to further explore it in Phase 2.</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black">Footnote 15</span></b><span style="color:black"> is a recommendation that should be moved into the body of the Final Report & not be buried in a footnote. Also-
it needs to exclude registrations with privacy/proxy services and those for which the registrant has provided consent.</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black">PAGE 27</span></b><span style="color:black">: REDACTION OF CITY– we don’t agree with the redaction of CITY and are awaiting legal advice from Ruth on the issue.
As a result, it is premature to make a recommendation that it be redacted now. This should be a Phase 2 discussion</span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><b><span style="color:black">REC 9:</span></b><span style="color:black"> Instead of a “via a process that can be determined by each registrar” we should have concrete steps that can be
enforced by ICANN. Could the registrars identify some reasonable steps for this process?</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p><span style="color:black">ADD: <span style="background:yellow">After the implementation phase-in period, the ORG FIELD will no longer be REDACTED by either the registry or registrar.</span> </span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p><span style="color:black">We are still working through the remainder of the Final Report, and will follow up this email with additional comments.</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p><span style="color:black">All the best,</span><o:p></o:p></p>
<p><span style="color:black">Margie</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">_______________________________________________<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Gnso-epdp-team mailing list<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>