June 2026 - ALAC - lists.icann.org

Outcome of ccNSO Special Council Meeting – ALAC Rejection Action Petition.
by Laura Margolis June 7, 2026

June 7, 2026

Dear all, Today, June 7th. 2026, the ccNSO Council held a Special Council Meeting to consider ALAC’s Rejection Action Petition. *Agenda (for reference)* 1. Welcome and roll call: establish whether meeting is quorate 2. Introducing ALAC’s Rejection Action Petition – factual background, observations and discussion 3. Decision on ALAC’s Rejection Action Petition 4. Next Steps 5. AOB 6. Closure *Outcome* During the meeting, Council members reviewed the background of the petition, considered the comments received, and discussed the matter in accordance with the established procedures. Following the deliberations, the Council concluded that *it would not support the Rejection Action Petition.* The Chair will notify ALAC of the Council’s decision. Thank you. Kindest Regards, Laura Margolis -- *Laura Margolis* ALAC Liaison to ccNSO margolisl(a)gmail.com +59899690992 Teams: lauri.margolis ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

1 0

Re: [ECAdmin] ALAC's Rejection Action Permission
by Alejandra Reynoso Barral June 7, 2026

June 7, 2026

Dear Jonathan Today the ccNSO Council had a special meeting to discuss ALAC's Rejection Action Petition. After considering the comments received from the ccTLD community, and the discussion, the ccNSO Council decided NOT to support the Rejection Action Petition. Just as a heads up, we will follow up with a letter confirming this decision in the near future. Best regards, Alejandra Reynoso, ccNSO Council Chair ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Tue, Jun 2, 2026 at 5:43 AM Jonathan Zuck via ECAdmin <ecadmin(a)icann.org> wrote: > Dear ECA Members, > > Pursuant to Annex D, Section 2.2(d) of the ICANN Bylaws, having delivered > ALAC's Rejection Action Petition Notice to the EC Administration, the ALAC > would now like to invite any and all any other EC Decisional Participants > to support the ALAC's Rejection Action Petition. > > We are concerned both about the precedent set by this amendment and the > dramatically expanded timelines specifically proposed. This may be a case > where remaining in breach is better than sidestepping the bylaws in this > way. Feel free to reach out to me to discuss any part of this further. > > Please inform the ALAC at alac(a)icann.org by 23:59 PDT Monday, 8 June > 2026, to provide support for this Rejection Action Petition. > > Thank you very much! > > Jonathan > > > Jonathan Zuck > *Director, Future of Work Project* > Innovators Network Foundation > www.InnovatorsNetwork.org > _______________________________________________ > 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.

1 0

Fwd: GNSO Council has not supported the ALAC Rejection Action Petition on Transition Article 27.6
by Justine Chew June 7, 2026

June 7, 2026

My apologies, I had meant to send this update to the correct mail list but was distracted earlier. Kind regards, Justine --------- ---------- Forwarded message --------- From: Justine Chew <justine.chew.icann(a)gmail.com> Date: Sun, 7 Jun 2026, 13:45 Subject: GNSO Council has not supported the ALAC Rejection Action Petition on Transition Article 27.6 To: Alac-only <alac-only(a)icann.org> GNSO Council has just resolved not to join our petition as a Decisional Participant. Several SG/Cs understood and were in agreement with some of the points and concerns raised in the petition, but not enough for them to vote for Council to join us. Kind regards, Justine --------- On Fri, 5 Jun 2026, 05:02 Justine Chew, <justine.chew.icann(a)gmail.com> wrote: > FYI > > Kind regards, > Justine > > > > ---------- Forwarded message --------- > From: Susan Payne via council <council(a)icann.org> > Date: Fri, 5 Jun 2026 at 04:28 > Subject: [council] IPC Feedback on the Rejection Action Petition > To: Anne ICANN via council <council(a)icann.org> > Cc: GNSO-Secs <gnso-secs(a)icann.org> > > > I am sharing the IPC’s feedback on the merits of the GNSO becoming a > Supporting Decisional Participant to the ALAC’s Rejection Action Petition, > in accordance with the Solicitation of Community Feedback under Annex D > section 4.3.3 Guidelines for the GNSO to fulfill Its role and obligation > as a Decisional Participant in the Empowered Community. > > > > While this is not a unanimous view, the majority of IPC members expressing > a view do not support challenging the Board’s adoption of Transitional > Bylaw Article 27.6 at this time, and thus do not support the GNSO becoming > a Supporting Decisional Participant. > > > > IPC members do support the ALAC concerns in principle, including those > concerns set out at paragraph 3.3 of the ALAC Petition regarding failures > to implement current Board-approved recommendations. Nonetheless, and > after careful consideration, the IPC does not support the ALAC Petition, in > order to give the timed solutions in Art 27.6 a chance to work. IPC > strongly supports the accountability measures so carefully negotiated > during the IANA transition. The measures have not yielded the results that > we envisioned; it is time to right the ship, which the Board, Org and ICANN > community are seeking to do via the CCG work on Reviews. We see this > Transitional Bylaw as a measure that will allow that work to conclude. > Our deference to the Board's decision to amend the Bylaws in this way is > to give the Board the opportunity to govern as it deems necessary to uphold > the practice of accountability as well as the spirit. > > > > Article 27.6 replaces the current open‑ended Bylaws breach with guardrails > by imposing a time‑limited pause (12 months, extendable once to a maximum > of 24 months with SO/AC support or where community recommendations for a > new Reviews framework are being taken forward) and a mandatory, sequenced > restart of the Specific Reviews, if needed. In addition, rejection of the > Bylaws amendment at this time might actually delay mandatory reviews for > longer while the policy issues are worked out, and divert Board, Org and > Community attention from the CCG’s work. > > > > > > Susan Payne > Head of Legal Policy > > <https://comlaude.com/> > > 28 Little Russell Street, > London WC1A 2HN, UK > *T* +44 (0) 20 7421 8250 > *D* +44 (0) 20 74218 255 > > *comlaude.com <http://comlaude.com>* > > *Follow us on **LinkedIn > <https://t-uk.xink.io/Tracking/Index/pRkAAA98AAAukRcA0>** and** Youtube > <https://t-uk.xink.io/Tracking/Index/ZxkAAA98AAAukRcA0>* > > <https://www.linkedin.com/company/com-laude> > <https://twitter.com/comlaude?lang=en> > <https://www.facebook.com/ComLaude/> <https://www.youtube.com/@comlaude> > > ------------------------------ > 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 > To unsubscribe send an email to council-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. >

