<div><div dir="auto">(Observer )</div></div><div dir="auto"><br></div><div dir="auto">Yes I agree it's important and we need to give them a strong comment in regarding IRP related questions as well. </div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 12, 2019 at 8:40 PM Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p><font size="+1"><font face="Lucida Grande">I think we should jump in and support this as well, any dissent?</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Steph</font></font><br>
</p>
<div class="m_-687529805545132194moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="m_-687529805545132194moz-email-headers-table" cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">Subject: </th>
<td>Re: [ICANN Community Leaders] Accountability and community input on IRP standing panel</td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">Date: </th>
<td>Fri, 12 Apr 2019 11:40:12 -0400</td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">From: </th>
<td>Graeme Bunton <a class="m_-687529805545132194moz-txt-link-rfc2396E" href="mailto:gbunton@tucows.com" target="_blank">
<gbunton@tucows.com></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">To: </th>
<td><a class="m_-687529805545132194moz-txt-link-abbreviated" href="mailto:so-ac-sg-cleaders@icann.org" target="_blank">so-ac-sg-cleaders@icann.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<p>These are good points Katrina, thank you.<br>
</p>
<p>The RrSG shares these process concerns too, and expressed them directly to GDD staff already.</p>
<p>Graeme<br>
</p>
<div class="m_-687529805545132194moz-cite-prefix">On 2019-04-12 11:12 a.m., Austin, Donna via SO-AC-SG-CLeaders wrote:<br>
</div>
<blockquote type="cite">
<div class="m_-687529805545132194WordSection1">
<p class="MsoNormal"><span style="color:#1f497d">Dear Katrina<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Thank you for raising this important issue. The RySG has similar concerns about important request for input being buried in blog posts as opposed to the familiar public comment process. We agree that the timing
of this particular blog and request was unfortunate given it was, as you pointed out, posted right before ICANN64 when most people were travelling.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">The RySG supports your request for an extension and also your request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Donna<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Donna Austin<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Chair, RySG<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></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> SO-AC-SG-CLeaders [<a class="m_-687529805545132194moz-txt-link-freetext" href="mailto:so-ac-sg-cleaders-bounces@icann.org" target="_blank">mailto:so-ac-sg-cleaders-bounces@icann.org</a>]
<b>On Behalf Of </b>Katrina Sataki<br>
<b>Sent:</b> Friday, April 12, 2019 12:55 AM<br>
<b>To:</b> 'Goran Marby' <a class="m_-687529805545132194moz-txt-link-rfc2396E" href="mailto:goran.marby@icann.org" target="_blank">
<goran.marby@icann.org></a><br>
<b>Cc:</b> <a class="m_-687529805545132194moz-txt-link-abbreviated" href="mailto:ccnso-council@icann.org" target="_blank">
ccnso-council@icann.org</a>; 'Chris Disspain' <a class="m_-687529805545132194moz-txt-link-rfc2396E" href="mailto:chris@disspain.uk" target="_blank">
<chris@disspain.uk></a>; 'Nigel Roberts' <a class="m_-687529805545132194moz-txt-link-rfc2396E" href="mailto:nigel.roberts@board.icann.org" target="_blank">
<nigel.roberts@board.icann.org></a>; <a class="m_-687529805545132194moz-txt-link-abbreviated" href="mailto:so-ac-sg-cleaders@icann.org" target="_blank">
so-ac-sg-cleaders@icann.org</a><br>
<b>Subject:</b> [ICANN Community Leaders] Accountability and community input on IRP standing panel<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span lang="LV">Dear Göran:<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="LV">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:<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV"><u></u> <u></u></span></p>
<p class="m_-687529805545132194MsoListParagraph"><span lang="LV"><span>-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span lang="LV">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?
<u></u><u></u></span></p>
<p class="m_-687529805545132194MsoListParagraph"><span lang="LV"><span>-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span lang="LV">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?<u></u><u></u></span></p>
<p class="m_-687529805545132194MsoListParagraph"><span lang="LV"><span>-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span lang="LV">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?<u></u><u></u></span></p>
<p class="m_-687529805545132194MsoListParagraph"><span lang="LV"><span>-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span lang="LV">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?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="LV">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. <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="LV">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.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="LV">Taking into account that:<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV">1) the blog post was published right before ICANN64, when most volunteers are travelling or busy preparing for the meeting,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV">2) no corresponding public comments request has been published on the ICANN website,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV">3) no information about the request was published in ICANN Community Leadership Digest (the questions were first mentioned only on 11 April),
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV">and to ensure that:<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV">1) all community members are aware of the opportunity to provide input,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV">2) everyone has sufficient time to discuss the issue and submit their considerations,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV">3) the process is transparent and all comments are published in due time,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV">we would like to encourage you to re-launch the call for community inputs in accordance with the established procedures.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="LV">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.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="LV">Yours sincerely,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="LV">Katrina Sataki<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="LV">On behalf of the ccNSO Council<u></u><u></u></span></p>
</div>
<br>
<fieldset class="m_-687529805545132194mimeAttachmentHeader"></fieldset>
<pre class="m_-687529805545132194moz-quote-pre">_______________________________________________
SO-AC-SG-CLeaders mailing list
<a class="m_-687529805545132194moz-txt-link-abbreviated" href="mailto:SO-AC-SG-CLeaders@icann.org" target="_blank">SO-AC-SG-CLeaders@icann.org</a>
<a class="m_-687529805545132194moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders" target="_blank">https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders</a>
</pre>
</blockquote>
<pre class="m_-687529805545132194moz-signature" cols="72">--
____________________________
Graeme Bunton
Director, Analytics & Policy
Tucows Inc.
PH: 416 535 0123 ext 1634</pre>
</div>
</div>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div>