<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)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
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.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";
mso-fareast-language:EN-US;}
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.EmailStyle19
{mso-style-type:personal;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:684744338;
mso-list-template-ids:-1896038718;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
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="FR" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">No, you’re not, Michele, it is very odd.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">In all fairness, the form of that one post has a lot to do with that, there were specific questions being asked and no link to a public comment thread,
as opposed to other posts where the intent was clearly to draw attention to that single entry point. But nonetheless it’s unfortunate.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Philippe
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:FR">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:FR"> council [mailto:council-bounces@gnso.icann.org]
<b>On Behalf Of </b>Michele Neylon - Blacknight<br>
<b>Sent:</b> Friday, April 12, 2019 11:56 AM<br>
<b>To:</b> Drazek, Keith; council@gnso.icann.org<br>
<b>Subject:</b> Re: [council] Fwd: [ICANN Community Leaders] Accountability and community input on IRP standing panel<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Thanks Keith<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I suspect I am not alone in echoing the ccNSO’s feelings about this.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">While I think that blog posts and other communications are good for raising awareness about topics of “community interest” if ICANN is soliciting input and feedback then it needs to add those items / topics to the public
comments section. Otherwise they get lost and it’s also unclear as to where the input, if any, ends up when these less structured processes are used.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Michele<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">--<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">Mr Michele Neylon<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">Blacknight Solutions<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">Hosting, Colocation & Domains<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">https://www.blacknight.com/<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">https://blacknight.blog/<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">Intl. +353 (0) 59 9183072<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">Direct Dial: +353 (0)59 9183090<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">Personal blog: https://michele.blog/<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">Some thoughts: https://ceo.hosting/
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">-------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black;mso-fareast-language:EN-GB">Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-IE" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-IE" style="font-size:12.0pt;color:black">council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org><br>
<b>Reply to: </b>Keith Drazek <kdrazek@verisign.com><br>
<b>Date: </b>Friday 12 April 2019 at 10:27<br>
<b>To: </b>"council@gnso.icann.org" <council@gnso.icann.org><br>
<b>Subject: </b>[council] Fwd: [ICANN Community Leaders] Accountability and community input on IRP standing panel</span><span lang="EN-IE" style="font-size:12.0pt;color:black;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE"><br>
FYI, an email from ccNSO Chair Katrina Sataki to Göran concerning ICANN’s recent use of blog posts to invite comment.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-IE">Keith<br>
<br>
Begin forwarded message:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-IE">From:</span></b><span lang="EN-IE"> Katrina Sataki <<a href="mailto:katrina@nic.lv">katrina@nic.lv</a>><br>
<b>Date:</b> April 12, 2019 at 3:54:44 AM EDT<br>
<b>To:</b> 'Goran Marby' <<a href="mailto:goran.marby@icann.org">goran.marby@icann.org</a>><br>
<b>Cc:</b> <<a href="mailto:ccnso-council@icann.org">ccnso-council@icann.org</a>>, 'Chris Disspain' <<a href="mailto:chris@disspain.uk">chris@disspain.uk</a>>, "'Nigel Roberts'" <<a href="mailto:nigel.roberts@board.icann.org">nigel.roberts@board.icann.org</a>>,
<<a href="mailto:so-ac-sg-cleaders@icann.org">so-ac-sg-cleaders@icann.org</a>><br>
<b>Subject:</b> <b>[EXTERNAL] [ICANN Community Leaders] Accountability and community input on IRP standing panel</b><o:p></o:p></span></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-IE">Dear Göran:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">In your blog post of 9 March 2019, you invited community inputs on the process for the selection of a standing panel to hear Independent Review Process (IRP) complaints. You included a series of questions, with a deadline
for responses by 15 April 2019:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE"> <o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span lang="EN-IE">Qualifications for Standing Panelists: Are there specific qualifications that should be included? If so, what are they? Anything disqualifying? Should the SOs and ACs recommend qualifications?
And if so, how? <o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span lang="EN-IE">Identifying a Slate of Well-Qualified Panelists: We’ve heard concerns from some members of the ICANN community as to whether the broader community has the appropriate experience and skill
for this selection work, and have suggested the possibility that ICANN instead contract with experts to perform this vetting process. Should the community rely on expertise to help vet and recommend a final slate for the standing panel?<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span lang="EN-IE">Board Approval of Panel Slate – Further Questions: After there is a slate of well-qualified applicants, the Board must confirm the panel. If the Board has questions that might impact its
confirmation, to whom should those questions be addressed? If experts are used to develop the slate, should the experts, the SOs and ACs, or some combination thereof be part of that conversation?<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span lang="EN-IE">Future Selections: Should the process being designed today be reviewed for effectiveness after the first slating is completed, prior to making it standard operating procedure for future
selection rounds?<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">The IRP, as you correctly stated, is an accountability mechanism arising from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for breaches of ICANN’s own policies, core values or because decisions have
been made on the basis of incorrect information. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">Matters of high importance that fall within scope include disputes involving the rights of the Empowered Community, enforcement of ICANN’s contractual rights with respect to the IANA Naming Function Contract, and claims
regarding PTI service complaints by direct customers of the IANA naming functions (that are not resolved through mediation). The appointment of appropriately qualified and independent panellists who will be making these review decision is therefore a high
concern to us.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">Taking into account that:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">1) the blog post was published right before ICANN64, when most volunteers are travelling or busy preparing for the meeting,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">2) no corresponding public comments request has been published on the ICANN website,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">3) no information about the request was published in ICANN Community Leadership Digest (the questions were first mentioned only on 11 April),
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">and to ensure that:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">1) all community members are aware of the opportunity to provide input,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">2) everyone has sufficient time to discuss the issue and submit their considerations,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">3) the process is transparent and all comments are published in due time,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">we would like to encourage you to re-launch the call for community inputs in accordance with the established procedures.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">Furthermore, we request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future. While a blog post may remain to be a good tool for reminders, and senior staff
commentary may encourage engagement and participation, they are no substitute for due process.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">Yours sincerely,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">Katrina Sataki<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">On behalf of the ccNSO Council<o:p></o:p></span></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-IE" style="mso-fareast-language:EN-GB">_______________________________________________<br>
SO-AC-SG-CLeaders mailing list<br>
<a href="mailto:SO-AC-SG-CLeaders@icann.org">SO-AC-SG-CLeaders@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders">https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders</a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<PRE>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>