March 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

Summary Report for GNSO Council 11 March 2026 meeting at ICANN85
by Justine Chew March 20, 2026

March 20, 2026

Dear all, Here is my report for the GNSO Council meeting held on 11 March 2026 during ICANN85. *Summary Report to the ALAC on GNSO Council Meeting #03 held on 11 March 2026 during ICANN85 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/722010207/G…> *(click on 'Report to the ALAC' tab) For brevity, I will just highlight outcomes on key issues here. You may get more information under the Matters of Interest and/or Meeting Records tabs. *1. Consent Agenda* - Paul McGrady was confirmed as the Chair of the GNSO DNS Abuse PDP 1 Working Group on Associated Domain Checks. *2. System for Standardized Access/Disclosure (SSAD) Recommendations - Next Steps* - The SSAD is a system proposed to centrally handle requests for non-public registration data, envisioned in Recommendations 1-18 of the Final Report <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phas…> of the GNSO Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Phase 2 (of October 2020). - Simply put, these Recommendations 1-18 remain pending with the ICANN Board, due mainly to feasibility concerns, and the Registration Data Request Service (RDRS) was instead implemented as a temporary solution. - Council had tasked its Registration Data Request Service (RDRS) Standing Committee to analyze the data collected on the RDRS, and in particular, the RDRS Standing Committee’s Assignment #4 was to make suggestions to Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of those SSAD recommendations. - The Standing Committee produced Recommendation 5, which provides, in part, “*the SC recommends that the Board should consider the 18 recommendations together as one package. The SC further recommends that when the GNSO Council and ICANN Board engage in a dialogue, the Council should recommend that the ICANN board reject the SSAD recommendations (as a package) and send them back to the GNSO Council for further action and Supplemental Recommendation.*” - After having accepted <https://gnso.icann.org/en/council/resolutions/2020-current#202512> the RDRS Standing Committee updated Findings Report <https://icann-community.atlassian.net/wiki/x/PjLlBg>, Council took next steps to address the Standing Committee’s Recommendation 5 – which in brief, was to recommend that ICANN Board reject EPDP Phase 2 Recommendations 1-18 as a package, to trigger the GNSO Supplemental Recommendation process. Council had discussed this with ICANN Board Liaison Wes Hardaker and Board Member Greg DiBiase to move it forward. - The Board undertook <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> this action to not adopt these Recommendations 1-18 at its meeting on 12 March 2026, and the Board Chair wrote <https://itp.cdn.icann.org/en/files/correspondence/sinha-to-payne-18-03-2026…> to the GNSO Chair on this action. - Council will now deal with the mechanism for handling the Supplemental Recommendation process. Some councilors were of the opinion that this process should be kept at Council level, while others prefer the use of a small team plus to address inclusivity for the work. - The ALAC should consider identifying a representative (and possibly, an alternate) to participate in or contribute this Supplemental Recommendation process work. - On a related issue - of Urgent Requests - there was agreement for including the period of “24 hours” into the EPDP Phase 1 Recommendation 18 text as a matter of implementation, and to avoid asking the Board to reverse adopt this recommendation, in order to not halt or further delay its implementation. Implementation will be tied to the ongoing work on authentication of LEA requestors as well as the Supplemental Recommendation process for EPDP Phase 2 Recommendations 1-18. *3. Proposed GNSO Process for Board to Reverse Adoption of GNSO Policy Recommendations* - Council considered the input <https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-co…> from the recent Public Comment Proceeding and will work towards finalization of updates to the Policy Development Process (PDP) Manual and the GNSO Guidance Process (GGP) Manual. - Based on the discussion during the meeting, I provided an additional suggestion (not inconsistent with AL-ALAC-ST-1125-01-00-EN <https://www.icann.org/en/public-comment/proceeding/proposed-gnso-process-fo…>) for Council to consider adding text to encourage deeper Board rationale in exercising this exceptional mechanism. *4. GNSO Prioritization of Work* - Discussion on Council’s prioritization of work <https://gnso.icann.org/sites/default/files/policy/2025/draft/gnso-council-p…> centered around what mechanism should be used to establish the “urgency” or ”ranking” of priorities. Discussion will continue. Thanks for reading / considering. *Justine Chew* ALAC Liaison to the GNSO GNSO Liaison Workspace <https://icann-community.atlassian.net/wiki/x/15-wBQ> On Mon, 2 Mar 2026 at 11:32, Justine Chew <justine.chew.icann(a)gmail.com> wrote: > Dear all, > > Please be informed that the agenda for the GNSO Council Meeting of March > 2026 during ICANN85, is as follows. > > It is a jam-packed agenda with lots of matters being proposed to move > forward with. > > *GNSO Council Meeting held on 11 March 2026 > <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/722010207/G…>* > > *Full Agenda* <https://icann-community.atlassian.net/wiki/x/OAA7J>* | * > *Documents* <https://icann-community.atlassian.net/wiki/x/AYBQJ>* | * > *Motions* <https://icann-community.atlassian.net/wiki/x/pYAtJ> > > - > > *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 15 January 2026, posted 31 January 2026. > - > > Minutes > <https://gnso.icann.org/sites/default/files/policy/2026/minutes/minutes-gnso…> of > the GNSO Council Meeting on 12 February 2026 were posted on 03 March 2026.* > [updated the link]* > - > > 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* > - > > *Confirm DNS Abuse Mitigation PDP 1 Working Group Chair: Paul > McGrady* > - > > *Item 4: COUNCIL UPDATE - Celebrating GNSO Accomplishments since > ICANN84* > - > > *Item 5: Council Discussion - Update on Proposed Propose to Un-Adopt > Approved GNSO Policy Recommendations* > - > > *Item 6: Council Update - Next Steps for SSAD Recommendations* > - > > *Item 7: Recap of Outcomes from the GNSO Strategic Planning Session* > - > > *Item 8: Proposed GNSO Prioritization Methodology* > - > > *Item 9: Follow-up on Accuracy Small Team Recommendation* > - > > *Item 10: Open Mic* > - > > Item 11: Any other business > - > > 11.1 - GNSO Chair Election > <https://gnso.icann.org/sites/default/files/file/field-file-attach/proposed-…> > Timeline Announcement > > 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 *Wednesday, 11 March 2026 at > 13:15 IST local time (07:45 UTC) for 2 hours *in Jasmine Hall 1B (GNSO > Room), and is open to observers both on-site and remotely. Remote > Participation is via Zoom, which link will be posted to the ICANN85 > Schedule <https://icann85.sched.com/event/2GwmF/gnso-council-meeting> 24 > hours in advance of 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

