June 2025 - ALAC - lists.icann.org

ALAC Liaison to the GAC updates: GAC Joint Webinar Invitation, Prague Bilateral Agenda, and May Briefing – Request for Input by 5 May
by Joanna Kulesza July 21, 2025

July 21, 2025

Dear Colleagues, I hope this message finds you well. I am writing to share several updates and to seek your input on key upcoming ALAC engagement opportunities with the GAC: ------------------------------ *1. Invitation to ASO-GAC Webinar on the RIR Governance Document (13 May, 13:00 UTC)* Marco Hogewoning, GAC VC, has extended an invitation to ALAC to participate in a *joint ASO-GAC webinar* on the proposed *Governance Document for the Recognition, Maintenance, and Derecognition of RIRs* (a revision of ICP-2). The session will take place on *Tuesday, 13 May at 13:00 UTC* for 90 minutes. The webinar will provide an overview of the draft, which is currently open for public comment until *27 May 2025*: 🔗 ICANN Public Comment Page <https://www.icann.org/en/public-comment/proceeding/governance-document-for-…> 🔗 ICP-2 Background <https://www.nro.net/policy/internet-coordination-policy-2/> Given the relevance of this topic to ALAC, I strongly encourage participation. Please also consider whether ALAC should offer a brief intervention during the session—perhaps by *Jonathan Zuck*, ALAC Chair, should he be willing and available. ------------------------------ *2. GAC-ALAC Bilateral Meeting at ICANN83 – Draft Agenda and Speaker Suggestions* Kristina has proposed the following agenda for our bilateral session, with two suggested ALAC speakers: - *Applicant Support Program (ASP) – Equity in the Next gTLD Round [recommended]* *Suggested Speaker: Avri Doria* - *DNS Abuse Mitigation – Policy, Enforcement, and End User Protection* - *Universal Acceptance (UA) and the Multilingual Internet* - *Domain Name Registration Data – RDRS, Accuracy, and Access* - *Digital Inclusion and Capacity Building* - *Public Interest Frameworks and Advisory Roles * *[recommended]* *Suggested Speaker: Justine Chew* Your comments and additional suggestions are welcome. Please kindly note that given our usual, limited timing for these sessions, we are likely to cover no more than two topics of shared interest. My recommendations, as your liaison to the GAC, are noted above. ------------------------------ *3. May Regulatory Updates Briefing – Call for Input* Together with our GAC colleagues, we are ready to welcome your suggestions for the topic to be covered during our May Regulatory Updates Briefing <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/180715827/G…> session, the last one before our Prague meeting. Zeina has originally proposed a focus on *infrastructure governance in the Middle East* as one of the topics for us to consider during these sessions, whereas we await further ideas from the Governmental Engagement team. I would appreciate any additional suggestions from the ALAC regarding policy topics or regional insights that should be reflected in this session. ------------------------------ *Kindly provide your feedback on the above items by Monday, 5 May.* Thank you for your attention to this matter and lasting support. -- Kind regards, Joanna Kulesza ------------------- Joanna Kulesza, PhD Professor of International Law Lodz Cyber Hub / University of Lodz Law School / Poland www.cyber.uni.lodz.pl (EURALO ALS 341) ALAC / EURALO / ALAC Liaison to the GAC

10 18

Petition for EC Request for Reconsideration of the Board's decision on reviews
by Jonathan Zuck June 26, 2025

June 26, 2025

Folks, As discussed, here is the Empowered Community Petition for a Request for Reconsideration of the Board’s May 19 decision on reviews. We are now on the clock to find allies. Jonathan

6 12

Re: [CPWG] Re: The DNS Is Broken - Response
by Seun Ojedeji June 19, 2025

June 19, 2025

