<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">Darcy has asked an
excellent question. As an outgoing councilor, I guess I can
afford to be blunt here. What is going on? I quit the RDS
PDP after two years of soul destroying work because it was
blindingly clear we were going nowhere, and the Board was
already working on a temp spec to override anything we were
doing. IS the same thing going to happen with the EPDP? I am
deeply concerned about the integrity of the multi-stakeholder
process.<br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Sorry for being
direct, but time is precious.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie Perrin</font></font><br>
</p>
<div class="moz-cite-prefix">On 2018-09-19 14:07, Darcy Southwell
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:00ee01d45043$9cd25d10$d6771730$@endurance.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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;}
@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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
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;
font-family:"Candara",sans-serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Candara",sans-serif;
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><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?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Candara",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Candara",sans-serif;color:black">Darcy<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Candara",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Darcy Southwell
<a class="moz-txt-link-rfc2396E" href="mailto:darcy.southwell@endurance.com"><darcy.southwell@endurance.com></a> <br>
<b>Sent:</b> Tuesday, September 18, 2018 8:11 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a><br>
<b>Subject:</b> EPDP & Accreditation/Access Model<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-family:"Candara",sans-serif;color:black">The
BC/IPC recently sent a letter to ICANN org (<a
href="https://www.icann.org/en/system/files/correspondence/bc-ipc-to-marby-07sep18-en.pdf"
moz-do-not-send="true">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Candara",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Candara",sans-serif;color:black">Will
our BC and/or IPC councilors please shed some light on this?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Candara",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Candara",sans-serif;color:black">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Candara",sans-serif;color:black">Darcy<o:p></o:p></span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
council mailing list
<a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/council">https://mm.icann.org/mailman/listinfo/council</a>
</pre>
</blockquote>
</body>
</html>