July 2025 - council - lists.icann.org

Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4
by Susan Payne July 3, 2025

July 3, 2025

I’m sure that will be fine Greg, thanks. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:ignored-in-diff-63A8E673-A4F0-43C2-8A23-496AF120C0CC] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0> ________________________________ From: DiBiase, Gregory <dibiase(a)amazon.com> Sent: Thursday, July 3, 2025 8:21:06 PM To: Susan Payne <susan.payne(a)comlaude.com>; Council(a)icann.org <council(a)icann.org> Cc: Ashcraft, Damon <dashcraft(a)swlaw.com> Subject: RE: [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 Thanks for the update, Susan. Would the IPC be willing to submit the motion to vote on this matter at Council? Page 12 of this document<https://gnso.icann.org/sites/default/files/file/field-file-attach/article-4…> contains a draft motion titled 6.2 [Section 4.2] Motion to Approve a Petition to Support a Community IRP that can serve as a template. More information re: requirements to support the petition is available here: https://www.icann.org/en/governance/bylaws#annexD . Leadership and staff stand ready to assist if the documentation is not clear. Staff will revise the Council agenda to include the voting item, and we will now allocate 40 minutes for discussion of this issue. We think that should be sufficient time and obviate the need for a special meeting (we could also go over time at Council meeting if necessary). Should the motion pass, we can proceed with notification procedures right after the Council meeting concludes (we're confident there is sufficient time). Does this work for the IPC? Thanks, Greg From: Susan Payne <susan.payne(a)comlaude.com> Sent: Thursday, July 3, 2025 10:04 AM To: DiBiase, Gregory <dibiase(a)amazon.com>; GNSO Council List <council(a)gnso.icann.org> Cc: Ashcraft, Damon <dashcraft(a)swlaw.com> Subject: RE: [EXTERNAL] [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Hi Greg, All You asked councillors to indicate, where possible, whether or not our SG/Cs favour the GNSO supporting the ALAC Petition. Damon and my instructions are that the IPC does support this. The IPC considers that the ALAC’s concerns are important and pressing issues for the ICANN community. At this juncture in time, the IPC believes that the requested actions are warranted, given the serious nature of the governance issue. ICANN simply cannot ignore its bylaws for the sake of convenience. We take this position with the recognition that ICANN reviews are deeply backlogged and inherently flawed. There is the universally agreed-upon need for fixes to be implemented. The ALAC Petition provides an important safeguard if those fixes are not made swiftly, and the IPC urges the Board and the Community to implement fixes to the review processes with all due haste and upon an agreed, non-extendable timeline. To the extent that the reconsideration request may be paused to negotiate a remedy we would encourage this to happen, with the Petition remaining pending, with the aim of an expeditious, mutually agreed remedy. Insofar as the question of whether there should be a special Council meeting early next week, the IPC would support this as an opportunity for further discussion, to allow other SGs and Cs time, if needed, to reach a firm position on whether they favour the GNSO supporting the ALAC’s Petition. I note that the NCSG, RrSG, and now the IPC already have shared their positions. I also note that we do have 30 minutes allocated for discussion during our Thursday Council meeting. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01DBEC14.F02EEDB0] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0> From: DiBiase, Gregory <dibiase(a)amazon.com<mailto:dibiase@amazon.com>> Sent: 02 July 2025 23:35 To: Anne ICANN <anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com>>; Susan Payne <susan.payne(a)comlaude.com<mailto:susan.payne@comlaude.com>> Cc: Paul McGrady <paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>>; Tomslin Samme-Nlar <mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>>; GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: RE: [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 Dear Councilors, In hopes of focusing our conversation re: Reviews and the pending ALAC petition, Leadership has gathered several potential paths forward, based on community discussions at ICANN83 and discussions amongst ourselves. It’s worth noting that even if the Council agrees on a preferred option, the path forward will be subject to ongoing Board discussion on this topic. Councilors are encouraged to propose alternative paths (or viewpoints) for discussion as well. Potential paths forward: 1. The ICANN Board amends 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 to suspend the initiation of all Reviews until this exercise is completed. (this option was discussed by the SOAC leaders at ICANN83 and put forth by the NCSG on list) 2. The ICANN Board amends the Bylaws to change the cadence of mandated Reviews to alleviate concerns about non-compliance with current Bylaws and initiates a one-time review of all Reviews through other means (i.e., the review of all Reviews is NOT outlined in a Bylaws amendment). 3. The ICANN Board does not amend any Bylaws but continues to defer Reviews while the Community initiates a review of all Reviews. (this option is essentially the path envisioned in the Board’s resolution<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…>) 4. ATRT4 is convened with the mandate to conduct a review of Reviews (although this would not be binding, and the ATRT 4 team would be able to change scope as indicated in the relevant Bylaws text). When considering the options, it might be helpful to think about what we are trying to accomplish. From what we have heard, these are the important elements: 1. Getting ICANN back into compliance with the Bylaws; 2. Initiating a review of Reviews sooner rather than later; and 3. Guardrails to ensure that any review of Reviews is completed by a certain date. If, after discussion, Councilors believe there appears to be a way forward (based on the options above) and it is not prudent to support ALAC’s petition, our next step could be a letter to the Board with our thoughts. If, after discussion, Councilors believe joining the ALAC’s petition is warranted, support can be gauged via a vote. From our understanding, the next steps are guided by the ARTICLE 4, 4.3/ANNEX D, 4.2 Independent Review Process<https://gnso.icann.org/sites/default/files/file/field-file-attach/article-4…> documentation, which can be found on the GNSO Operating Procedures<https://gnso.icann.org/en/council/procedures> page. It states that in order to determine whether the GNSO will support a Community IRP, the action ”will be put before the GNSO Council as a motion for consideration. Threshold for approval is a simple majority vote of each house, which per Section 11.3(i) of the ICANN Bylaws is the default voting threshold.” The document also includes a draft motion that can be leveraged. Also of note: we’ve allocated additional time to this matter at Council given the concerns cited by Anne and others. If a SG believes a special meeting is also warranted, please let Leadership know as soon as possible. We hope this is helpful. Please let us know if you have questions. Thanks, Greg From: Anne ICANN <anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com>> Sent: Wednesday, July 2, 2025 2:14 PM To: Susan Payne <susan.payne(a)comlaude.com<mailto:susan.payne@comlaude.com>> Cc: Paul McGrady <paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>>; DiBiase, Gregory <dibiase(a)amazon.com<mailto:dibiase@amazon.com>>; Tomslin Samme-Nlar <mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>>; GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: RE: [EXTERNAL] [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Many thanks Susan. This is extremely helpful. I think that given the support expressed for Lori's draft, the IPC should ask for the special meeting. We will also hopefully have a chance to consider a more definite alternative proposal to the ALAC approach which Greg says he will be sending. I share your concern that time is running out to request the special meeting. The introduction of a late motion at Council appears quite complicated in that it apparently must be accepted by all Councilors as appropriate for a vote. Is that how you read 3.3.2? (It seems unlikely we could get that agreement from all Councilors.) I wonder whether the IPC should go ahead and ask for the special meeting since there have been strong expressions of support for Lori's draft. It's possible that vetting of Greg's anticipated proposal at said special meeting could be persuasive to IPC members. A meeting early next week could happen if we request it now. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com> On Wed, Jul 2, 2025 at 4:57 AM Susan Payne via council <council(a)icann.org<mailto:council@icann.org>> wrote: Hi all I thought it would be helpful for us to have in mind the timing on this, as we consider what the GNSO’s position is – I am not prejudging whether the GNSO supports the Petition: Thursday 19 June: The ALAC’s Petition was delivered to the EC Admin. Our time therefore runs from then, as Tomslin indicated. Thursday 10 July at 11.59pm PDT: The deadline for the GNSO, and other EC Decisional Participants, to inform the ALAC if we support the Petition. 24 hours later: If the GNSO supports, then within 24 hours of that decision we must notify the EC Admin, other decisional Participants, and the Secretary of that support. That notice must include certain required information including a rationale, point of contact, and whether we would like a public conference call before formal Community Forum. Our next Council meeting is on 10 July at 1300 UTC (0600 PDT). The timing is very tight, but if we were to hold a vote on this at that meeting and decide to support the ALAC it ought to be possible to meet the midnight PDT deadline later that day, and to give the necessary notice within 24 hours. We are past the documents deadline for our 10 July meeting, but the Operating Procedures s3.3.2 do contain a process for consideration and voting on a late-submitted Motion. The alternative if we need a formal vote, as Greg suggests, would be an extraordinary meeting before 10 July, but given that the US is about to go into a holiday weekend that may be challenging to organise. Damon and I hope to be able to share the IPC’s views shortly. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01DBEC14.F02EEDB0] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0> From: Paul McGrady via council <council(a)icann.org<mailto:council@icann.org>> Sent: 02 July 2025 01:59 To: DiBiase, Gregory <dibiase(a)amazon.com<mailto:dibiase@amazon.com>>; Tomslin Samme-Nlar <mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 This seems sensible. Thanks Tomslin. Best, Paul ________________________________ From: Tomslin Samme-Nlar via council <council(a)icann.org<mailto:council@icann.org>> Sent: Tuesday, July 1, 2025 6:47 PM To: DiBiase, Gregory <dibiase(a)amazon.com<mailto:dibiase@amazon.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 Hi Greg, The NCSG will NOT be supporting the petition. NCSG instead supports the following proposal: * The community to urgently 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 to suspend the conduct of all Reviews until this exercise is completed; * 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. Remain blessed, Tomslin On Thu, 26 Jun 2025 at 16:52, DiBiase, Gregory <dibiase(a)amazon.com<mailto:dibiase@amazon.com>> wrote: Hi All, Do other SGs have a position here? If other SGs support the ALAC petition then it may be worth having an extraordinary meeting to determine if the GNSO as a whole supports (without support from other SOs, this petition will expire at 06:59 UTC on 11 July 2025, several hours after our next Council meeting). If there is not strong support for ALAC’s petition, I think we can forgo an extraordinary meeting and prioritize discussion of next steps re: “ATRT4 and Review of Reviews” in our next Council meeting. Thanks, Greg From: DiBiase, Gregory via council <council(a)icann.org<mailto:council@icann.org>> Sent: Wednesday, June 25, 2025 8:48 AM To: Anne ICANN <anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com>>; Tomslin Samme-Nlar <mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [EXTERNAL] [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Hi All, Noting here that the RrSG understands and appreciates the ALAC concerns but does not believe an EC petition is warranted at this juncture (dialogue on how to best proceed is ongoing). Separately, Leadership will follow up shortly on next steps from a GNSO Council perspective. Thanks, Greg From: Anne ICANN via council <council(a)icann.org<mailto:council@icann.org>> Sent: Sunday, June 22, 2025 4:58 PM To: Tomslin Samme-Nlar <mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [EXTERNAL] [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. I think the ALAC faced a deadline to preserve the community's accountability position when there was no actual proposal in place for the Board to rectify the situation in relation to an indefinite suspension of Bylaws-mandated reviews. I don't see this as very different from action taken by the IPC when it filed an RFR in relation to the Bylaws issue on Auction Proceeds Recommendation 7. It is now incumbent on the Board and the Community to "get moving" on how this will be addressed. To my mind, it is incumbent upon the GNSO Council, after consultations with SOs and ACs, to write to the Board urging it to quickly address the proposed Bylaws amendment that would rectify the current situation, state a time frame and methodology for the Review of Reviews and a corresponding time frame for ATRT4 and other reviews to be reinstated if no new solution is forthcoming. (This is all as discussed in our Council wrap-up session in Prague.) In this regard, I note that the Board has the ability to request a GNSO Input Process and the Council has the ability to initiate one as well. We all need to keep in mind that any Bylaws Amendment requires sufficient support from the EC to be approved. Let's not drag our feet on this one. "Wait and see what the Board does" is an unhealthy approach and is not consistent with the MSM we are advocating in global fora (IGF is June 23-27.) Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com> On Sat, Jun 21, 2025 at 8:33 PM Tomslin Samme-Nlar via council <council(a)icann.org<mailto:council@icann.org>> wrote: Hi Paul, We are also blindfolded by this as I don't recall this option ever being tabled. Personally, I am with you here on strategy. My view 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. 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. 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. Remain blessed, Tomslin On Sat, 21 June 2025, 22:21 Paul McGrady, <paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>> wrote: Thanks Tomslin. Anyone else feel blindsided by this? I thought the SO/AC leaders agreed in Prague to quickly work with the Board to get bylaw amendments in place so that we can kick off a review of reviews discussion while keeping bylaws integrity in place? Does anyone have any intel on why the ALAC did a complete 180 here? Frankly, I'm having trouble understanding the ALAC strategy - if it is to get bylaws in place and really fix the freeway pileup of reviews, then this was filed to make something happen that everyone already said they were in agreement to do. If this was filed to permanently calcify the ATRT pileup which isn't working, that is odd too since I don't hear anyone saying that the permanent pileup is a winning strategy. Clearly, something needs to change in how we are doing reviews, so digging in and taking the position "but that is how we have always done it" doesn't seem like a winning strategy for the ALAC or the broader community. I prefer our needle threading approach to this that we communicated to the Board earlier which boils down to: take the space you need to get this mess fixed, but let's get this fixed quickly and right. Attempting to spin up the Empowered Community for the first time over what boils down to a workflow issue seems a but much. Best, Paul ________________________________ From: Tomslin Samme-Nlar via council <council(a)icann.org<mailto:council@icann.org>> Sent: Saturday, June 21, 2025 2:17 AM To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 Dear Councilors, As you will find attached, ALAC has initiated a Community Reconsideration Request Petition on the Board’s postponement of ATRT4. As a result, ALAC is seeking support from other Decision Participants of the EC for this request. According ICANN Bylaws Annex D, Section 4.3, the GNSO as Decision Parricipant has 21 days to decide if we support the request or not. This period began on 19th June. I will discuss with leadership on how best we can address this request within the time frame since our regular council meeting might be a bit late for a discussion. In the meantime, please circulate with your SG/Cs. Remain blessed, Tomslin ---------- Forwarded message --------- From: Jonathan Zuck via ECAdmin <ecadmin(a)icann.org<mailto:ecadmin@icann.org>> Date: Fri, 20 June 2025, 02:17 Subject: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 To: Alejandra Reynoso Barral via Soac-leadership <soac-leadership(a)icann.org<mailto:soac-leadership@icann.org>> Cc: Christian Wheeler via ECAdmin <ecadmin(a)icann.org<mailto:ecadmin@icann.org>>, Justine Chew <justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>>, Claire C. Craig <claireccraig(a)gmail.com<mailto:claireccraig@gmail.com>> Fellow EC Chairs and EC Administrator Please find attached the ALAC initiated petition for an EC Request for Reconsideration on the matter of reviews. Please let me know if you have any questions. Jonathan Jonathan Zuck Chair, ALAC _______________________________________________ ECAdmin mailing list -- ecadmin(a)icann.org<mailto:ecadmin@icann.org> To unsubscribe send an email to ecadmin-leave(a)icann.org<mailto:ecadmin-leave@icann.org> _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) 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. This email originated from outside the firm. Please use caution. _______________________________________________ council mailing list -- council(a)icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave(a)icann.org<mailto:council-leave@icann.org> _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) 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. This email originated from outside the firm. Please use caution. ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> _______________________________________________ council mailing list -- council(a)icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave(a)icann.org<mailto:council-leave@icann.org> _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) 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. ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/>

1 0

Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4
by Susan Payne July 3, 2025

July 3, 2025

Hi Greg, All You asked councillors to indicate, where possible, whether or not our SG/Cs favour the GNSO supporting the ALAC Petition. Damon and my instructions are that the IPC does support this. The IPC considers that the ALAC’s concerns are important and pressing issues for the ICANN community. At this juncture in time, the IPC believes that the requested actions are warranted, given the serious nature of the governance issue. ICANN simply cannot ignore its bylaws for the sake of convenience. We take this position with the recognition that ICANN reviews are deeply backlogged and inherently flawed. There is the universally agreed-upon need for fixes to be implemented. The ALAC Petition provides an important safeguard if those fixes are not made swiftly, and the IPC urges the Board and the Community to implement fixes to the review processes with all due haste and upon an agreed, non-extendable timeline. To the extent that the reconsideration request may be paused to negotiate a remedy we would encourage this to happen, with the Petition remaining pending, with the aim of an expeditious, mutually agreed remedy. Insofar as the question of whether there should be a special Council meeting early next week, the IPC would support this as an opportunity for further discussion, to allow other SGs and Cs time, if needed, to reach a firm position on whether they favour the GNSO supporting the ALAC’s Petition. I note that the NCSG, RrSG, and now the IPC already have shared their positions. I also note that we do have 30 minutes allocated for discussion during our Thursday Council meeting. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01DBEC42.698E9430] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0> From: DiBiase, Gregory <dibiase(a)amazon.com> Sent: 02 July 2025 23:35 To: Anne ICANN <anneicanngnso(a)gmail.com>; Susan Payne <susan.payne(a)comlaude.com> Cc: Paul McGrady <paul(a)elstermcgrady.com>; Tomslin Samme-Nlar <mesumbeslin(a)gmail.com>; GNSO Council List <council(a)gnso.icann.org> Subject: RE: [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 Dear Councilors, In hopes of focusing our conversation re: Reviews and the pending ALAC petition, Leadership has gathered several potential paths forward, based on community discussions at ICANN83 and discussions amongst ourselves. It’s worth noting that even if the Council agrees on a preferred option, the path forward will be subject to ongoing Board discussion on this topic. Councilors are encouraged to propose alternative paths (or viewpoints) for discussion as well. Potential paths forward: 1. The ICANN Board amends 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 to suspend the initiation of all Reviews until this exercise is completed. (this option was discussed by the SOAC leaders at ICANN83 and put forth by the NCSG on list) 2. The ICANN Board amends the Bylaws to change the cadence of mandated Reviews to alleviate concerns about non-compliance with current Bylaws and initiates a one-time review of all Reviews through other means (i.e., the review of all Reviews is NOT outlined in a Bylaws amendment). 3. The ICANN Board does not amend any Bylaws but continues to defer Reviews while the Community initiates a review of all Reviews. (this option is essentially the path envisioned in the Board’s resolution<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…>) 4. ATRT4 is convened with the mandate to conduct a review of Reviews (although this would not be binding, and the ATRT 4 team would be able to change scope as indicated in the relevant Bylaws text). When considering the options, it might be helpful to think about what we are trying to accomplish. From what we have heard, these are the important elements: 1. Getting ICANN back into compliance with the Bylaws; 2. Initiating a review of Reviews sooner rather than later; and 3. Guardrails to ensure that any review of Reviews is completed by a certain date. If, after discussion, Councilors believe there appears to be a way forward (based on the options above) and it is not prudent to support ALAC’s petition, our next step could be a letter to the Board with our thoughts. If, after discussion, Councilors believe joining the ALAC’s petition is warranted, support can be gauged via a vote. From our understanding, the next steps are guided by the ARTICLE 4, 4.3/ANNEX D, 4.2 Independent Review Process<https://gnso.icann.org/sites/default/files/file/field-file-attach/article-4…> documentation, which can be found on the GNSO Operating Procedures<https://gnso.icann.org/en/council/procedures> page. It states that in order to determine whether the GNSO will support a Community IRP, the action ”will be put before the GNSO Council as a motion for consideration. Threshold for approval is a simple majority vote of each house, which per Section 11.3(i) of the ICANN Bylaws is the default voting threshold.” The document also includes a draft motion that can be leveraged. Also of note: we’ve allocated additional time to this matter at Council given the concerns cited by Anne and others. If a SG believes a special meeting is also warranted, please let Leadership know as soon as possible. We hope this is helpful. Please let us know if you have questions. Thanks, Greg From: Anne ICANN <anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com>> Sent: Wednesday, July 2, 2025 2:14 PM To: Susan Payne <susan.payne(a)comlaude.com<mailto:susan.payne@comlaude.com>> Cc: Paul McGrady <paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>>; DiBiase, Gregory <dibiase(a)amazon.com<mailto:dibiase@amazon.com>>; Tomslin Samme-Nlar <mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>>; GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: RE: [EXTERNAL] [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Many thanks Susan. This is extremely helpful. I think that given the support expressed for Lori's draft, the IPC should ask for the special meeting. We will also hopefully have a chance to consider a more definite alternative proposal to the ALAC approach which Greg says he will be sending. I share your concern that time is running out to request the special meeting. The introduction of a late motion at Council appears quite complicated in that it apparently must be accepted by all Councilors as appropriate for a vote. Is that how you read 3.3.2? (It seems unlikely we could get that agreement from all Councilors.) I wonder whether the IPC should go ahead and ask for the special meeting since there have been strong expressions of support for Lori's draft. It's possible that vetting of Greg's anticipated proposal at said special meeting could be persuasive to IPC members. A meeting early next week could happen if we request it now. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com> On Wed, Jul 2, 2025 at 4:57 AM Susan Payne via council <council(a)icann.org<mailto:council@icann.org>> wrote: Hi all I thought it would be helpful for us to have in mind the timing on this, as we consider what the GNSO’s position is – I am not prejudging whether the GNSO supports the Petition: Thursday 19 June: The ALAC’s Petition was delivered to the EC Admin. Our time therefore runs from then, as Tomslin indicated. Thursday 10 July at 11.59pm PDT: The deadline for the GNSO, and other EC Decisional Participants, to inform the ALAC if we support the Petition. 24 hours later: If the GNSO supports, then within 24 hours of that decision we must notify the EC Admin, other decisional Participants, and the Secretary of that support. That notice must include certain required information including a rationale, point of contact, and whether we would like a public conference call before formal Community Forum. Our next Council meeting is on 10 July at 1300 UTC (0600 PDT). The timing is very tight, but if we were to hold a vote on this at that meeting and decide to support the ALAC it ought to be possible to meet the midnight PDT deadline later that day, and to give the necessary notice within 24 hours. We are past the documents deadline for our 10 July meeting, but the Operating Procedures s3.3.2 do contain a process for consideration and voting on a late-submitted Motion. The alternative if we need a formal vote, as Greg suggests, would be an extraordinary meeting before 10 July, but given that the US is about to go into a holiday weekend that may be challenging to organise. Damon and I hope to be able to share the IPC’s views shortly. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01DBEC42.698E9430] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0> From: Paul McGrady via council <council(a)icann.org<mailto:council@icann.org>> Sent: 02 July 2025 01:59 To: DiBiase, Gregory <dibiase(a)amazon.com<mailto:dibiase@amazon.com>>; Tomslin Samme-Nlar <mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 This seems sensible. Thanks Tomslin. Best, Paul ________________________________ From: Tomslin Samme-Nlar via council <council(a)icann.org<mailto:council@icann.org>> Sent: Tuesday, July 1, 2025 6:47 PM To: DiBiase, Gregory <dibiase(a)amazon.com<mailto:dibiase@amazon.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 Hi Greg, The NCSG will NOT be supporting the petition. NCSG instead supports the following proposal: * The community to urgently 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 to suspend the conduct of all Reviews until this exercise is completed; * 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. Remain blessed, Tomslin On Thu, 26 Jun 2025 at 16:52, DiBiase, Gregory <dibiase(a)amazon.com<mailto:dibiase@amazon.com>> wrote: Hi All, Do other SGs have a position here? If other SGs support the ALAC petition then it may be worth having an extraordinary meeting to determine if the GNSO as a whole supports (without support from other SOs, this petition will expire at 06:59 UTC on 11 July 2025, several hours after our next Council meeting). If there is not strong support for ALAC’s petition, I think we can forgo an extraordinary meeting and prioritize discussion of next steps re: “ATRT4 and Review of Reviews” in our next Council meeting. Thanks, Greg From: DiBiase, Gregory via council <council(a)icann.org<mailto:council@icann.org>> Sent: Wednesday, June 25, 2025 8:48 AM To: Anne ICANN <anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com>>; Tomslin Samme-Nlar <mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [EXTERNAL] [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Hi All, Noting here that the RrSG understands and appreciates the ALAC concerns but does not believe an EC petition is warranted at this juncture (dialogue on how to best proceed is ongoing). Separately, Leadership will follow up shortly on next steps from a GNSO Council perspective. Thanks, Greg From: Anne ICANN via council <council(a)icann.org<mailto:council@icann.org>> Sent: Sunday, June 22, 2025 4:58 PM To: Tomslin Samme-Nlar <mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [EXTERNAL] [council] Re: Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. I think the ALAC faced a deadline to preserve the community's accountability position when there was no actual proposal in place for the Board to rectify the situation in relation to an indefinite suspension of Bylaws-mandated reviews. I don't see this as very different from action taken by the IPC when it filed an RFR in relation to the Bylaws issue on Auction Proceeds Recommendation 7. It is now incumbent on the Board and the Community to "get moving" on how this will be addressed. To my mind, it is incumbent upon the GNSO Council, after consultations with SOs and ACs, to write to the Board urging it to quickly address the proposed Bylaws amendment that would rectify the current situation, state a time frame and methodology for the Review of Reviews and a corresponding time frame for ATRT4 and other reviews to be reinstated if no new solution is forthcoming. (This is all as discussed in our Council wrap-up session in Prague.) In this regard, I note that the Board has the ability to request a GNSO Input Process and the Council has the ability to initiate one as well. We all need to keep in mind that any Bylaws Amendment requires sufficient support from the EC to be approved. Let's not drag our feet on this one. "Wait and see what the Board does" is an unhealthy approach and is not consistent with the MSM we are advocating in global fora (IGF is June 23-27.) Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com> On Sat, Jun 21, 2025 at 8:33 PM Tomslin Samme-Nlar via council <council(a)icann.org<mailto:council@icann.org>> wrote: Hi Paul, We are also blindfolded by this as I don't recall this option ever being tabled. Personally, I am with you here on strategy. My view 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. 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. 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. Remain blessed, Tomslin On Sat, 21 June 2025, 22:21 Paul McGrady, <paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>> wrote: Thanks Tomslin. Anyone else feel blindsided by this? I thought the SO/AC leaders agreed in Prague to quickly work with the Board to get bylaw amendments in place so that we can kick off a review of reviews discussion while keeping bylaws integrity in place? Does anyone have any intel on why the ALAC did a complete 180 here? Frankly, I'm having trouble understanding the ALAC strategy - if it is to get bylaws in place and really fix the freeway pileup of reviews, then this was filed to make something happen that everyone already said they were in agreement to do. If this was filed to permanently calcify the ATRT pileup which isn't working, that is odd too since I don't hear anyone saying that the permanent pileup is a winning strategy. Clearly, something needs to change in how we are doing reviews, so digging in and taking the position "but that is how we have always done it" doesn't seem like a winning strategy for the ALAC or the broader community. I prefer our needle threading approach to this that we communicated to the Board earlier which boils down to: take the space you need to get this mess fixed, but let's get this fixed quickly and right. Attempting to spin up the Empowered Community for the first time over what boils down to a workflow issue seems a but much. Best, Paul ________________________________ From: Tomslin Samme-Nlar via council <council(a)icann.org<mailto:council@icann.org>> Sent: Saturday, June 21, 2025 2:17 AM To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 Dear Councilors, As you will find attached, ALAC has initiated a Community Reconsideration Request Petition on the Board’s postponement of ATRT4. As a result, ALAC is seeking support from other Decision Participants of the EC for this request. According ICANN Bylaws Annex D, Section 4.3, the GNSO as Decision Parricipant has 21 days to decide if we support the request or not. This period began on 19th June. I will discuss with leadership on how best we can address this request within the time frame since our regular council meeting might be a bit late for a discussion. In the meantime, please circulate with your SG/Cs. Remain blessed, Tomslin ---------- Forwarded message --------- From: Jonathan Zuck via ECAdmin <ecadmin(a)icann.org<mailto:ecadmin@icann.org>> Date: Fri, 20 June 2025, 02:17 Subject: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 To: Alejandra Reynoso Barral via Soac-leadership <soac-leadership(a)icann.org<mailto:soac-leadership@icann.org>> Cc: Christian Wheeler via ECAdmin <ecadmin(a)icann.org<mailto:ecadmin@icann.org>>, Justine Chew <justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>>, Claire C. Craig <claireccraig(a)gmail.com<mailto:claireccraig@gmail.com>> Fellow EC Chairs and EC Administrator Please find attached the ALAC initiated petition for an EC Request for Reconsideration on the matter of reviews. Please let me know if you have any questions. Jonathan Jonathan Zuck Chair, ALAC _______________________________________________ ECAdmin mailing list -- ecadmin(a)icann.org<mailto:ecadmin@icann.org> To unsubscribe send an email to ecadmin-leave(a)icann.org<mailto:ecadmin-leave@icann.org> _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) 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. This email originated from outside the firm. Please use caution. _______________________________________________ council mailing list -- council(a)icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave(a)icann.org<mailto:council-leave@icann.org> _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) 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. This email originated from outside the firm. Please use caution. ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> _______________________________________________ council mailing list -- council(a)icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave(a)icann.org<mailto:council-leave@icann.org> _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) 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. ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/>

2 1

FYI | FW: [Ext] NEW: ICANN84 Annual General Meeting Relocated
by Terri Agnew July 3, 2025

July 3, 2025

FYI – check it out, loads of new items [https://danh45uab.cc.rs6.net/on.jsp?ca=110eb191-7da6-4a45-b472-f0b854f7e324…] Thursday, 03 July 2025 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] Click here to learn more about the New gTLD Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org!<mailto:policyinfo@icann.org> Table of Contents Information Sharing · NEW: ICANN Announces Dispute Resolution Service Providers for the Next Round · NEW: Launching the New Five-Year ICANN Strategic Plan · NEW: ICANN84 Annual General Meeting Relocated · NEW: Charting the Path Forward: ICANN Middle East Regional Plan FY26–30 · NEW: Making the Internet Work: Remarks at the IGF 2025 Opening Session · NEW: ICANN Achieves Key Milestone in Universal Acceptance · NEW: Approved Resolutions | Special Meeting of the ICANN Board | 27 June 2025 · ICANN Materials Provide Prospective New gTLD Applicants Clarity on Key Topics · Next Round Champions Toolkit Available in the Six ICANN Languages · ICANNWiki Seeking Volunteers 🚨 Action Items 🚨 · ICANN Opens Nomination Period for Dr. Tarek Kamel Award for Capacity Building · Call for ASP Mentors Public Comment · NEW: Public Comment Summary Report: Transfer Policy Review Working Group Final Report for ICANN Board Consideration · Updated ICANN Community Participant Code of Conduct Concerning SOIs · Proposed Next Round Base gTLD Registry Agreement - Public Comment 1 of 2 · Final Proceeding for Proposed Language for the Draft Next Round Applicant Guidebook (AGB) · Root Zone Label Generation Rules Version 6 (RZ-LGR-6) · Maximal Starting Repertoire Version 6 (MSR-6) Events · These events occur in July 2025. Information Sharing NEW: ICANN Announces Dispute Resolution Service Providers for the Next Round The dispute resolution process is intended to afford certain parties an opportunity to advance arguments against introducing certain new gTLDs into the Domain Name System or for having certain strings enter a contention set. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> NEW: Launching the New Five-Year ICANN Strategic Plan 2030 Vision: As the trusted steward of the Internet's unique identifier systems, ICANN is dedicated to strengthening the single, globally interoperable Internet for all. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> NEW: ICANN84 Annual General Meeting Relocated Recent developments, including associated flight disruptions and impending timelines related to planning the meeting, made it prudent and necessary to select an alternative and available location. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> NEW: Charting the Path Forward: ICANN Middle East Regional Plan FY26–30 The FY26–30 Middle East Regional Plan reflects the close collaboration between ICANN's Global Stakeholder Engagement (GSE) team in the Middle East and the region's community members. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> NEW: Making the Internet Work: Remarks at the IGF 2025 Opening Session ICANN President and CEO Kurtis Lindqvist delivered remarks on the importance of practical collaboration, technical coordination, and the risks of fragmentation. His message set the tone for the week. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> NEW: ICANN Achieves Key Milestone in Universal Acceptance Users can now sign up for and sign in to ICANN Account using email addresses in their local languages and scripts – a major step forward in making the Internet truly accessible to all. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> NEW: Approved Resolutions | Special Meeting of the ICANN Board | 27 June 2025 Please find the Approved Resolutions from the 27 June 2025 Special Meeting of the ICANN Board here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…>. Next Round Outreach, Engagement, and Communications Snapshot We’re excited to introduce the Next Round Snapshot, a new monthly recap that highlights key updates shared during the IRT Outreach meetings. This report covers recent activities across the Applicant Support Program (ASP), Registry Service Provider (RSP) evaluation, regional and topical engagement, web traffic stats, and communications milestones. Developed in response to GAC feedback, this snapshot supports visibility and alignment across teams working on the New gTLD Program: Next Round. 📅 Published monthly following each IRT Outreach meeting 📎 Check out the inaugural April/May edition here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…>. For questions, contact globalsupport(a)icann.org.<mailto:globalsupport@icann.org> ICANN Materials Provide Prospective New gTLD Applicants Clarity on Key Topics ICANN org is developing supplemental, complementary materials to aid prospective generic top-level domain (gTLD) applicants in understanding the Next Round application requirements, and how to navigate the application and evaluation processes. Blog [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…>. Key Topic Overview Documents. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> Next Round Champions Toolkit Available in the Six ICANN Languages ICANN is working with the community to identify potential Applicant Support Program (ASP) applicants – especially in regions that are currently under-represented in ICANN. If you are interested in helping to raise awareness among your own contacts or communities, please use the materials in the Next Round Champions Toolkit [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…>. To stay up to date on the New gTLD Program: Next Round and ASP, join the mailing list: nextroundinfo(a)icann.org. ASP leads, targets, and ideas can be sent to engagement.newgTLDprogram(a)icann.org<mailto:engagement.newgTLDprogram@icann.org>. ICANNWiki Seeking Volunteers ICANNWiki is seeking volunteers to assist with creating and editing articles and content for the site. Do you want to help? Getting started is as simple as requesting an account [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…>. Then, make sure to read the short content guide [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> to get a feel for what belongs in the wiki. Also, feel free to take a look at some data source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> on where to find reliable data. Happy editing! Action Items ICANN Opens Nomination Period for Dr. Tarek Kamel Award for Capacity Building It recognizes ICANN community members for significant efforts in developing aptitude in areas related to ICANN's mission. Deadline: 31 July 2025 at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> Call for ASP Mentors ICANN is seeking volunteer mentors who would like to offer their expertise to supported applicants as part of the ASP in the new gTLD Program: Next Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…>. ICANN is looking for mentors who can share insights and experience across ICANN Languages (Arabic, Chinese, English, French, Russian, or Spanish) to support diverse gTLD applicants. Mentors may play a role in: advising applicants on navigating the gTLD application process and DNS industry; identifying resources; providing guidance; sharing experiences as appropriate; and helping supported applicants navigate the ICANN community and Public Meetings. If you or someone in your network might be interested, please refer to the mentor registration announcement [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> for more information. Questions about the ASP or becoming a supported applicant Mentor can be sent to globalsupport(a)icann.org<mailto:globalsupport@icann.org>. Public Comment NEW: Public Comment Summary Report: Transfer Policy Review Working Group Final Report for ICANN Board Consideration [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> Updated ICANN Community Participant Code of Conduct Concerning SOIs [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> Submissions Opening Date: Monday, 12 May 2025 Submissions Closing Date: Monday, 14 July 2025 Proposed Next Round Base gTLD Registry Agreement - Public Comment 1 of 2 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> Submissions Opening Date: Wednesday, 4 June 2025 Submissions Closing Date: Monday, 21 July 2025 Final Proceeding for Proposed Language for the Draft Next Round Applicant Guidebook (AGB) [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> Submissions Opening Date: Friday, 30 May 2025 Submissions Closing Date: Wednesday, 23 July 2025 Root Zone Label Generation Rules Version 6 (RZ-LGR-6) [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> Open for Submissions: 17 June 2025 Closed for Submissions: 29 July 2025 Maximal Starting Repertoire Version 6 (MSR-6) [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> Open for Submissions: 17 June 2025 Closed for Submissions: 29 July 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…>. Events These events occur in July 2025. To learn more, please visit our community engagement calendar [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…>. · CANTO 2025 Conference · Africa Law Tech Festival 2025 · DNS Operations and DNSSEC Hands-On Workshop - Pakistan 2025 · AAU 16th Quadrienal General Conference · VNNIC Internet Conference 2025 · Asia Pacific Advanced Network Conference (APAN60) Volume 7, Issue 48 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…> | Next Issue: Monday, 07 July 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001jQwb-32…>

1 0

Fwd: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4
by Tomslin Samme-Nlar July 2, 2025

July 2, 2025

Dear Councilors, As you will find attached, ALAC has initiated a Community Reconsideration Request Petition on the Board’s postponement of ATRT4. As a result, ALAC is seeking support from other Decision Participants of the EC for this request. According ICANN Bylaws Annex D, Section 4.3, the GNSO as Decision Parricipant has 21 days to decide if we support the request or not. This period began on 19th June. I will discuss with leadership on how best we can address this request within the time frame since our regular council meeting might be a bit late for a discussion. In the meantime, please circulate with your SG/Cs. Remain blessed, Tomslin ---------- Forwarded message --------- From: Jonathan Zuck via ECAdmin <ecadmin(a)icann.org> Date: Fri, 20 June 2025, 02:17 Subject: [ECAdmin] Petition for an EC Request Reconsideration on on the postponement of ATRT4 To: Alejandra Reynoso Barral via Soac-leadership <soac-leadership(a)icann.org> Cc: Christian Wheeler via ECAdmin <ecadmin(a)icann.org>, Justine Chew < justine.chew.icann(a)gmail.com>, Claire C. Craig <claireccraig(a)gmail.com> Fellow EC Chairs and EC Administrator Please find attached the ALAC initiated petition for an EC Request for Reconsideration on the matter of reviews. Please let me know if you have any questions. Jonathan Jonathan Zuck Chair, ALAC _______________________________________________ ECAdmin mailing list -- ecadmin(a)icann.org To unsubscribe send an email to ecadmin-leave(a)icann.org _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) 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.

5 15

GNSO Council Portfolio Management Tool Suite - 10 July 2025 Meeting
by Steve Chan July 2, 2025

July 2, 2025

Dear all, Please see links below to the latest version of the GNSO Council’s Portfolio Management Tool Suite for the meeting on 10 July 2025. Agenda: * https://icann-community.atlassian.net/wiki/x/KKafBg Motions: * https://icann-community.atlassian.net/wiki/x/PKifBg Links to the Program Suite: * Program/Project Management Framework (PPMF): https://icann-community.atlassian.net/wiki/x/TgyfBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/Tgy…> * Portfolio Management Tool (PMT): https://icann-community.atlassian.net/wiki/x/WQyfBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/WQy…> * **Action/Decision Radar (ADR): https://icann-community.atlassian.net/wiki/x/cAyfBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/cAy…> * **Project List (PL): https://icann-community.atlassian.net/wiki/x/ZAyfBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/ZAy…> * **Action Items (AIs): https://icann-community.atlassian.net/wiki/x/64OeBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/64O…> * Council Small Teams (CSTs): https://icann-community.atlassian.net/wiki/x/JS6fBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/JS6…> * ** denotes the required three work products for review by Councilors in preparation for monthly meetings Key Program Suite Structural Changes for this Period: * None for this period Key Project Changes or Milestones for this Period: * GNSO Council review of the GAC Communique for ICANN83 * GNSO Council to consider next steps regarding Registration Data Accuracy * GNSO Council to consider next steps regarding DNS Abuse * IRT Status Page: https://www.icann.org/policy/implementation Key Project Activities for August/September 2025: * Registration Data Policy effective data begins * GNSO Council to consider 2026 CSC slate * GNSO Council to consider non-CPH candidates to CSC * GNSO Council to consider next steps in consideration of a review of the Expiration Policy * GNSO Council to consider findings from Board Readiness Recommendations small team * Portfolio Management Tool (PMT) suite reset for FY26-FY30 Please let staff know if you have any questions. Best, Steve Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Meeting Invitation | GNSO Council Meeting | Thursday, 10 July 2025
by Terri Agnew July 1, 2025

July 1, 2025

Dear all, The GNSO Council meeting is scheduled on Thursday, 10 July 2025 at 13:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> Visit the Wiki Agenda page: https://icann-community.atlassian.net/wiki/x/KKafBg Check your time zone: https://tinyurl.com/58frfr46 Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Passcode: mkt7*ULa9b If joining Zoom via Zoom App the following will be required: Webinar ID: 910 4823 5847 Passcode: 9213420189 Or One tap mobile : +13462487799,,91048235847#,,,,*9213420189# US (Houston) +16699006833,,91048235847#,,,,*9213420189# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/a6JrPP2u5 Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://icann-community.atlassian.net/wiki/x/4KefBg> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0