<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;}
@font-face
        {font-family:Candara;
        panose-1:2 14 5 2 3 3 3 2 2 4;}
/* 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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        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:black;}
.MsoChpDefault
        {mso-style-type:export-only;
        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:700402790;
        mso-list-type:hybrid;
        mso-list-template-ids:1497935286 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:"Courier New";}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Wingdings;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Symbol;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:"Courier New";}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Wingdings;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Symbol;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:"Courier New";}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Wingdings;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></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-family:"Calibri",sans-serif;color:black">Thanks Rafik.  Thanks Darcy.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Darcy, to respond to your request, I’m not sure that I can provide much more background on this than the letter itself, which is pretty self-explanatory.  We all know the history:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">      
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif;color:black">GNSO Community working on various policy development efforts to address WHOIS, including protecting privacy and allowing disclosure for legitimate purposes.  .<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">      
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif;color:black">GDPR comes into effect with deadline for fines.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">      
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif;color:black">Certain Contracted Parties become concerned about fines and work with Staff to develop the Temp Spec.  IPC and other folks who need disclosure for legitimate purposes
 practically beg Staff to include the <b><u>details</u></b> of a framework for such disclosures.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">      
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif;color:black">Staff produces a Temp Spec for the Board to implement which contains the
<b><u>requirement</u></b> for disclosures but little detail.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">      
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif;color:black">Almost immediately, it is much more difficult to obtain needed disclosures for legitimate purposes, creating a safe haven for all sorts of Internet maladies.  We understand
 that some do not believe in the existence of this problem, but like most real things, the existence of the problem isn’t dependent on a need for 100% of people to believe in them.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">      
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif;color:black">Like Contracted Parties who saw an immediate problem and went to Staff seeking a Temp Spec while GNSO Community policy work was ongoing, IPC and others are working with
 Staff to (hopefully) get a Temp Spec in place addressing the details for a uniform/unified disclosure process while the Community work continues.  Hopefully, the EPDP produces Policy that finally, after decades of work, solves all of the above.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">To the extent that the policy development process is being undermined by the letter it seems to me that it has already been undermined by the request by certain Contracted Parties
 for the Temp Spec.  That ship has sailed and, respectfully, certain of the Contracted Parties were at the helm.  I know this may be unpopular email, but I think it is best not to dance around the issues or try to get cute in explaining why the letter was sent. 
 I think as far as the EPDP is concerned, it seems like a non-issue, since as Rafik noted, the letter had no effect on the work of the EPDP.   <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Apologies for the inevitable slowness in any future responses to this response.  I am in London setting up my daughter’s flat and leaving her here for university, so I will be a
 bit distracted and out of the usual time zone until next week.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Paul<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> council <council-bounces@gnso.icann.org>
<b>On Behalf Of </b>Rafik Dammak<br>
<b>Sent:</b> Thursday, September 20, 2018 10:02 AM<br>
<b>To:</b> Darcy Southwell <darcy.southwell@endurance.com><br>
<b>Cc:</b> Council GNSO <council@gnso.icann.org><br>
<b>Subject:</b> Re: [council] EPDP & Accreditation/Access Model<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Hi Darcy,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">while the letter was shared in the mailing list by EPDP team member this week, there was no discussion or reaction on that matter within the EPDP team.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Rafik <o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Le jeu. 20 sept. 2018 à 03:07, Darcy Southwell <<a href="mailto:darcy.southwell@endurance.com">darcy.southwell@endurance.com</a>> a écrit :<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-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Candara",sans-serif;color:black">Rafik, as Council liaison to the EPDP, what can you share about the impact the EPDP Team sees here?</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Candara",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Candara",sans-serif;color:black">Darcy</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Candara",sans-serif;color:black"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> Darcy Southwell <<a href="mailto:darcy.southwell@endurance.com" target="_blank">darcy.southwell@endurance.com</a>>
<br>
<b>Sent:</b> Tuesday, September 18, 2018 8:11 AM<br>
<b>To:</b> <a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<b>Subject:</b> EPDP & Accreditation/Access Model<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Candara",sans-serif;color:black">The BC/IPC recently sent a letter to ICANN org (<a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fen%2Fsystem%2Ffiles%2Fcorrespondence%2Fbc-ipc-to-marby-07sep18-en.pdf&data=02%7C01%7Cpmcgrady%40winston.com%7C71d033a9821d4ef00ef708d61e8c5549%7C12a8aae45e2f4ad8adab9375a84aa3e5%7C0%7C0%7C636729985406750073&sdata=%2F5e3XBAB9HJLerW3eImKmx9pEWnVev2CGPLuhWxWHGc%3D&reserved=0" target="_blank">https://www.icann.org/en/system/files/correspondence/bc-ipc-to-marby-07sep18-en.pdf</a>)
 about the accreditation and access model.  This letter seems problematic at this stage of the game.  We discussed this issue ad nauseam during the EPDP Charter development and the Council has tasked the EPDP with addressing the Annex. To ask ICANN org to circumvent
 the EPDP undermines the policy development process and seems disingenuous to the Council’s approval of the Charter.  In addition, the
</span><span style="color:black">EDPB’s July 5 letter states responsibility for designing an access model lies with ICANN
<b><u>and</u></b> the registries/registrars, not just ICANN as indicated in the BC/IPC letter.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Candara",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Candara",sans-serif;color:black">Will our BC and/or IPC councilors please shed some light on this?</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Candara",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Candara",sans-serif;color:black">Thanks,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Candara",sans-serif;color:black">Darcy</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fcouncil&data=02%7C01%7Cpmcgrady%40winston.com%7C71d033a9821d4ef00ef708d61e8c5549%7C12a8aae45e2f4ad8adab9375a84aa3e5%7C0%7C0%7C636729985406760069&sdata=74pu9jvsIQj8g%2FjG8RjpGKpgRxI1O%2FAkA%2BvHjU0jieU%3D&reserved=0" target="_blank">https://mm.icann.org/mailman/listinfo/council</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
<font color="gray" size="1" face="Arial"><br>
<p></p>
<hr>
The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this
 message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations.
<p></p>
</font>
</body>
</html>