1 0

Two Years of Enforcing DNS Abuse Mitigation Requirements: Progress & Next Steps
by Justine Chew June 3, 2026

June 3, 2026

https://www.icann.org/en/blogs/details/two-years-of-enforcing-dns-abuse-mit… Kind regards, Justine ---------

1 0

Enforcement of Nonpublic Registration Data Disclosure Request Requirements
by Justine Chew June 3, 2026

June 3, 2026

https://www.icann.org/en/blogs/details/enforcement-of-nonpublic-registratio… Kind regards, Justine

1 0

GNSO Extraordinary Council Meeting on 07 June 2026
by Justine Chew June 3, 2026

June 3, 2026

Dear all, Following the 01 June 2026 filing of the ALAC Rejection Action Petition regarding the ICANN Board's proposed insertion of Bylaws Transition Article 27.6 on Specific Reviews, the GNSO Council is convening an Extraordinary Council Meeting on *Sunday, 07 June 2026 at 11:00 UTC (13:00 CEST)* to discuss and decide on the said petition. Please find the agenda of this Extraordinary Council Meeting *here <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/722010207/G…>* (click on the 'Agenda' tab) Non-Council members are welcomed to *join* <https://icann.zoom.us/j/92983839529?pwd=DyyxXAO3IN-_JiujB6dHDRVzkll77e1YNB0…> the meeting in observer mode. *Justine Chew* ALAC Liaison to the GNSO GNSO Liaison Workspace <https://icann-community.atlassian.net/wiki/x/15-wBQ> ------

1 0

Fwd: [council] ICANN86 Policy Outlook Report / GNSO Chair Blog
by Justine Chew June 2, 2026

June 2, 2026

FYI Kind regards, Justine ---------- Forwarded message --------- From: Julie Bisland via council <council(a)icann.org> Date: Tue, 2 Jun 2026 at 21:35 Subject: [council] ICANN86 Policy Outlook Report / GNSO Chair Blog To: council(a)icann.org <council(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Dear All, On behalf of the GNSO Team, I am happy to share the ICANN86 Policy Outlook Report and the GNSO Chair Blog: - *GNSO Chair Blog: https://www.icann.org/en/blogs/details/the-gnso-council-welcomes-you-to-ica… <https://www.icann.org/en/blogs/details/the-gnso-council-welcomes-you-to-ica…>* - *Policy Outlook Report*: https://go.icann.org/outlook86 Happy reading! With kind regards, Julie -- *Julie Bisland* Policy Operations Analyst (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) 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…> _______________________________________________ _______________________________________________ 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.

1 0

GNSO Council 10 June 2026 meeting agenda is out
by Justine Chew June 2, 2026

June 2, 2026

Dear all, Please be informed that the agenda for the GNSO Council Meeting of June 2026 during ICANN86, is as follows. I encourage you to review more more details on the marked agenda items (save for AOB) by visiting this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/722010207/G…> (please click on 'Matters of Interest'). *GNSO Council Meeting held on 10 June 2026 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/722010207/G…>* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/bAAtJ>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/AYBSJ>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/cwAtJ> - *Item 1: Administrative Matters* - 1.1 - Roll Call - 1.2 - Updates to Statements of Interest - 1.3 - Review / Amend Agenda - 1.4 - Minutes - Minutes <https://gnso.icann.org/sites/default/files/policy/2026/minutes/minutes-gnso…>of the GNSO Council Meeting on 16 April 2026 were posted on 30 April 2026. - Minutes of the GNSO Council Meeting on 21 May 2026 will be posted on 05 June 2026. - Item 2: Opening Remarks / Review of Projects Action List - 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://icann-community.atlassian.net/wiki/x/ZAyfBg> and Action Item List <https://icann-community.atlassian.net/wiki/x/ZAyfBg>. - *Item 3: Consent Agenda * - Motion to commemorate Arinola Akinyemi - Motion to commemorate Alan Barrett - Item 4: COUNCIL VOTE - RSP Issue Consideration for Potential Change Request to SPIRT - *Item 5: Council Discussion - Celebrating accomplishments between ICANN meetings* - Item 6: Council Discussion - Update on the Curative Rights Implementation Review Team - *Item 7: Board Approval of ICANN Fundamental Bylaws Amendments re: Customer Standing Committee and IANA Naming Function Review* - *Item 8: Council Discussion - Prioritization of upcoming work* - *Item 9: Any other business * - 9.1 - *ALAC Liaison Update* - 9.2 - Open mic This Council meeting will take place on *Wednesday, 10 June 2026 at 12:45 UTC for 2 hours*, and is open to observers, both in-person and remotely. Remote Participation is via Zoom - Zoom room details will be published on the ICANN84 schedule <https://icann86.sched.com/event/2NQNN/> 24 hours before the meeting. Thanks for reading / considering. *Justine Chew* ALAC Liaison to the GNSO GNSO Liaison Workspace <https://icann-community.atlassian.net/wiki/x/15-wBQ>

1 0