<div><div dir="auto">Thank you Julie for sharing the draft and for supporting our efforts in developing it. Your moderation helped us a lot, I must say.</div><div dir="auto"><br></div><div dir="auto">Generally, I just want to note to the council, a personal comment I had discussed internally but might not have necessarily been reflected in the text of the document:</div></div><div dir="auto"><br></div><div dir="auto"><span style="color:rgb(49,49,49);word-spacing:1px">W</span><span lang="EN" style="font-size:1rem;color:rgb(49,49,49);word-spacing:1px">ith respect to identifying a slate of well-qualified panelists, I personally think, as a GNSO Council, we should trust our SOs and ACs to have that expertise instead of relying on external parties to do the job for us, but also keep external expertise within reach. We could definitely have institutions advise on the form and essence as well as substance when asked, but they should not be the ones leading the process. </span><span style="color:rgb(49,49,49);word-spacing:1px">We had different views as to how much the external experts are to be included in the process (Flip and I). I think it should be optional and only when the need arises that we have external experts engage in the process. SOs and ACs should be more than capable of leading the efforts in reference to certain advice that independent and neutral external orgs/institutions would have provided in the very beginning concerning their process.</span><br></div><div dir="auto"><span style="color:rgb(49,49,49);word-spacing:1px"><br></span></div><div dir="auto"><span style="color:rgb(49,49,49);word-spacing:1px">Thank you all for your attention, and I look forward to any comments.</span></div><div dir="auto"><span style="color:rgb(49,49,49);word-spacing:1px"><br></span></div><div dir="auto"><span style="color:rgb(49,49,49);word-spacing:1px">Best,</span></div><div dir="auto"><span style="color:rgb(49,49,49);word-spacing:1px"><br></span></div><div dir="auto"><span style="color:rgb(49,49,49);word-spacing:1px">Elsa</span></div><div dir="auto"><font color="#313131"><span style="word-spacing:1px">—</span></font></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 9, 2019 at 7:11 PM Julie Hedlund <<a href="mailto:julie.hedlund@icann.org">julie.hedlund@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_-6286979671826764561WordSection1">
<p class="MsoNormal">Dear GNSO Councilors,<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">As you may recall, Elsa Saade and Flip Petillion volunteered to be the small team to draft a possible GNSO Council response to the request for the community to respond to the questions relating to the IRP Implementation Oversight Team (IOT)
as requested at ICANN65. The original deadline to respond to ICANN Org was 15 April 2019, per the Blog Post from Göran Marby dated 09 March 2019: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blog_independent-2Dreview-2Dprocess-2Dstanding-2Dpanel-2Dcall-2Dto-2Daction&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=ktiAwHmKA7hfUHjB7rA9oVMOqwDPHtrq4kWbcy5VkxM&s=l016TWKIgM_C82rF4B4MOYWbxALBFkuF8k03Yz1mRKQ&e=" title="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blog_independent-2Dreview-2Dprocess-2Dstanding-2Dpanel-2Dcall-2Dto-2Daction&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=ktiA" target="_blank">https://www.icann.org/news/blog/independent-review-process-standing-panel-call-to-action
[icann.org]</a>. In May Samantha Eisner and David McCauley gave a presentation on the IRP-IOT to the GNSO Council. At ICANN65 the Council asked for volunteers to draft possible GNSO Council responses, which Elsa and Flip have now done and it is attach for
your consideration after considerable discussion and upon reviewing the comments provided by the GNSO Community. We have confirmed with Samantha Eisner that ICANN Org is still interested in receiving input from the GNSO.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">This document is on the agenda for discussion for the GNSO Council meeting on Thursday, 19 September. In the meantime, please let us know if you have any questions or comments.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Kind regards,<u></u><u></u></p>
<p class="MsoNormal">Julie <u></u><u></u></p>
<p class="MsoNormal">Julie Hedlund on behalf of Elsa Saade and Flip Petillion<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/council" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/council</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">--<br><br>Elsa Saade<br>Consultant</div></div><div>Gulf Centre for Human Rights</div><div>Twitter: @Elsa_Saade</div></div></div></div></div>