<div dir="ltr"><div>Hi,</div><div><br></div><div>I think the urgent thing to do is to prepare responses to the questions. the process for setting the standing panel is taking too much time and you can notice that some parts in ICANN are interested to push in some direction for the implementation.</div><div>I put Robin and Farzaneh in cc as they followed closely the work on IRP and what the Implementation Oversight Team (IOT) did.</div><div><br></div><div>Best</div><div><br></div>Rafik<div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 16 avr. 2019 à 05:28, Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p><font size="+1"><font face="Lucida Grande">why can't he say he is sorry? I guess this is input for our meeting<br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">SP </font></font><br>
</p>
<div class="gmail-m_-284776783407702526moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="gmail-m_-284776783407702526moz-email-headers-table" cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">Subject: </th>
<td>Re: [ICANN Community Leaders] [Ext] RE: Accountability and community input on IRP standing panel</td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">Date: </th>
<td>Mon, 15 Apr 2019 20:14:59 +0000</td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">From: </th>
<td>Goran Marby <a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:goran.marby@icann.org" target="_blank">
<goran.marby@icann.org></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">To: </th>
<td>Austin, Donna <a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:Donna.Austin@team.neustar" target="_blank">
<Donna.Austin@team.neustar></a>, Katrina Sataki <a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:katrina@nic.lv" target="_blank">
<katrina@nic.lv></a>, David Olive <a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:david.olive@icann.org" target="_blank">
<david.olive@icann.org></a>, Samantha Eisner <a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:Samantha.Eisner@icann.org" target="_blank">
<Samantha.Eisner@icann.org></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">CC: </th>
<td><a class="gmail-m_-284776783407702526moz-txt-link-abbreviated" href="mailto:ccnso-council@icann.org" target="_blank">ccnso-council@icann.org</a>
<a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:ccnso-council@icann.org" target="_blank"><ccnso-council@icann.org></a>, 'Chris Disspain'
<a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:chris@disspain.uk" target="_blank"><chris@disspain.uk></a>,
<a class="gmail-m_-284776783407702526moz-txt-link-abbreviated" href="mailto:so-ac-sg-cleaders@icann.org" target="_blank">so-ac-sg-cleaders@icann.org</a>
<a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:so-ac-sg-cleaders@icann.org" target="_blank"><so-ac-sg-cleaders@icann.org></a>, 'Nigel Roberts'
<a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:nigel.roberts@board.icann.org" target="_blank"><nigel.roberts@board.icann.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<div class="gmail-m_-284776783407702526WordSection1">
<p class="MsoNormal">Hi friends,<span style="font-family:-webkit-standard,serif;color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span>I wish to thank you for the e-mails, noting the importance to the community of the selection of a Standing Panel for Independent Review Processes (IRPs), and
suggesting that ICANN Org relaunch the call for community input via the public comment process. I would like to take this opportunity to assure everyone that our publication of a blog post on this topic on 9 March was intended to supplement, and not displace,
the existing processes through which we seek the community’s feedback. This is why the same request was circulated after the conclusion of the ICANN64 Kobe meeting in the Community Leadership Digest.<u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span> <u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span>On this specific topic, what we have tried to do is provide more specific and targeted ways for the community to provide feedback, since the establishment of an IRP Standing Panel
has been a long-standing topic of community discussion. You will recall that a webinar was held in January 2018, followed by a public session at ICANN61 in March 2018. The questions that we have developed result from these discussions to date and builds on
work done by the community-based IRP Implementation Oversight Team. We had hoped that this continuous process will allow for multiple opportunities for the community to provide its views, as we work toward completing the important task of seating the Standing
Panel.<u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span> <u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span>I take the point that publishing the blog post on 9 March without providing more specific information about how else we intend to collect community feedback may have sent the wrong
signal. In addition, I understand that the suggested 15 April deadline may not be feasible at this stage. I therefore invite you and your community groups to continue to provide your feedback via email to the publicly-archived mailing list that was set up
some time ago for the community to continue its discussions in a transparent and accessible way: <a href="https://mm.icann.org/pipermail/irp-standing-panel/" target="_blank">https://mm.icann.org/pipermail/irp-standing-panel/</a>. If possible, I ask
that you provide your input by <b><a>15 May 2019</a></b>.<u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span> <u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span>In relation to the need to provide greater clarity while ensuring transparency in our operations, you may be interested to know that, prior to the ICANN64 Kobe meeting, I had already
requested that David Olive and his team prepare a comprehensive set of guidelines regarding the appropriate use of public comment proceedings and other community consultations. I expect to hold a discussion about this with my Executive Team around the time
of ICANN65 in Marrakech.<u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span> <u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span>In closing, I thank you all for your helpful and constructive feedback. I look forward to sharing very shortly with you further information about the remaining work to be done on
the IRP Standing Panel, as well as our plans to clarify the use of public comment and consultation opportunities.<u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span><br>
<br>
<u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span>Regards<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Göran<br>
<br>
<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">"Austin, Donna"
<a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:Donna.Austin@team.neustar" target="_blank"><Donna.Austin@team.neustar></a><br>
<b>Date: </b>Monday, April 15, 2019 at 10:27 AM<br>
<b>To: </b>Katrina Sataki <a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:katrina@nic.lv" target="_blank">
<katrina@nic.lv></a>, Goran Marby <a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:goran.marby@icann.org" target="_blank">
<goran.marby@icann.org></a><br>
<b>Cc: </b><a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:ccnso-council@icann.org" target="_blank">"ccnso-council@icann.org"</a>
<a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:ccnso-council@icann.org" target="_blank"><ccnso-council@icann.org></a>, 'Chris Disspain'
<a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:chris@disspain.uk" target="_blank"><chris@disspain.uk></a>, 'Nigel Roberts'
<a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:nigel.roberts@board.icann.org" target="_blank"><nigel.roberts@board.icann.org></a>,
<a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:so-ac-sg-cleaders@icann.org" target="_blank">"so-ac-sg-cleaders@icann.org"</a>
<a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:so-ac-sg-cleaders@icann.org" target="_blank"><so-ac-sg-cleaders@icann.org></a><br>
<b>Subject: </b>[Ext] RE: [ICANN Community Leaders] Accountability and community input on IRP standing panel<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">As the deadline for responses is today 15 April 2019, do we have any update on whether the deadline will be extended as requested by Katrina.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"> </span><u></u><u></u></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> SO-AC-SG-CLeaders [<a class="gmail-m_-284776783407702526moz-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="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:goran.marby@icann.org" target="_blank">
<goran.marby@icann.org></a><br>
<b>Cc:</b> <a class="gmail-m_-284776783407702526moz-txt-link-abbreviated" href="mailto:ccnso-council@icann.org" target="_blank">
ccnso-council@icann.org</a>; 'Chris Disspain' <a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:chris@disspain.uk" target="_blank">
<chris@disspain.uk></a>; 'Nigel Roberts' <a class="gmail-m_-284776783407702526moz-txt-link-rfc2396E" href="mailto:nigel.roberts@board.icann.org" target="_blank">
<nigel.roberts@board.icann.org></a>; <a class="gmail-m_-284776783407702526moz-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:</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV"> </span><u></u><u></u></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:</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV"> </span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="gmail-m_-284776783407702526MsoListParagraph" style="margin-left:0in"><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? </span><u></u><u></u></li><li class="gmail-m_-284776783407702526MsoListParagraph" style="margin-left:0in"><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?</span><u></u><u></u></li><li class="gmail-m_-284776783407702526MsoListParagraph" style="margin-left:0in"><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?</span><u></u><u></u></li><li class="gmail-m_-284776783407702526MsoListParagraph" style="margin-left:0in"><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?</span><u></u><u></u></li></ul>
<p class="MsoNormal"><span lang="LV"> </span><u></u><u></u></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. </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV"> </span><u></u><u></u></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.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV">Taking into account that:</span><u></u><u></u></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,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV">2) no corresponding public comments request has been published on the ICANN website,</span><u></u><u></u></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),
</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV">and to ensure that:</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV">1) all community members are aware of the opportunity to provide input,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV">2) everyone has sufficient time to discuss the issue and submit their considerations,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV">3) the process is transparent and all comments are published in due time,</span><u></u><u></u></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.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV"> </span><u></u><u></u></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.
</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV">Yours sincerely,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV">Katrina Sataki</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="LV">On behalf of the ccNSO Council</span><u></u><u></u></p>
</div>
</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></div>