ALAC Wrap up
by Laura Margolis March 12, 2026

March 12, 2026

Dear All: I am attending the ccNSO Council Meeting at the same time as the ALAC Wrap up, so I cannot be there with you. Will be sending my report shortly. Thank you! Best, Laura -- *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

ccNSO sessions during ICANN85 in Mumbai
by Laura Margolis March 3, 2026

March 3, 2026

Dear All: This is a very brief description on what will be going on in the ccNSO during ICANN85 in Mumbai *Saturday & Sunday* will focus on governance, strategy, and committee work. Sessions will include meetings of the ccNSO Council, study groups, and committees addressing Internet governance, DNS abuse, Universal Acceptance, IANA public records, IANA’s role in disaster recovery, and ccTLD input into ICANN and PTI planning. Strategic discussions will also identify trends affecting ICANN’s mission and operations, alongside CSC reviews of IANA Naming Function performance. *Monday* will be dedicated to *ccNSO Tech Day*, featuring four community-wide sessions on technical, operational, and security topics, including a roundtable on Universal Acceptance readiness. *Tuesday & Wednesday* will host the *ccNSO Members Meeting*. Tuesday will cover Internet governance and regulatory developments, updates from ccNSO working groups and committees, and ccTLD market discussions, including global trends and regional strategy case studies. On Wednesday ccNSO will focus in community engagement, with a newcomer meet-up, the ccTLD News Session, and joint sessions on DNS abuse, discussions with ccNSO-appointed ICANN Board members, and ccTLD input into ICANN review processes. *Thursday* will conclude with the open *ccNSO Council Meeting*, featuring Council business and the annual election of ccNSO leadership. *Some recommended sessions – Please add to your agenda!* *MONDAY 9th.:* For those who want to listen to more tech sessions, you have *TECH DAY* all day, divided into 4 blocks: *TechDay (1 of 4)* *Local time:* 10:45-12:00 https://icann85.sched.com/event/2Gwn0/ccnso-tech-day-1-of-4 *TechDay & UAC (2 of 4)* *Local time:* 13:15-14:30 https://icann85.sched.com/event/2Gwmv/ccnso-tech-day-uac-2-of-4 *TechDay (3 of 4)* *Local time:* 15:00-16:00 https://icann85.sched.com/event/2Gwn3/ccnso-tech-day-3-of-4 *TechDay (4 of 4)* *Local time:* 16:30-17:30 https://icann85.sched.com/event/2Gwmy/ccnso-tech-day-4-of-4 *TUESDAY 10th.:* *Session: ccTLD Market: Trends (1 of 2) * *Local time:* 15:00-16:00 https://icann85.sched.com/event/2GwnJ/ccnso-cctld-market-trends This session will explore the latest global trends shaping the ccTLD market, including growth patterns and emerging challenges. It provides the information for the follow-up session on ccTLD market strategies. *Session: ccTLD Market: Strategies (2 of 2)* *Local time:* 16:30-17:30 https://icann85.sched.com/event/2GwnL/ccnso-cctld-market-strategies This session will focus on the market insights presented in the earlier Trends session *WEDNESDAY 11th.:* *Session: Casual Meet up for ccNSO Newcomers* *Local time:* 9:00-10:00 https://icann85.sched.com/event/2GwoM/ccnso-casual-meet-up-for-ccnso-newcom… If you would like to learn a little bit more about ccNSO, this is a welcome session for newcomers *Session: ccTLD News Session* *Local time:* 10:30-12:00 https://icann85.sched.com/event/2GwnO/ccnso-cctld-news-session ccTLD News Sessions include case studies, statistics, new developments, trends, and more. The ccTLD News Sessions have been part of the ccNSO Members Meetings for several years, offering a global platform for both experienced people and newcomers to meet, share experiences, and discuss ccTLD-related topics. *Session: ccNSO Join session with GNSO RySG on Abuse* *Local time:* 13:15-14:30 https://icann85.sched.com/event/2GwnP/ccnso-joint-session-with-gnso-rysg-on… ccTLD and gTLD registry operators face similar challenges in addressing DNS abuse. This session will briefly explain the GNSO Policy Development Process on “Associated Domain Checks” and why the ccNSO decided to participate, even though gTLD policies do not apply to ccTLDs. Associated Domain Checks involve proactive review of domains linked to malicious actors, particularly in bulk registrations. The session will conclude with examples from ccTLD managers and discussion of operational practices, including registrar API access and safeguards. *THURSDAY 12th.:* On Thursday the ccNSO will have the *Council meeting #226* Local time: 13:15-14.30 https://icann85.sched.com/event/2GwoY/ccnso-council-meeting If you would like to join me, see you there! There are many other sessions going on, any question or additional information you would like to know, please stop me at the venue anytime and I will be happy to answer. Thank you for reading! See you soon in Mumbai, or online! -- *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…>