I do agree with Michael that we should not loose sight of the fact that ATRT was a process enshrined into ICANN bylaw(re:ATRT). The issue for me is not a question of whether ATRT should remain or not but how ICANN is attempting to get rid of ATRT. If the process has become such a resource guzzling activity then ICANN should come back to the community to find a fix to it. ATRT 3 still has less than 60% implementation, unless a new ATRT will be looking into a major structural review, allowing more time to implement v3 and introducing a lighter version ATRT may be a good way forward but that discussion needs to have occurred within the community (and the Board). Once a force has been able to get a vehicle jump started, it's good to let go, continuing to push the vehicle can be a waste of resources. Previous ATRTs have achieved a lot of the objective of the activity and perhaps a longer periodic trigger for ATRT would be ideal if having a lighter version with much smaller scope is not desirable by the community. Regards On Wed, 18 Jun 2025 at 13:07, michael palage.com via CPWG <cpwg(a)icann.org> wrote: > Thanks for pointing out Milton’s constructive response. > > > > I have responded to his comments to hopefully continue a constructive > dialogue. > > > > *From: *Judith Hellerstein via CPWG <cpwg(a)icann.org> > *Date: *Wednesday, June 18, 2025 at 12:08 PM > *To: *Carlton Samuels <carlton.samuels(a)gmail.com> > *Cc: *CPWG <cpwg(a)icann.org>, alac(a)icann.org <alac(a)icann.org> > *Subject: *[CPWG] Re: The DNS Is Broken - Response > > Hi Carlton, > > Very interesting. Milton is not wrong in many of his points. > > > > Judith > > Sent from my iPad > > judith(a)jhellerstein.com > > Mobile: +1202333517 > > > > On Jun 18, 2025, at 12:00 PM, Carlton Samuels via CPWG <cpwg(a)icann.org> > wrote: > > > > Y'all might have already seen on one or other of these lists the article > authored by Michael Palage and now published in CirceID. > > > > The response from one of my favourite polemicists, Milton Mueller, is as > interesting. > > > > https://circleid.com/posts/icann-is-broken > > > > Carlton > > ============================== > *Carlton A Samuels* > > *Mobile: 876-818-1799 Strategy, Process, Governance, Assessment & > Turnaround* > ============================= > > _______________________________________________ > CPWG mailing list -- cpwg(a)icann.org > To unsubscribe send an email to cpwg-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. > > _______________________________________________ > CPWG mailing list -- cpwg(a)icann.org > To unsubscribe send an email to cpwg-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. > -- ------------------------------------------------------------------------ *Seun Ojedeji,* Bringing another down does not take you up - think about your action!

2 1

Re: [CPWG] The DNS Is Broken - Response
by Judith Hellerstein June 18, 2025

June 18, 2025

Hi Carlton, Very interesting. Milton is not wrong in many of his points. Judith Sent from my iPad judith(a)jhellerstein.com Mobile: +1202333517 > On Jun 18, 2025, at 12:00 PM, Carlton Samuels via CPWG <cpwg(a)icann.org> wrote: > > > Y'all might have already seen on one or other of these lists the article authored by Michael Palage and now published in CirceID. > > The response from one of my favourite polemicists, Milton Mueller, is as interesting. > > https://circleid.com/posts/icann-is-broken > > Carlton > ============================== > Carlton A Samuels > Mobile: 876-818-1799 > Strategy, Process, Governance, Assessment & Turnaround > ============================= > _______________________________________________ > CPWG mailing list -- cpwg(a)icann.org > To unsubscribe send an email to cpwg-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

Summary Report for GNSO Council 11 June 2025 meeting
by Justine Chew June 15, 2025

June 15, 2025

