<div dir="auto"><div dir="auto">Hi Seun,</div><div dir="auto"><br></div><div dir="auto">Thanks, I appreciate you taking the time to respond. </div><div dir="auto"><br></div><div dir="auto">I agree that the community certainly needs to discuss this and that discussion I believe started in Prague. However, the sequence of events (amongst other proposals) that seemed to me middle ground for the community was the following:</div><div dir="auto"><ul><li>Community to propose a Bylaws amendment to the board that would amend the Bylaws to allow for a one-time review of all Reviews currently required by the Bylaws (with solutions for the issues we face today with reviews as output recommendations) and suspend the conduct of all Reviews until this exercise is completed; </li><li>With the explicit safeguard of time frame and that if this is not done within a specified period, the current Reviews obligations come back fully into force. </li></ul></div><div dir="auto">That is the sequence I propose NCSG supports.</div><div dir="auto"><br></div><div data-smartmail="gmail_signature" dir="auto">Remain blessed, <br>Tomslin</div><br><div class="gmail_quote gmail_quote_container" dir="auto"><div dir="ltr" class="gmail_attr">On Mon, 23 June 2025, 23:44 Seun Ojedeji, <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Tomslin,<div><br></div><div>What you say in your last statement with regards to option, does sound to me like a discussion that needs to happen during the community discussion phase as part of the reconsideration process, if there is no support to even get past the current stage how does the community formally get on to the next. </div><div><br></div><div>Perhaps it would be more strategic to support and then discuss any further modification of what the community wants ATRT4 and beyond to look like, unless NCSG is saying it's fine for the Board to go against its own bylaw and no further ICANN accountability is due.</div><div><br></div><div>Regards</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 21 Jun 2025 at 22:36, Tomslin Samme-Nlar <<a href="mailto:mesumbeslin@gmail.com" target="_blank" rel="noreferrer">mesumbeslin@gmail.com</a>> wrote:<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 dir="auto"><div>Hi James, all,</div><div dir="auto"><br></div><div dir="auto">I am with you here from a strategy point of view. My view (and I attempted to convey this during our bilateral with ALAC in Prague) is that narrowly focusing only on the sole issue of the bylaw violation (of not starting ATRT4), and not the underlying problem of how reviews are done (including timely implementation of recommendations that come out of each review cycle before the next) is not the better strategy overall. </div><div dir="auto"><br></div><div dir="auto">I am aware ALAC argues that ATRT4 SHOULD be used for this purpose (of reviewing the review strategy), but since per the bylaws, we cannot pre-scope what ATRT4 can or can not do, I believe the risks outweigh the benefits here, since nothing stops any ATRT4 member from asking for a wider scope similar to ATRT3 or more, thereby putting us in the same position or worse.</div><div dir="auto"><br></div><div dir="auto">The option to first put together a community group with a predictable narrow scope to review the reviews strategy and how they are done, before starting the next review cycle seems to me the better holistic option.</div><div><br></div><div>Remain blessed, <br>Tomslin</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 21 June 2025, 18:08 James Gannon, <<a href="mailto:james@policywonk.xyz" target="_blank" rel="noreferrer">james@policywonk.xyz</a>> wrote:<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 dir="auto"><div>Agreed. This would not have my support.</div><div><br></div><div><div dir="ltr"><p class="MsoNormal">--</p><p class="MsoNormal">James</p></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 21, 2025, 09:01 Johan Helsingius <<a href="mailto:00001963cc94b85a-dmarc-request@listserv.syr.edu" rel="noreferrer noreferrer" target="_blank">00001963cc94b85a-dmarc-request@listserv.syr.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I don't think we should support it.<br>
<br>
Julf<br>
<br>
<br>
On 21/06/2025 09:20, Tomslin Samme-Nlar wrote:<br>
> **PLEASE READ**<br>
> <br>
> For discussion below. We must decide as a stakeholder group whether we <br>
> support this request or not.<br>
> <br>
> Tomslin<br>
> <br>
> ---------- Forwarded message ---------<br>
> From: *Tomslin Samme-Nlar* <<a href="mailto:mesumbeslin@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">mesumbeslin@gmail.com</a> <br>
> <mailto:<a href="mailto:mesumbeslin@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">mesumbeslin@gmail.com</a>>><br>
> Date: Sat, 21 June 2025, 17:17<br>
> Subject: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on <br>
> the postponement of ATRT4<br>
> To: GNSO Council List <<a href="mailto:council@gnso.icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">council@gnso.icann.org</a> <br>
> <mailto:<a href="mailto:council@gnso.icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">council@gnso.icann.org</a>>><br>
> <br>
> <br>
> Dear Councilors,<br>
> <br>
> As you will find attached, ALAC has initiated a CommunityReconsideration <br>
> Request Petition on the Board’s postponement of ATRT4. As a result, ALAC <br>
> is seeking support from other Decision Participants of the EC for this <br>
> request.<br>
> <br>
> According ICANN Bylaws Annex D, Section 4.3, the GNSO as Decision <br>
> Parricipant has 21 days to decide if we support the request or not. This <br>
> period began on 19th June.<br>
> <br>
> I will discuss with leadership on how best we can address this request <br>
> within the time frame since our regular council meeting might be a bit <br>
> late for a discussion. In the meantime, please circulate with your SG/Cs.<br>
> <br>
> Remain blessed,<br>
> Tomslin<br>
> <br>
> ---------- Forwarded message ---------<br>
> From: *Jonathan Zuck via ECAdmin* <<a href="mailto:ecadmin@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">ecadmin@icann.org</a> <br>
> <mailto:<a href="mailto:ecadmin@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">ecadmin@icann.org</a>>><br>
> Date: Fri, 20 June 2025, 02:17<br>
> Subject: [ECAdmin] Petition for an EC Request Reconsideration on on the <br>
> postponement of ATRT4<br>
> To: Alejandra Reynoso Barral via Soac-leadership <soac- <br>
> <a href="mailto:leadership@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">leadership@icann.org</a> <mailto:<a href="mailto:soac-leadership@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">soac-leadership@icann.org</a>>><br>
> Cc: Christian Wheeler via ECAdmin <<a href="mailto:ecadmin@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">ecadmin@icann.org</a> <br>
> <mailto:<a href="mailto:ecadmin@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">ecadmin@icann.org</a>>>, Justine Chew <<a href="mailto:justine.chew.icann@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">justine.chew.icann@gmail.com</a> <br>
> <mailto:<a href="mailto:justine.chew.icann@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">justine.chew.icann@gmail.com</a>>>, Claire C. Craig <br>
> <<a href="mailto:claireccraig@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">claireccraig@gmail.com</a> <mailto:<a href="mailto:claireccraig@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">claireccraig@gmail.com</a>>><br>
> <br>
> <br>
> Fellow EC Chairs and EC Administrator<br>
> <br>
> Please find attached the ALAC initiated petition for an EC Request for <br>
> Reconsideration on the matter of reviews. Please let me know if you have <br>
> any questions.<br>
> <br>
> __ __<br>
> <br>
> Jonathan<br>
> <br>
> __ __<br>
> <br>
> Jonathan Zuck<br>
> <br>
> Chair, ALAC<br>
> <br>
> __ __<br>
> <br>
> _______________________________________________<br>
> ECAdmin mailing list -- <a href="mailto:ecadmin@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">ecadmin@icann.org</a> <mailto:<a href="mailto:ecadmin@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">ecadmin@icann.org</a>><br>
> To unsubscribe send an email to <a href="mailto:ecadmin-leave@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">ecadmin-leave@icann.org</a> <mailto:<a href="mailto:ecadmin-" rel="noreferrer noreferrer noreferrer" target="_blank">ecadmin-</a> <br>
> <a href="mailto:leave@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">leave@icann.org</a>><br>
> <br>
> _______________________________________________<br>
> By submitting your personal data, you consent to the processing of your <br>
> personal data for purposes of subscribing to this mailing list <br>
> accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/</a> <br>
> policy <<a href="https://www.icann.org/privacy/policy" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>>) and the website Terms of <br>
> Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/tos</a> <<a href="https://www.icann.org/" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://www.icann.org/</a> <br>
> privacy/tos>). You can visit the Mailman link above to change your <br>
> membership status or configuration, including unsubscribing, setting <br>
> digest-style delivery or disabling delivery altogether (e.g., for a <br>
> vacation), and so on.<br>
</blockquote></div>
</blockquote></div>
</blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">------------------------------------------------------------------------<br><font color="#888888"><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:garamond,serif">
<i><span style="color:rgb(0,102,0)">Seun Ojedeji,<br style="color:rgb(0,102,0)"></span></i><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Bringing another down does not take you up - think about your action!<br></blockquote></blockquote></font><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>