2 1

GNSO Council 11 March 2026 meeting agenda is out
by Justine Chew March 2, 2026

March 2, 2026

Dear all, Please be informed that the agenda for the GNSO Council Meeting of March 2026 during ICANN85, is as follows. It is a jam-packed agenda with lots of matters being proposed to move forward with. *GNSO Council Meeting held on 11 March 2026 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/722010207/G…>* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/OAA7J>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/AYBQJ>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/pYAtJ> - *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 15 January 2026, posted 31 January 2026. - Minutes of the GNSO Council Meeting on 12 February 2026 were posted on 03 March 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* - *Confirm DNS Abuse Mitigation PDP 1 Working Group Chair: Paul McGrady* - *Item 4: COUNCIL UPDATE - Celebrating GNSO Accomplishments since ICANN84* - *Item 5: Council Discussion - Update on Proposed Propose to Un-Adopt Approved GNSO Policy Recommendations* - *Item 6: Council Update - Next Steps for SSAD Recommendations* - *Item 7: Recap of Outcomes from the GNSO Strategic Planning Session* - *Item 8: Proposed GNSO Prioritization Methodology* - *Item 9: Follow-up on Accuracy Small Team Recommendation* - *Item 10: Open Mic* - Item 11: Any other business - 11.1 - GNSO Chair Election <https://gnso.icann.org/sites/default/files/file/field-file-attach/proposed-…> Timeline Announcement 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 *Wednesday, 11 March 2026 at 13:15 IST local time (07:45 UTC) for 2 hours *in Jasmine Hall 1B (GNSO Room), and is open to observers both on-site and remotely. Remote Participation is via Zoom, which link will be posted to the ICANN85 Schedule <https://icann85.sched.com/event/2GwmF/gnso-council-meeting> 24 hours in advance of 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