Dear all, Just a very short note to let you know of my summary report for the GNSO Council meeting that took place during ICANN83. Please visit this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/265846872/G…> and then click on the ALAC report sublink. Happy to answer questions, if any. Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Y…> --------- On Sat, 31 May 2025, 14:58 Justine Chew, <justine.chew.icann(a)gmail.com> wrote: > Dear all, > > Please be informed that the agenda for the GNSO Council Meeting taking > place on Wednesday, 11 June 2025 during ICANN 83 is as follows: > > *GNSO Council Meeting #6 of 2025 held on 11 June 2025 during ICANN83* > > *Full Agenda* <https://icann-community.atlassian.net/wiki/x/IKafBg>* | * > *Documents* <https://icann-community.atlassian.net/wiki/x/2KefBg>* | * > *Motions* <https://icann-community.atlassian.net/wiki/x/NKifBg> > > - > > *Item 1: Administrative Matters* > - > > 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://gnso.icann.org/en/council/project> and Action Item List > <https://community.icann.org/x/RgZlAg> > - Item 3: Consent Agenda > - Deferral of Whois Implementation Advisory Group work > - *Item 4: COUNCIL DISCUSSION - Prioritization of Upcoming Work* > - *Item 5: COUNCIL UPDATE - Update from Board Readiness Small Team* > - *Item 6: COUNCIL UPDATE - Progress Update from Council Accuracy > Small Team* > - *Item 7: COUNCIL UPDATE: Status Update from DNS Abuse Small Team* > - *Item 8: COUNCIL DISCUSSION: Update on Reviews* > - Item 9: Any Other Business > - 9.1 - Open Mic > > > For more details on the marked agenda items, please visit *this link > <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/265846872/G…>* > and > *click on 'Matters of Interest'* > As usual, non-Council members are welcome to attend the meeting as > observers only, save for item 9.1 Open Mic. If you are interested in > observing this meeting either in-person or online via Zoom, please refer t > o https://icann83.sched.com/event/246XL for meeting details, noting that > the Zoom link will only be made available 24 hours prior to the meeting.. > > Thanks for reading / considering. > > Justine Chew > ALAC Liaison to the GNSO > GNSO Liaison Report Workspace > <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Y…> > ------ > > > >

2 1

Re: At-Large Response to ICANN Board regarding ATRT4
by Alfredo Calderon June 4, 2025

June 4, 2025

As an At-Large community member the Request for Reconsideration (RfR) is a clear documented communication to the Board. I support the submission of the request. The second document has a solid timeline to gather support from the ICANN community to gather support to move forward on the next steps to meet the deadline as required by the bylaws for situations similar to this travesty of the Board. Alfredo Calderon At-Large community member Alfredo Calderon Email: calderon.alfredo(a)gmail.com Twitter: acalderon52 LinkedIn: pr.linkedin.com/in/acalderon52 Skype: alfredo_1212 Business Card: http://myonepage.com/acalderon Blog: https://aprendizajedistancia.blogspot.com VSIG: Virtual School on Internet Governance - https://virtualsig.org

1 0

At-Large Response to ICANN Board regarding ATRT4
by Jonathan Zuck June 4, 2025

June 4, 2025

After a lot of discussion, research and drafting, the ALT would like to recommend to the ALAC to engage in a number of steps with respect to the Board’s decision to postpone ATRT4. There’s been quite a bit of discussion on this list, a blog post by Avri and a draft by Daniel, all of which are rolled into the following plan we would like to propose. Olivier, who got this conversation started on the list, referred to ALAC advice on this matter but technically, that was merely correspondence in follow-up to the ALAC-Board meeting in Seattle. So the first step would be to convert it to Advice. Next we would file our own Request for Reconsideration (RfR) to the Board, to ensure we make the deadline. Here is a draft RfR for your review: https://docs.google.com/document/d/1uvknIIFoJhUCDVoHo-ydJdwxU1A76Y3WFrnIABO… Finally, we would attempt to gather support from others in the community for a Community RfR. The whole plan and timeline are outlined here: https://docs.google.com/document/d/1zVe_YZHlgSlx1GpJNfw0bOqcq9ZqAwdw6ILY9kx… Please take the next couple of days to familiarize yourself with these two documents, the draft RfR in particular, and get back to me with any feedback and we’ll get this process started within the ALAC. Thank you for your patience on this as we worked to get organized. Jonathan Jonathan Zuck Chair, ALAC

3 2

Saludos a todos
by Sandra Rodriguez June 4, 2025

June 4, 2025

Estimados, Encuentre una lista de sesiones relacionadas con UA en ICANN83 en Praga. La sesión principal que les recomendamos es " Celebrando 10 años de UASG y avanzando ". Agradecemos enormemente su participación. Actualizaciones, reuniones y sesiones relacionadas con la UA en la ICANN 83 Semana de reuniones (9-12 de junio de 2025) Día/Fecha Tiempo Habitación Sesión Lunes, 9 de junio de 2025 13:45-15:00 Sala Sur 3 C (General) Sesión de políticas generales (temas de IDN y UA) Martes 10 de junio de 2025 13:45 - 15:00 Pabellón Sur 3 A/B (ccNSO) ccNSO: Rompiendo barreras: cómo los gobiernos y los ccTLD impulsan la autenticación universal Miércoles 11 de junio de 2025 15:30 - 17:00 Terraza 2B Celebrando 10 años de UASG y avanzando Atentamente, UASG

