February 2026 - ALAC - lists.icann.org

SAC130: SSAC Comments on Name Collision Guidelines in the Proposed Language for the Draft Next Round Applicant Guidebook
by Matthias M. Hudobnik April 24, 2026

April 24, 2026

Dear Colleagues, 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…. Best, Matthias

3 4

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

April 21, 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 6

Fwd: APRALO Bytes - DNS Abuse, 23 Feb 2026
by Justine Chew Feb. 26, 2026

Feb. 26, 2026

Dear all, We are pleased to release the second *APRALO Byte *for 2026, which is on *DNS Abuse*, published at https://icann-community.atlassian.net/wiki/spaces/APRALO/pages/412844037/AP… (click on 'Read more'). As we head closer to the next ICANN public meeting in Mumbai, we thought it would be useful to focus on this topic, given the upcoming commencement of the *new GNSO PDP1 on DNS Abuse Mitigation*, and the *ICANN85 At-Large Plenary* on 10 March. 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

Report – ccNSO Council Meeting 226 - 19 February 2026
by Laura Margolis Feb. 23, 2026

Feb. 23, 2026

Dear ALAC colleagues, Please find below a summary of the ccNSO Council meeting #226, held on Thursday, 19th. February 2026 at 21:00 UTC. Agenda and Background Materials <https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/685113345/…> Working Groups written updates February 2026 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99711461/AL…> *Main topics informed and discussed:* 1. DNS Abuse & Participation in GNSO PDP 2. Progress on ccPDP4-IDN and ccPDP3 Review Mechanism – Implementation Considerations 3. Fundamental Bylaws Amendments (IANA Reviews & CSC Charter) 4. RSS Governance Working Group (RSS GWG) 5. SOI Guideline Update (Alignment with ICANN Code of Conduct) 6. Mentoring Program Relaunch (OMC) 7. ccNSO Membership – .ly (Libya) 8. CCG Review of Reviews 9. Appointments and Resignments 10. Planning for ICANN85 *1 - DNS Abuse & Participation in GNSO PDP* Following Resolution 225-01, the ccNSO requested the Domain Abuse Standing Committee (DASC <https://www.icann.org/en/ccnso/committees-and-working-groups/dns-abuse-stan…>) to nominate representatives to the GNSO PDP on DNS Abuse – Associated Domain Name Checks. The Chair informed the GNSO Secretariat of the nominations prior to 9 February 2026. In a related development, Alejandra Reynoso reported on a one-on-one meeting with the ICANN CEO where the following were discussed: - ccNSO participation in the DNS Abuse PDP. - The importance of balanced messaging in ICANN’s outreach regarding DNS abuse. Later in the meeting, Alejandra informed Council that Paul McGrady, preliminary Chair of the PDP Working Group, requested early written input from the ccNSO. Alejandra proposed responding by referencing Resolution 225-01, clarifying that: The ccNSO does not hold a unified position on the matter and its appointed members do not represent a collective ccTLD view. *2 – Progress on ccPDP4-IDN and ccPDP3 Review Mechanism – Implementation Considerations* *ccPDP4-IDN* It was reported that due to the ICANN Board workshop, the working group had not met since the previous Council meeting but would resume the following week. Work is progressing toward preparation for full Board consideration. *ccPDP3 Implementation* Bart Boswinkel provided an update on implementation discussions related to ccPDP3. The ccPAIG (ccPDP3 Implementation Advisory Group) addressed a question from the Implementation Planning Team concerning the composition of 3-member review panels. Key issue is whether non-precertified reviewers may be used if the pre-certified pool is too small to allow sufficient diversity and choice. The ccPAIG indicated: - Preference for relying on a sufficiently large and diverse pre-certified pool. - Flexibility may be required if the reviewer pool proves too limited. *Relevance to End Users:* - The Review Mechanism enhances accountability between ccTLD managers and IANA. - Diversity and independence of reviewers strengthen procedural fairness. - Robust review structures enhance confidence in root zone management decisions. *3 - Fundamental Bylaws Amendments (Articles 17 & 18) and CSC Charter* The Council discussed the public comment on amendments to: - ICANN Fundamental Bylaws Articles 17 and 18 (IANA Function Review and CSC Effectiveness Review frequency). - Customer Standing Committee (CSC) Charter (including allowing alternates). The Council unanimously agreed to: - Draft a lightweight statement supporting the proposed changes. - Submit it for adoption at Meeting #227. These amendments require Empowered Community approval. *4 – RSS Governance Working Group (RSS GWG)* The group is nearing its conclusion, with a final consensus call currently underway and the preparation of the public comment report in progress. The outcomes of the work are expected to be presented during a dedicated session at ICANN85 in Mumbai. Subject to Board consideration and approval, the process could lead to the establishment of a new governance structure for the Root Server System. In that scenario, the ccNSO is anticipated to be allocated six seats within the future governance body. *5 - SOI Guideline Update (Alignment with ICANN Code of Conduct)* Proposed updates were introduced to the ccNSO SOI Guideline, triggered by alignment with the ICANN Code of Conduct. *Key elements:* - Expanded disclosure requirements (including country of residence). - Structured escalation path for non-compliance (up to suspension). - Five-year automatic review cycle. - Structural updates and improved referencing in agendas. *Next steps:* - Councillors to review and provide feedback by February 26th. - GRC (Guidelines Review Committee) to finalize draft. - Community notification in ICANN85-Mumbai. - Anticipated approval at the April Council meeting. *6 - Mentoring Program Relaunch* The Council reviewed the proposal from the Onboarding and Mentoring Committee (OMC) to relaunch the mentoring program, building on the 2018 initiative. Reference was made to the success of the previous mentoring program, highlighting its positive impact and outcomes. Emphasis was also placed on the importance of appropriate oversight mechanisms and the consideration of regional pairing between mentors and mentees to ensure effective participation and balanced representation. The Council adopted the resolution supporting the mentoring program and instructed the Secretariat to publish the decision. * 7 - ccNSO Membership – .ly (Libya)* The membership application of the General Authority of Communication and Informatics (GACI), the new ccTLD manager for .ly. The IANA Services team identified no concerns. The Council unanimously approved the application and welcomed GACI as the 180th ccNSO member. *8- CCG Review of Reviews* Chris Disspain provided an update on the CCG Review of Reviews. The work is structured into five thematic buckets, including: - Accountability and transparency - Continuous improvement - Structural reviews - Ad hoc reviews Preparatory sessions are underway, with consultations planned in Mumbai followed by a plenary session. Input has been received from ISPC and RySG, with additional input encouraged during ICANN85. *9 – Appointments and Resignments* The Council approved the following appointments: - Idrissa Sarr (.sn) – Member, Domain Abuse Standing Committee (DASC) - Jenifer Lopez, Alejandra Reynoso, Sean Copeland (Councillors), and Nick Wenban-Smith (.uk) – Members, IGLC Review Team The council received resignations from Molehe Wesi and Stephen Deerhake. *10 - Planning for ICANN85 Elections* The Council reviewed the draft ccNSO schedule and preparation materials for Chair and Vice Chair elections. Staff clarified: - Nominations and secondments will occur during the meeting. - Voting will occur only if more than one candidate is nominated. - Chair and Vice Chair must be from different regions. This is all for now. *I will be sending you a list of recommended sessions to attend during ICANN85, shortly.* Any question or additional information you may need, please let me know. Thank you! Kindest Regards, Best, -- *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

