May 2026 - ALAC - lists.icann.org

Fwd: In Memoriam: Alan Barrett
by Aftab Siddiqui May 29, 2026

May 29, 2026

A very devastating news :( Alan was an amazing person and a dear friend. Regards, Aftab A. Siddiqui ---------- Forwarded message --------- From: Andrew Alston via zanog-discuss <zanog-discuss(a)lists.nog.net.za> Date: Thu, May 28, 2026 at 4:51 PM Subject: [zanog-discuss] In Memoriam: Alan Barrett To: zanog-discuss <zanog-discuss(a)lists.nog.net.za> Cc: Andrew Alston <aa(a)alstonnetworks.net> Dear friends and colleagues, As some of you will already be aware, it is with immense sadness that we confirm, on behalf of his wife Kerry and the family, the passing of Alan Barrett. Alan died on May 28th in Cape Town, South Africa, following a diagnosis of late-stage cancer about a month ago. We are sharing this notice so that the community has accurate information at a moment when Kerry and the family need space to grieve. Alan was a friend, a willing listener, and someone who always stepped up to help when called upon. His contributions to the African Internet ecosystem were second to none, and with his passing we lose not only a friend but a giant of the industry. In 1990, Alan helped establish the very first Internet connection to South African universities, and in 1993 he co-founded the country's first commercial Internet Service Provider. In 1997 he co-authored the proposal to create AfriNIC and subsequently served on the steering committee tasked with bringing it into being. Alan served on the AfriNIC board from 2004 to 2009 and was a member of the NRO NC from 2004 to 2014. In 2015 he was appointed CEO of AfriNIC, a role he held until 2019. Beyond Africa, he was a central participant in the IANA Stewardship Transition Coordination Group, and until his death served on the ICANN board on behalf of the Address Supporting Organisation. Alan will be sorely missed by the community, his relatives and his wife, Kerry. Kerry and the family ask for privacy at this time. We will be organising an online memorial in due course and will share details once they are available. Andrew Alston Remco van Mook

18 17

GAC Liaison Report for May 2026
by Joanna Kulesza May 26, 2026

May 26, 2026

Dear colleagues, Please find below my GAC Liaison Report for May 2026. I apologise for my inability to join tonight's call due to competing commitments and am happy to respond to any questions by email. --- GAC Liaison Report to the ALAC Monthly Call May 2026 Joanna Kulesza, GAC Liaison, ALAC 1. ALAC-GAC Bilateral Meeting at ICANN86 GAC Leadership has proposed deferring the ALAC-GAC bilateral meeting to ICANN87, citing the shortened four-day format of ICANN86. In lieu of the bilateral, GAC Leadership has invited ALAC participation, through designated Topic Leads, in internal GAC discussions on DNS Abuse and on WHOIS and Registration Data. Arrangements are underway to ensure ALAC Topic Leads attend these sessions. I welcome this as a constructive step and remain available to support that engagement in my liaison capacity. 2. Registration Data Accuracy and Trilateral Dialogue The GAC Chair has requested a trilateral dialogue between the GAC, the ICANN Board, and the GNSO on domain registration data accuracy, rescheduled to a post-ICANN86 date. I have placed my availability as GAC Liaison on record and recommend that ALAC's inclusion be sought as a structural feature of the process from the outset. 3. Regulatory Developments Briefing Series Planning for the next session could not be completed this period. No feedback has been received from the ICANN Governmental Engagement team or the GAC. I will follow up with both during ICANN86. I look forward to active engagement on all open matters in Seville and will report in full following ICANN86. --- Staff: please kindly add this report to the GAC Liaison page on the wiki. Thank you. Best regards, Joanna Kulesza

1 0

SSAC report and apology for the ALAC Monthly meeting on 26/08
by Matthias M. Hudobnik May 26, 2026

May 26, 2026

Dear Colleagues, please find below my report. I apologize for not being able to attend the ALAC Monthly meeting on August 26th. Have a nice day! Best, Matthias Publications: SAC130: SSAC Comments on Name Collision Guidelines in the Proposed Language for the Draft Next Round Applicant Guidebook The SSAC welcomes the opportunity to comment on ICANN's Draft Applicant Guidebook (AGB) for the New gTLD Program: Next Round. Our comments focus on improving Section 6.7 on Name Collisions, with an emphasis on risks arising from collisions between DNS and alternative naming systems (e.g., blockchain-based systems), as outlined in the Name Collision Analysis Project Study 2 Report (NCAP2). SUMMARY OF KEY RECOMMENDATIONS: * Clarify TRT's Role in Initial Assessments AGB §6.7.2 does not clearly state that the Technical Review Team (TRT) conducts the initial name collision risk assessment. NCAP2 indicates TRT is responsible from the outset. _Recommendation:_ Explicitly assign the initial assessment to the TRT. * Enable Pre-Delegation Action on High-Risk Strings Current language suggests high-risk strings are identified only after temporary delegation. NCAP2 supports action based on existing data. _Recommendation:_ Allow TRT to recommend withholding delegation if early analysis shows high risk. * Broaden TRT's Assessment Scope Beyond DNS Data Limiting analysis to DNS logs misses collisions from alternative namespaces that resolve via DNS (e.g., users accustomed to _.wallet_ from blockchain). _Recommendation:_ Permit use of OSINT, qualitative assessments, and external data sources per NCAP2. * Allow TRT Flexibility to Evolve Assessment Methods AGB cites four NCAP2 methods (NI, CI, VI, VIN), but doesn't state whether TRT may adopt new techniques. _Recommendation:_ Affirm TRT's discretion to evolve methods to address future risks. These updates will better align the AGB with NCAP2 and ICANN Board guidance, while improving transparency, security, and technical rigor in handling name collisions. The SSAC appreciates the efforts of the ICANN org and Subsequent Procedures IRT, and we are available for further discussion. Link: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe…. Ongoing work parties: * DNSSEC Operational Considerations Work Party * Open-Source Software Work Party * Responsible Integration of External Technologies into the DNS * SSAC Workshop Work Party SSAC Membership Applications: The application deadline is closed now and potential candidates are being assessed by the Membership Selection Committee. SSAC Workshop: For SSAC members only, will be held in September in Mexico City.

2 7

GNSO Council 21 May 2026 meeting agenda is out
by Justine Chew May 25, 2026

May 25, 2026

Dear all, Please be informed that the agenda for the GNSO Council Meeting of May 2026, is as follows. I encourage you to review more more details on the marked agenda items (save for Item 6: 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 21 May 2026 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/722010207/G…>* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/MoA_J>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/CIBNJ>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/kgA3J> - *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 11 March 2026 were posted on 29 March 2026. - 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. - 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: COUNCIL VOTE - Board Un-Adoption Process in Updated GGP and PDP Manuals* - *Item 4: COUNCIL VOTE - Council Process for Response to SPIRT Request * - *Item 5: Council Discussion - GNSO Mechanism for Work Prioritization* - *Item 6: Any other business* - 6.1 - ICANN86 Planning - GNSO Prep Week Webinar - 28 May 2026 at 13:00 UTC - questions will be taken from GNSO Council only - *6.2 - DNS Abuse PDP2 Charter Drafting* - 6.3 - SPIRT Issue regarding RSP This Council meeting will take place on *Thursday, 21 May 2026 at 05:00 UTC for 2 hours*, and is open to observers remotely. Remote Participation is via this Zoom link <https://icann.zoom.us/j/92983839529?pwd=R0BcWsye1mbmk1uFXUbeN42WAt2jyP.1>. Thanks for reading / considering. *Justine Chew* ALAC Liaison to the GNSO GNSO Liaison Workspace <https://icann-community.atlassian.net/wiki/x/15-wBQ>

1 1

ccNSO Council Meeting 229 Summary
by Laura Margolis May 25, 2026

May 25, 2026

Dear all, I hope you are doing fine. Please find below a summary of the main discussions, decisions, and action points from the ccNSO Council Meeting #229 held on 21 May 2026. Full Agenda and Background Materials <https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/685408257/…> WG written updates <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99711461/AL…> – May 2026 *Administrative Matters* - Minutes from Meeting #228 were approved. - All outstanding action items from Meeting #228 were completed, except for one item assigned to the Triage Committee, which remains scheduled for future work. *Intermeeting and Triage Updates* - Approval comments regarding the Co-Chair's Review of Reviews refined outline were adopted between meetings. - The Triage Committee reviewed three requests and made recommendations related to NomCom leadership expressions of interest, approval/rejection actions, and Ombuds survey participation. - Discussion took place regarding the Triage Committee mandate and decision-making authority, with additional discussions expected offline. *Policy and Working Group Updates* - Progress on ccPDP4-IDN and implementation activities continues. A caucus group is reviewing policy sections and identifying implementation considerations. Four clarification questions for the ccNSO are expected. - Progress on the Review of Reviews initiative and upcoming planning for Seville was noted. - Updates were provided on the GNSO DNS Abuse Mitigation PDP1, including the appointment of Nick Wenban-Smith as Vice Chair. *Chair and Community Updates* - Jordan Carter's continuation on Council following affiliation changes was confirmed without objections. - The Chair's meeting with ICANN leadership was postponed and will be rescheduled. - Updates were shared from regional organizations including CENTR, LACTLD, and APTLD activities. *Decisions Approved* The Council approved: - Adoption of the ccNSO Board Director Removal, NomCom Board Director Removal, and Board Recall Guidelines. - Launch of a call for volunteers for a ccNSO appointee to the NomCom. - Multiple appointments: • Luis Diego Espinoza as Vice Chair of Tech WG • Irina Danelia and Charles Noir for the Planning Prioritization Process Group • Grace Mwikarago as member of MPC Discussion took place regarding how abstentions should be handled in combined (omnibus) resolutions, particularly when a councillor is directly affected by only part of a decision, and how the rationale for such abstentions should be documented in future meeting records." *Portfolio and Work Planning* - Portfolio monitoring and work plan updates were presented. - Some study groups will require additional time and now target completion by ICANN87. - Staff changes in the Secretariat beginning in October may impact the launch of new initiatives, with recommendations to delay additional work until transition activities stabilize. *Upcoming Activities* - Updated Board Nomination Guidelines were introduced and opened for Council review, with comments due by 29 May. - Preparations for ICANN86 in Seville continue, including Council preparation calls, meeting planning, and agenda coordination. This report, as well as more information is uploaded in the ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…> *I will send you an email, shortly regarding the recommended sessions for ICANN86.* Thank you! Best 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

ICANN86 Participation and Travel Details
by Alan Greenberg May 18, 2026

May 18, 2026

For those who want to share their travel information (just for information or to facilitate ride-sharing), the Google spreadsheet is at http://tinyurl.com/ICANN86-At-Large-Travel. Or to simply say you will be attending in person or remotely. If I know the address you use for Google, you should have access, otherwise request access. If you know of someone who is travelling but not on this list, please feel free to share. Staff welcome as well. Alan

1 0

Correspondences from GAC to GNSO and the Board on RDA
by Justine Chew May 17, 2026

May 17, 2026

Dear ALAC colleagues, Please find attached FYI, 2 letters from the GAC Chair to the GNSO Chair, and the GAC Chair to the Board Chair and GNSO Chair, respectively. In brief, both have to do with the topic of RDA (domain registration data accuracy) 1. The first letter is about a pre-ICANN86 GAC Webinar to discuss with GNSO the 15-day timeline for registrars to validate and verify registrants contact information; and 2. The second letter is the GAC Chair's request to re-convene a GAC-Board-GNSO trilateral dialogue to address RDA during ICANN86, and to discuss policy prioritization in the longer term. We do not believe we have an active role in either meeting, but should, if possible, pay attention to both. Kind regards, Justine ------ *Justine Chew* At-Large Advisory Committee (ALAC) Liaison to the GNSO Internet Corporation for Assigned Names and Numbers (ICANN) At-Large website: https://atlarge.icann.org/ ------

6 9

ICANN Adds Urgent Requests Requirement to Registration Data Policy
by Justine Chew May 16, 2026

May 16, 2026

FYI -- https://www.icann.org/en/announcements/details/icann-adds-urgent-requests-r… As of 12 May 2026, the ICANN Registration Data Policy <https://www.icann.org/en/contracted-parties/consensus-policies/registration…> has been updated to include requirements for *ICANN contracted parties to respond within 24 hours to urgent requests for the lawful disclosure of generic top-level domain nonpublic registration data from authenticated requestors*. Urgent requests include situations that pose an imminent threat to life, of serious bodily injury, to critical infrastructure, or of child exploitation where disclosure of data is necessary in combatting or addressing the threat. *The urgent request policy language will not go into effect until an authentication mechanism for law enforcement is implemented.* Discussion about development of an authentication mechanism is currently in process in the Governmental Advisory Committee's Public Safety Working Group. ICANN has participated in these conversations with law enforcement, GNSO stakeholder groups, and members of civil society to understand the available tools, technologies, and desired features for an authentication mechanism. *ICANN org is developing a proof-of-concept test with law enforcement experienced in authentication, such as Interpol and the FBI*. This testing will help ICANN and the community develop requirements for identity providers. *This work will also support a long-term solution for requesting nonpublic registration data, once supplemental policy recommendations for the System for Standardized/Access Disclosure are finalized.* Kind regards, Justine

3 2

APRALO Bytes - WSIS+20 Outcome: Shaping the Future of IGF, 15 May 2026
by Justine Chew May 15, 2026

May 15, 2026

Dear all, We are pleased to release the next *APRALO Byte *for 2026, which touches on *WSIS+20 Outcome*, specifically on initial steps to *shaping the future of the Internet Governance Forum (IGF)*, published at https://icann-community.atlassian.net/wiki/spaces/APRALO/pages/412844037/AP… (click on 'Read more'). We hope to receive continued keen interest from our readership and will be doubling efforts to secure more Byte contributions from the APRALO community. Kind regards, APRALO Leadership Team ---------------------- *APRALO Bytes* (see: https://icann-community.atlassian.net/wiki/x/BYCbG) is aimed at *keeping the community apprised *of issues or topics of importance to the At-Large and/or APRALO community in a manner that is *issue/topic-focused, informative yet lightweight, while encouraging community interest and discourse* in such issues/topics. Feedback and contributions are welcomed; please reach out if you wish to contribute a Byte.

1 0

APRALO Bytes - Broadening participation, Engaging Newcomers, 05 May 2026
by Justine Chew May 15, 2026

May 15, 2026

Dear all, We would like to share an *APRALO Byte* from earlier this month (05 May 2026), which is on *Outreach and Engagement*, in particular, an overview of* how the APRALO ICANN Readouts are evolving to broaden participation and engage newcomers*. This Byte is published at https://icann-community.atlassian.net/wiki/spaces/APRALO/pages/412844037/AP… (click on 'Read more'). Kind regards, APRALO Leadership Team ---------------------- *APRALO Bytes* (see: https://icann-community.atlassian.net/wiki/x/BYCbG) is aimed at *keeping the community apprised* of issues or topics of importance to the At-Large and/or APRALO community in a manner that is *issue/topic-focused, informative yet lightweight, while encouraging community interest and discourse* in such issues/topics. Feedback and contributions are welcomed; please reach out if you wish to contribute a Byte.

1 0