1 0

Recommended ccNSO Sessions at ICANN83 for the At-Large Community
by Laura Margolis June 3, 2025

June 3, 2025

Dear All, As ICANN83 approaches, I would like to recommend you to attend some ccNSO sessions that may be of particular interest to the ALAC and At-Large community, especially regarding Universal Acceptance, DNS abuse and Internet Governance: *TUESDAY 10th. * *🟦 10:45–12:15 - IGLC Session: 20 Years of WSIS Implementation* Schedule: https://icann83.sched.com/event/246Y6/ccnso-20-years-of-wsis-implementation… The IGLC (Internet Governance Liaison Committee) session will explore how the principles established in the WSIS process have been implemented over the past two decades and the specific ways in which ccTLDs have contributed to this implementation, namely, through their engagement in national and regional Internet Governance Forums. *🟦 13:45–15:00 - UAC: Breaking Barriers – How Governments and ccTLDs Advance Universal Acceptance* Schedule: https://icann83.sched.com/event/246Y7/ccnso-breaking-barriers-how-governmen… This session will explore how ccTLDs and governments can help overcome barriers to Universal Acceptance and promote digital inclusion. *🟦 15:30–17:00 - ccTLD Financial Contributions * Schedule: https://icann83.sched.com/event/246Y9/ccnso-cctld-financial-contributions An important conversation on how ccTLDs support ICANN, including models that promote fairness and voluntary contributions. The group is aiming to deliver community-endorsed recommendations to the ccNSO Council by ICANN83. *WEDNESDAY 11th.* *🟦 10:45–12:15 - ccTLD News Session* Schedule: https://icann83.sched.com/event/246YC/ccnso-cctld-news-session ccTLD News Session is a classic during ICANN meetings, and includes a collection of case studies, statistics, new developments, trends, and more. *🟦 13:45–15:00 - DASC Session: Online Scams and Financial Crime* **Highly recommended* Schedule: https://icann83.sched.com/event/246YD/ccnso-dasc-online-scams-and-financial… This session will explore online scams, financial crime, and their connection to domain name related abuse. The focus will be the ccTLD perspective. *🟦 15:30–17:00 - Joint ccNSO–GNSO RySG Session* A cross-community exchange on shared issues like DNS abuse, regulatory developments, and DNS resilience. Schedule: https://icann83.sched.com/event/246YG/ccnso-joint-session-with-ccnso-and-gn… *THURSDAY 13th* *🟦 10:45–12:15 - ccNSO Council Meeting: * Schedule: https://icann83.sched.com/event/246ZA/ccnso-council-meeting Here is a link to *all* the ccNSO sessions: https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/19841024… ** You are all more than welcome to join me and attend all the sessions! Thank you for reading and for those going to Prague, safe travels! Best regards, *Laura Margolis* ALAC Liaison to ccNSO margolisl(a)gmail.com +59899690992 ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

2 2

URGENT: Approved Resolutions | Special Meeting of the ICANN Board | 19 May 2025 // ICANN Reviews Program Path
by Olivier MJ Crépin-Leblond June 2, 2025

June 2, 2025