Announcement of the Results of the At-Large Seat 15 Director Selection
by Heidi Ullrich Feb. 21, 2026

Feb. 21, 2026

Dear All, On behalf of Alan Greenberg, Chair of the Board Member Selection Process Committee (BMSPC), we are announcing the final election result of ICANN Board Director (Seat #15) selected by the At-Large Community. The nomination will be sent to the Empowered Community for the formal appointment of the Director as per the ICANN Bylaws. The At-Large Community's ICANN Board Director selection process was a six-month effort and officially ended on 19 February 2026. Justine Chew has been selected by At-Large as the successor of León Felipe Sánchez Ambía and will begin her three-year term as an ICANN Board Director at the end of ICANN87 (22 October 2026). The selection process began in September 2025 and started with the formation of two At-Large committees tasked with managing the timeline, calling for and evaluating the candidates, and organizing the final election. Four Expressions of Interest for the position were received, of which all were deemed eligible. The candidates were Sébastien Bachollet, Justine Chew, Maureen Hilyard, and Rafael (Lito) Ibarra. Before the election took place, the At-Large Community was given several opportunities to ask questions to the finalists, both verbally and in writing, to make an informed choice. The final selection was made by the fifteen (15) members of the At-Large Advisory Committee and the five (5) Regional At-Large Large Organization Chairs with the involvement of the At-Large Community. Click here<https://icann-community.atlassian.net/wiki/spaces/ABMS/pages/873005063/Fina…> to review the result, as well as detailed information about the election process. See additional information about Justine Chew on the At-Large Board Member Selection Home – 2025-2026 workspace<https://icann-community.atlassian.net/wiki/spaces/ABMS/pages/394657793/At-L…>. Kind regards, Heidi Ullrich, Silvia Vivanco, and Michelle DeSmyter At-Large Board Member Selection Program Staff Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 437 3956 Fax: +1 310 823 8649 Website: atlarge.icann.org<https://atlarge.icann.org/> Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 437 3956 Fax: +1 310 823 8649 Website: atlarge.icann.org<https://atlarge.icann.org/>

7 6

ccNSO 2025 Achievements report
by Laura Margolis Feb. 19, 2026

Feb. 19, 2026

Dear All: Please find attached the recently published report outlining the ccNSO’s key achievements in 2025. Thank you. Best regards, -- *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

GNSO Council 12 February 2026 meeting agenda is out
by Justine Chew Feb. 16, 2026

Feb. 16, 2026

Dear all, Please be informed that the agenda for the GNSO Council Meeting of February 2026, is as follows: *GNSO Council Meeting held on 12 February 2026 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/722010207/G…>* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/ZQAtJ>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/AQBQJ>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/PgA-J> - *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/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 11 December 2025 were posted on 05 January 2026. - Minutes <https://gnso.icann.org/sites/default/files/policy/2026/minutes/minutes-gnso…> of the GNSO Council Meeting on 15 January 2026 were posted on 31 January 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://gnso.icann.org/en/council/project> and Action Item List <https://community.icann.org/x/RgZlAg>. - Item 3: Consent Agenda - Confirm the GNSO-nominated ICANN Fellowship Program Mentor - *Item 4: COUNCIL VOTE - Standing Committee on Continuous Improvement (SCCI) Policy Status Report (PSR) Final Report* - *Item 5: Council Discussion - Next Steps for System for Standardized Access/Disclosure (“SSAD”) Recommendations* - *Item 6: Council Discussion - ICANN85 GAC and GNSO Bilateral Proposed Agenda* - *Item 7: Council Discussion - Prioritization of Work* - *Item 8: Any other business* - * 8.1 - Update on ICANN85 planning and Draft GNSO Schedule* - *GNSO Prep Week Webinar - 19 February 2025 at 13:00UTC* - 8.2 - ccNSO & GAC Liaison update - *8.3 - Deadline Reminders * - *Latin Script Diacritics PDP Public Comment closes on 23 February* For more details on the marked agenda items, please visit *this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/722010207/G…>* and click on 'Matters of Interest' This Council meeting will take place on *Thursday, 12 February 2026 at 21:00 UTC for 2 hours* and is open to observers remotely in listen-only mode via *this Zoom link* <https://icann.zoom.us/j/92983839529?pwd=DyyxXAO3IN-_JiujB6dHDRVzkll77e1YNB0…> . 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

ICANN85 Participation and Travel Details
by Alan Greenberg Feb. 14, 2026

Feb. 14, 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/ICANN85-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

**REMINDER** Meeting invitation: Meet the At-Large Seat 15 Board Candidates Call on Thursday, 12 February 2026 at 18:30 UTC
by ICANN At-Large Staff Feb. 12, 2026

Feb. 12, 2026

Dear All, Please join us for a call to Meet the At-Large Seat 15 Board Candidates which is scheduled for Thursday, 12 February 2026 at 18:30 UTC for 90 minutes. For other times: HERE<https://tinyurl.com/yh48n4nc> The agenda and call details can be found at: https://icann-community.atlassian.net/wiki/x/D4B6M Zoom Room: https://icann.zoom.us/j/93392733247?pwd=UyL26M4pN7TcT6rQOauFwlaz3TyYN8.1 / Passcode: Z+#@!hcP5Q Spanish & French interpretation will be provided Join instructions for phone only: See here<https://icann.zoom.us/meetings/96552363627/invitations?signature=pHsYEIbpem…> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community www.icann.org<http://www.icann.org/>

2 2

Re: Launch of The Internet Ecosystem Book
by Peter Anderson Feb. 9, 2026

Feb. 9, 2026

*(Apologies for cross-posting)* As a researcher, I have never come across a highly intensive and inclusive book like "The Internet Ecosystem". The book englobes the whole Internet Ecosystem with the correct information compared to misleading information from blogs/wikipedia on the Internet. This book was reviewed by Vint Cerf. I have just completed the reading, I will highly recommend it and it is nice to have a copy to keep for reference. Professor Peter Anderson Head of Research ------------------------------ *From:* Nikesh B. Simmandree <nikeshbs(a)outlook.com> *Sent:* Monday, August 18, 2025 1:35 PM *To:* alac-announce(a)icann.org <alac-announce(a)icann.org>; alac(a)icann.org < alac(a)icann.org>; at-large(a)icann.org <at-large(a)icann.org>; afri-discuss(a)icann.org <afri-discuss(a)icann.org> *Subject:* Launch of The Internet Ecosystem Book Dear Community, I am thrilled to announce the launch of my book, *The Internet Ecosystem* — a comprehensive exploration of the history, architecture, governance, and future of the Internet. This book distills decades of technological evolution — from ARPANET and packet switching, to AI, Web3, quantum networks, and beyond — into a clear, engaging narrative accessible to both technical and non-technical readers *What the Book Covers* - *The Past:* How Cold War research, ARPANET, and packet switching gave birth to the Internet we know today. - *The Present:* The intricate roles of ISPs, backbone providers, cloud infrastructure, AI, cybersecurity, and global governance shaping our daily online experiences. - *The Future:* Insights into 5G/6G, blockchain, immersive technologies, quantum security, and the Internet in 2050. With *49 detailed chapters*, the book provides a definitive yet approachable reference for students, professionals, policymakers, and curious readers alike. My mission with *The Internet Ecosystem* is to make the Internet’s complexity understandable — showing not only *how* the Internet works, but also *why* it matters and has become one of the most transformative human inventions — while sparking dialogue on how we build a secure, inclusive, and sustainable digital future. In the 21st century, understanding the Internet is not optional — it’s essential. Whether you’re a business leader, policymaker, educator, student, or everyday Internet user, this book provides the context and clarity you need to navigate the opportunities and challenges of our connected world. *Get Your Copy* *The Internet Ecosystem* is now available: https://payhip.com/b/hfvYg Thank you, Best Regards, Nikesh B. Simmandree +230-5-907-3413 nikeshbs(a)outlook.com This message and its attachments are intended only for the person or entity to which it is addressed and are strictly confidential. If you have received this in error, please delete it from any devices after having informed the sender.

1 0