<div dir="auto">I will also be an apology for today’s meeting due to a conflicting obligation. </div><div dir="auto"><br></div><div dir="auto">Kristina </div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 20, 2021 at 12:02 PM Nigel Roberts via IOT <<a href="mailto:iot@icann.org">iot@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I will also be an apology for todays meeting due to a clash.<br>
<br>
<br>
<br>
<br>
<br>
On 20/07/2021 14:42, Flip Petillion via IOT wrote:<br>
> All :<br>
> <br>
> I’ll not be able to join you today. But I will listen to the recording.<br>
> Best<br>
> <br>
> Flip<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Flip Petillion<br>
> <br>
> fpetillion@petillion.law <mailto:<a href="mailto:fpetillion@petillion.law" target="_blank">fpetillion@petillion.law</a>><br>
> <br>
> +32484652653<br>
> <br>
> www.petillion.law<br>
> <br>
> <br>
> <br>
> id:image001.png@01D3691D.DA7539C0 <<a href="https://www.petillion.law/" rel="noreferrer" target="_blank">https://www.petillion.law/</a>><br>
> <br>
> <br>
> <br>
> Attorneys – Advocaten – Avocats<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> *From: *IOT <<a href="mailto:iot-bounces@icann.org" target="_blank">iot-bounces@icann.org</a>> on behalf of "McAuley, David via<br>
> IOT" <<a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a>><br>
> *Reply to: *"McAuley, David" <dmcauley@Verisign.com><br>
> *Date: *Tuesday, 20 July 2021 at 13:20<br>
> *To: *"<a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a>" <<a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a>><br>
> *Subject: *[IOT] Possible work remaining for IOT<br>
> <br>
> <br>
> <br>
> Dear IOT colleagues,<br>
> <br>
> <br>
> <br>
> Susan asked us to note any work items that we think remain to be done.<br>
> In my personal opinion, these are possible tasks remaining beyond those<br>
> mentioned by Susan on the last call:<br>
> <br>
> <br>
> <br>
> * To develop a recall process relating to members of the standing<br>
> panel – see Bylaw 4.3(j)(iii);<br>
> <br>
> <br>
> <br>
> * To consider the development of additional independence requirements<br>
> for members of the standing panel, including term limits and<br>
> restrictions on post-term appointment to other ICANN positions – see<br>
> Bylaw 4.3(q)(i)(B) on conflicts of interests of members of the<br>
> standing panel;<br>
> <br>
> <br>
> <br>
> * Do we want to establish ‘limitations’ on appeals? – see Bylaw 4.3(w)<br>
> which states:<br>
> <br>
> <br>
> <br>
> o */Subjectto any limitations established through the Rules of<br>
> Procedure, an IRP Panel decision may be appealed to the full<br>
> Standing Panel sitting en banc within sixty (60) days of<br>
> issuance of such decision./*<br>
> <br>
> / /<br>
> <br>
> o One possible limitation which I think we may want to consider is<br>
> whether non-binding IRPs (see Bylaw 4.3(x)(iv)) should be appealable. //<br>
> <br>
> <br>
> <br>
> o Additionally, in this respect, is it within our remit to consider<br>
> whether non-binding IRPs should constitute precedent? //<br>
> <br>
> / /<br>
> <br>
> * Is there ambiguity regarding a standing panel’s ability to<br>
> ‘adjudicate’ a stay of ICANN action or just to ‘recommend’ a stay?<br>
> See Bylaws 4.3(o) and 4.3(p). If there is ambiguity, is there<br>
> anything within our remit to help clarify? //<br>
> <br>
> / /<br>
> <br>
> * Finally, with respect to the Rule 4 (Time for Filing) issue that we<br>
> are currently discussing, should we clarify that the rule we<br>
> eventually develop is either an affirmative defense that ICANN can<br>
> raise, or not, as it sees fit or, alternatively, a firm matter of<br>
> standing that the panel should invoke on its own without exemption,<br>
> subject only to the savings language that Sam and Liz are working on?<br>
> <br>
> Best regards,<br>
> <br>
> David<br>
> <br>
> <br>
> <br>
> David McAuley<br>
> <br>
> Sr International Policy & Business Development Manager<br>
> <br>
> Verisign Inc.<br>
> <br>
> 703-948-4154<br>
> <br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> IOT mailing list<br>
> <a href="mailto:IOT@icann.org" target="_blank">IOT@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/iot" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/iot</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.<br>
> <br>
_______________________________________________<br>
IOT mailing list<br>
<a href="mailto:IOT@icann.org" target="_blank">IOT@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/iot" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/iot</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>