Dear Colleagues, I don't often write to the ALAC mailing list as I mostly observe what's going on here, but seeing what seems to be no action on a Core Accountability measure of ICANN being simply cast aside, and with possibly only three days to go, with neither action on the OFB working group, or the ALAC mailing list, it is time for me to point something out urgently. On 19 May 2025, the ICANN Board held a special meeting in which it passed Resolutions 2025.05.19.01 – 2025.05.19.06. These can be read at: https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… Summarised: The ICANN Board has directed its President and CEO to design a review program aimed at improving *accountability, transparency, and effectiveness* within ICANN, with an emphasis on community-led processes. To achieve this, a *community dialogue* will be initiated to identify key areas for improvement. Key resolutions include: * *Progressing the Continuous Improvement Program* (CIP) while deferring Organisational Reviews until the first cycle is complete. * *Concluding the Pilot Holistic Review* (PHR), allowing ongoing work within SOs and ACs on continuous improvement. * *Deferring ATRT4, SSR, and RDS Specific Reviews* until the community dialogue informs next steps. * *Considering future actions* on Organisational Reviews after one CIP cycle. * *Planning a community dialogue* on ICANN Reviews, incorporating input from the ICANN84 Public Meeting. * *Recognising contributions* from the PHR Team and the broader ICANN community in shaping review processes. The rationale says that the Board's decisions reflect a commitment to *collaborative review mechanisms* that ensure ICANN remains effective and transparent. Unfortunately, in practice, the resolution that the Board has passed is likely to foster exactly the opposite. This decision was transmitted to SO/AC Chairs and can be read at: https://atlarge.icann.org/en/advice_statements/14007 The Board took this decision *against *ALAC Advice provided at: https://atlarge.icann.org/en/advice_statements/14003 So what are we to do, as an Advisory Committee, besides being shocked and stunned? The ICANN Board has a duty to act according to the ICANN Bylaws. The ICANN Bylaws mandate Periodic Review Mechanisms and also mandate Reconsideration Requests as part of Article IV of its Bylaws published on https://www.icann.org/en/governance/bylaws#article4 * Section 4.2. RECONSIDERATION * Section 4.4. PERIODIC REVIEW OF ICANN STRUCTURE AND OPERATIONS * Section 4.5. ANNUAL REVIEW * Section 4.6. SPECIFIC REVIEWS The periodicity of Reviews is mandated in order to avoid situations where reviews would be stopped altogether. "Section 4.6 (b) (vi) The Accountability and Transparency Review shall be conducted no less frequently than every five years measured from the date the previous Accountability and Transparency Review Team was convened." The last Accountability and Transparency Review Team (ATRT3) was appointed on 20 December 2018: https://www.icann.org/en/announcements/details/members-announced-for-the-th… Thus the next ATRT should have been appointed by "no less frequently than every five years" thus by *20 December 2023*. The Board at the time decided to delay the start of ATRT4. We are now *18 months late* to start this. It is now continuing to extend the delay to the start of ATRT4, thus contravening Bylaw Section 4.6 (b) (vi). According to: /Section 4.2 (c) A Requestor may submit a request for reconsideration or review of an ICANN action or inaction ("Reconsideration Request") to the extent that the Requestor has been adversely affected by: (i) One or more Board or Staff actions or inactions that contradict ICANN's Mission, Commitments, Core Values and/or established ICANN policy(ies);/ The Board is acting against its own Bylaws. The ALAC should submit a *Reconsideration Request *without further delay, based on the fact that the Board is now acting against its own Bylaws. A *Community Reconsideration Request* might have even more weight, but we have to be quite lucid about the fact that some other SOs/ACs/SGs, such as the Country Code Name Supporting Organisation (ccNSO) and the Registries Stakeholder Group (RySG) would oppose such Community Reconsideration as they have expressed their support for interrupting the review cycle. I have marked this message as "URGENT" because whilst the Bylaws mention a 30 day period for Reconsideration Requests, the Web Page explaining the reconsideration process ( https://www.icann.org/resources/pages/mechanisms-2014-03-20-en ) mentions only 15 days - obviously an error somewhere, but you never know, with ICANN... I'll remind everyone: whilst Bylaw-mandated Reviews might be tedious, repetitive and introduce a large workload on the Community, they are *Bylaw-mandated* for a reason: in order to make sure that *ICANN remains Accountable, Transparent, enhancing Public Trust*, and to ensure its decision-making processes remain *open, fair, and aligned with the public interest.* The reason given in relation to delaying ATRT4 is that ICANN Org is struggling to implement all of the recommendations made in past reviews, and ATRT3 in particular. This failure of ICANN Org to implement recommendations is unacceptable. It is about time that the ALAC calls this out. It used to be the US Department of Commerce (DoC) that used to do this and bang on the table. Unfortunately we now are reaching a level of complacency that is contravening ICANN's own Bylaws and this has to stop. I trust that you, the ALAC acting in the best interests of Internet users worldwide, will support filing a Reconsideration Request as soon as possible. Kindest regards, Olivier Crépin-Leblond (writing in my own personal capacity)

12 22