August 2025 - 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

Invitation to APAC Webinar on ICANN’s Applicant Support Program (ASP), 3 Sep 2025 at 05:00 UTC
by Justine Chew Sept. 3, 2025

Sept. 3, 2025

Dear colleagues, For the first time in over a decade, businesses, communities, regional and local governments, non-profits, and other organizations will have the opportunity to apply for a new generic top-level domain (gTLD). A TLD is the part of a web address that comes after the last dot. For example, in www.icann.org, “.org” is the TLD. TLDs are unique digital assets that can be used to serve diverse cultural, geographic, linguistic, and professional communities, and provide a unique and secure space for customers and constituents online. Today there are more than 1,200 new gTLDs representing brands and businesses like .microsoft and .toyota, cities and regions like .amsterdam, and communities like .kids. Plus, there are gTLDs available in different scripts representing many languages. The Internet Corporation for Assigned Names and Numbers (ICANN) is the organization that coordinates the Internet’s Domain Name System. ICANN <http://www.icann.org/>, in partnership with the Asian, Australasian and Pacific Islands Regional At-Large Organization (APRALO) <https://icann-community.atlassian.net/wiki/x/AoDdBg>, will host a webinar mainly for prospective and current applicants from the Asia Pacific to learn more about the resources available to help with the ASP and gTLD application processes. The webinar will cover: - How a gTLD can be used to create a meaningful and trusted digital space. - The availability of financial and non-financial assistance through the Applicant Support Program including information on how to apply and qualify for support. - Introductions to volunteer professional service providers and mentors, willing to provide general business support, application assistance, or technical assistance. - Key dates and milestones ahead. *Join us on 3 September 2025 at 05:00 UTC. Pre-registration <https://icann.zoom.us/webinar/register/WN_zs1c7B-9RXWFsUkP4mmh6w> is required.* Please feel free to share this invitation with interested persons, especially from the APAC region. Kind regards, APRALO Leadership Team

1 1

APRALO Bytes - Applicant Support, 26 Aug 2025
by Justine Chew Aug. 28, 2025

Aug. 28, 2025

Hello again everyone, Here is this week's *APRALO Byte*, which is on the topic of *Applicant Support*, published at https://icann-community.atlassian.net/wiki/spaces/APRALO/pages/412844037/AP… (click on 'Read more'). We would also like to take the opportunity to invite you to join the Applicant Support Program Webinar for the APAC Region <https://icann-community.atlassian.net/wiki/x/GABmGg> to be held on 3 September 2025 at 05:00 UTC, hosted by ICANN in partnership with APRALO. Pre-registration <https://icann.zoom.us/webinar/register/WN_zs1c7B-9RXWFsUkP4mmh6w> is required. Kind regards, APRALO Leadership Team *------------**----------* *APRALO Bytes* (see: https://icann-community.atlassian.net/wiki/x/BYCbG) is an APRALO initiative 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. .

5 4

APRALO Bytes - Review of ICANN Reviews, 13 Aug 2025
by Justine Chew Aug. 27, 2025

Aug. 27, 2025

Dear all, We are pleased to share the second *APRALO Byte*, which is on the topic of *Review of ICANN Reviews*, 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 an APRALO initiative 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.

1 0

APRALO Bytes - DNS Abuse, 6 Aug 2025
by Justine Chew Aug. 27, 2025

Aug. 27, 2025

Hello everyone, At the August 2025 ALAC Monthly Call <https://icann-community.atlassian.net/wiki/x/AQCeFw>, it was reported that APRALO has introduced a new initiative called *APRALO Bytes* which is single issue bulletin initiative aimed at keeping the APRALO community apprised of issues or topics of importance to the At-Large and/or APRALO community in a manner that is informative yet lightweight, while encouraging community interest and discourse in such issues/topics. The first Byte was on DNS Abuse (6 Aug), the second was on Review of ICANN Reviews (13 Aug) and the latest one was on Applicant Support (26 Aug). The first APRALO Byte on *DNS Abuse*, which is published at https://icann-community.atlassian.net/wiki/spaces/APRALO/pages/412844037/AP… (click on 'Read more'). The second and third Bytes will be shared separately. We hope you will find our Bytes informative ! With kind regards on behalf of the APRALO Leadership Team, Justine

1 0

ccNSO August 2025 meetings Report
by Laura Margolis Aug. 26, 2025

Aug. 26, 2025

Dear All: I hope you are all doing fine. During August, in addition to the monthly council meeting on August 21st., an extraordinary meeting was held on August 7th. *Extraordinary meeting on August 7th., 2025* During that meeting the ccNSO Council approved support of the Review of Reviews CCG Charter, adopted criteria for nominees, agreed to appoint two candidates, and endorsed both the formation of a Selection Committee and the related timeline. The final selection was made on August 19th. All resolutions were approved without objection. The 2 selected candidates are: Annaliese Williams and Chris Disspain *Council meeting #220 August 21st. 2025* Agenda and draft resolutions <https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/103123995/…> Statements and responses <https://ccnso.icann.org/en/about/statements.htm> *Some Highlights* *1. Administrative Updates* *Correspondence:* Letters discussed regarding Review of Reviews, CSC coordination, and deferral of the 3rd CSC Effectiveness Review. *Completed Action Items:* · The Secretariat published the adopted FY26–27 workplan, providing a roadmap for upcoming activities. · For the Board Seat 11 nomination process, the Secretariat published the resolution adjusting the voting procedure in the event of a single candidate. · The approval of IFRT recommendations was added to the Meeting #220 agenda, as requested. · Appointments to working groups and committees were formally communicated, enabling appointees to begin their roles immediately. · A note on proposed ICANN Bylaw and CSC Charter changes (introducing alternates and adjusting review timing) was circulated to gather Council feedback. · The Chair provided ongoing updates on the Review of Reviews charter and related matters. · The Secretariat ensured inclusion of the IANA IPR transfer decision on the Meeting #220 agenda. *Ongoing Action Items:* · The *Guidelines Review Committee (GRC) <https://ccnso.icann.org/en/workinggroups/grc.htm>* is considering whether to formalize Council voting periods by specifying clear opening and closing times for online votes. · The *Council Chair, Peter Koch, and Luis Diego Espinoza* (ccNSO appointees to the RSSAC GWG) are preparing the joint ccNSO–RSSAC session for ICANN84, which requires cross-community coordination. *2. Updates* - *Working Groups:* Many groups are dormant or awaiting for ICANN84 sessions. - *ccPDP4-IDN <https://ccnso.icann.org/en/workinggroups/idn-cctld-strings.htm>:* Still progressing slowly; caucus reconvening for validation processes. - *Review of Reviews:* Charter adopted; 2 members appointed (Annaliese Williams, Chris Disspain). Concerns raised about limited volunteers. - *360 Review:* Completed; feedback given, with suggestions to improve timing of evaluations. - *Board Seat 11 Nomination:* The only candidate is Patricio Poblete (current holder), moving forward with due diligence; no election required but a Q&A session will take place during ICANN84. - *Website Redesign:* Expected launch in December 2025. *3. Finance WG2 Final Report & Adoption* The *Finance Working Group 2 (Finance WG2) <https://ccnso.icann.org/en/workinggroups/sfwg.htm>* delivered its final report on August 15th., 2025, after 9 months of work, consultations during ICANN81–83, and a survey, and a July 2025 public comment period. *Main findings & proposals:* - Updated cost model sets *expected ccTLD contribution at USD 3.6 million* (previously USD 3.5M). - No major structural changes; voluntary principle reaffirmed. - New *banded model* introduces *three additional lower tiers* for smaller ccTLDs, maintaining a range of USD 500 to USD 225,000. - Addressing discrepancies between expected and actual contributions requires *segmented, personalized engagement* by ICANN, acknowledging the diversity of ccTLDs (size, governance, budget cycles). - Emphasis on transparency, outreach, and trust-building as motivators. *Council Decision:* The Council adopted the new 2025 Principles and Banded Model, requested the Chair to share the report with ICANN’s CEO, while recommending a more segmented outreach approach, instructed the Secretariat to replace the 2013 Guideline with the updated 2025 version, and confirmed that the Working Group would be formally closed seven days after the resolution’s publication. *4. Other Major Decisions* *Approval of IFRT2 Recommendations:* The Council approved two recommendations from the 2nd. IANA Function Review Team (IFRT2), both requiring changes to the IANA Naming Function Contract: 1. Remove policy details from the contract. 2. Identify and point to the appropriate policy authority for DNSSEC. These recommendations were published for public comment earlier in 2025 and received no objections. Approval was unanimous, ensuring alignment with ICANN Bylaws requirements for supermajority support. *Transfer of IANA Intellectual Property Rights:* The Council endorsed the transfer of stewardship of the IANA-related intellectual property (trademarks and domain names) from the *IETF Trust <https://trustee.ietf.org/>* to the newly created *IETF Intellectual Property Management Corporation (IPMC). <https://trustee.ietf.org/documents/minutes/>* The Council agreed to support the transfer of stewardship of the IANA intellectual property rights from the IETF Trust to the newly created IETF Intellectual Property Management Corporation (IPMC). This change was described as purely legal and technical, without altering any accountability mechanisms. The decision followed the advice of the ccNSO appointee to the Community Coordination Group (CCG), and it was confirmed that the transfer would become effective seven days after publication, with the ccNSO Secretariat tasked with notifying the appointee. *Root Server System Governance (RSS GWG):* A new *Council statement procedure* was initiated to provide ccNSO input on the draft governance structure for the Root Server System. A drafting team, supported by ccNSO-appointed members Peter Koch and Luis Diego Espinoza, will prepare the Council’s statement on the draft Root Server System Governance Structure. The statement is expected before next Council Meeting 221 in September 2025. *Rescheduling of Committee Reviews:* The Council approved an updated timeline for the review of all ccNSO committees, which had been delayed. The first review (MPC) will now begin in September 2025, with other committees shifted by six months. The Secretariat will update the ccNSO workplan and seek at least three volunteers who have not previously been involved in the committees under review. The revised timeline extends through 2030 and includes reviews of the IGLC, GRC, UAC, TLD-Ops, SOPC, Tech WG, OMC, and DASC. *Appointments to Working Groups and Committees:* The Council confirmed new appointments to several groups, adding Lucien Castex (.fr) and Fatma Demirel (.tr) to the IGLC, Sarah Gooch (.uk) to the SOPC, and Fatma Demirel (.tr) to the DASC. These appointments take effect immediately, and the Secretariat will coordinate their integration into the respective groups. *Customer Standing Committee (CSC) <https://www.icann.org/csc> related Matters:* *Membership Selection* The Customer Standing Committee (CSC) is composed of members appointed by both the RySG and the ccNSO, with voting rights, while liaisons do not hold voting power. The proposed slate of members includes: Pablo Rodriguez and Maarten Simon (ccNSO) as full members, Erwin Lansing (ccNSO) as alternate. Nick Wilhelm and Gordon Dick (Nominet, RySG) as RySG appointees. The next step is the approval of the full slate by both the ccNSO and GNSO Councils in September 2025. While the ccNSO has mandated a selection committee to oversee this process, the GNSO will address it through its consent agenda. Once approved, the new term will officially begin on 1 October 2025. *Bylaw and Charter Updates* The Second CSC Effectiveness Review produced three main recommendations: 1. Conduct a full SLA review; amended procedures will be published shortly, and the CSC, together with IANA, will review the 46 SLAs agreed upon during the transition. 2. Adjust the frequency of CSC effectiveness reviews to take place five years after the previous review, requiring changes to both ICANN Bylaws and the CSC Charter. 3. Introduce alternates formally, which also necessitates updates to the Bylaws and CSC Charter. Draft language is currently being developed by ICANN Legal and will be shared by the next Council meeting. Both the ccNSO and GNSO Councils will need to approve these updates once finalized. *5. ICANN84 - Dublin* The draft block schedule was presented and included a Disaster Recovery session, GRC workshop, and ccTLD News session. Thank you for reading. If you have any questions or topics you would like to have more information, please let me know and I will be happy to provide it. Have a nice week. Kindest 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…>

1 0

Launch of The Internet Ecosystem Book
by Nikesh B. Simmandree Aug. 18, 2025

Aug. 18, 2025

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

Summary Report for GNSO Council 14 August 2025 meeting
by Justine Chew Aug. 17, 2025

Aug. 17, 2025

Dear all, Please find below, the updated agenda for the GNSO Council 14 August 2025 meeting, followed by my Summary Report on Matters of Interest. You can also find these at this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/265846872/G…> under the relevant tabs. While the meeting agenda was lengthy, as usual, Council made decisions on 6 topics. I'd be happy to answer and questions on this thread or during the next ALAC Monthly Call on 26 August. *GNSO Council Meeting #8 of 2025 held on 14 August 2025 (updated 8 Aug 2025)* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/MKafBg>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/6KefBg>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/RKifBg> - *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 CSC Effectiveness Review* - Confirmation of GNSO Non-Registry Liaison and Alternate to the Customer Standing Committee (CSC) - Adoption of Team 14 outcomes document - Board Seat 14 appointment - *Confirmation of Support for the Board’s Proposed Non-Adoption of Select IGO Recommendations* - *Item 4: COUNCIL VOTE - Approval of IANA Review Function 2 (IFR2) Final Report* - *Item 5: COUNCIL VOTE - Approval of Recommendations from GNSO Council Small Team on Accuracy * - *Item 6: COUNCIL VOTE - Request for Issue Report on DNS Abuse* - *Item 7: COUNCIL VOTE - Approval of the Review of Reviews Cross Community Group Charter* - *Item 8: COUNCIL UPDATE - Privacy Proxy Services Accreditation Issues Implementation Work - Questions for GNSO Council* - *Item 9: COUNCIL UPDATE - Outcome of Transfer Policy Review PDP Human Rights Impact Assessment* - Item 10: Any Other Business - 10.1 - ICANN84 planning and GNSO Draft schedule - 10.2 - WSIS Update - 10.3 - GNSO Liaison to the GAC update - 10.4 - Question re: GNSO Liaison to the GAC * Summary to the ALAC on GNSO Council Meeting #8 of 2025 held on 14 August 2025* For brevity, I will just highlight outcomes on key issues here. For some of the issues, you can get more information under the Matters of Interest and/or Meeting Records tabs. Council resolved <https://icann-community.atlassian.net/wiki/x/RKifBg> quite a few issues at this meeting. 1. Deferred the *Third CSC Effectiveness Review* for one year; this decision will be revisited in August 2026. 2. Approved the 3 recommendations contained in the *Second IANA Naming Function Review Team (IFR2)* Final Report, covering: 1. Presence of specific Domain Name System Security Extensions (DNSSEC) policy details in the IANA Naming Function Contract 2. Transparency and availability of Contract amendments 3. Frequency of reviews 3. Does not object to the Board’s intention to reject 2 pending recommendations related to *International Governmental Organization (IGO) names protections *(i.e. Recommendations 3.3.5 and 3.3.7 from the 2013 Top & Second Level Protections for IGOs, Red Cross, Int’l Olympic Committee, and international NGOs (INGOs) PDP) on the basis that they have been superseded by subsequent policy development (i.e. the 2019: IGO & INGO Curative Rights PDP and the 2022 Expedited PDP on IGO Curative Rights). 4. Adopted the 4 recommendations on *Registration Data Accuracy (RDA) *as recommended by Council’s Accuracy Small Team. These recommendations were last discussed <https://icann-community.atlassian.net/wiki/download/attachments/351535105/2…> by Justine on CPWG 2 Jul 2025 call <https://icann-community.atlassian.net/wiki/x/AQD0F>. 5. Adopted the 3 recommendations on *DNS Abuse* as recommended by Council’s DNS Abuse Small Team. These recommendations were last discussed <https://icann-community.atlassian.net/wiki/download/attachments/389906434/2…> by Justine on 30 Jul 2025, with the key recommendations being (i) a Request for an Issue Report based upon the catalogue of issues the Small Team has developed (with input from SG/C/ACs); and (ii) elevating three prioritized gaps for a draft Charter development. At-Large input was provided per 1. *CPWG high-level update, 30 Jul 2025* <https://icann-community.atlassian.net/wiki/download/attachments/389906434/2…> (covers At-Large Position on DNS Abuse mitigation gaps) 2. *CPWG high-level update, 16 Jul 2025* <https://icann-community.atlassian.net/wiki/download/attachments/370246404/2…> (covers notes on DNS Abuse mitigation gaps; and At-Large priorities) 6. Approved the Charter for the *Review of Reviews* Cross Community Group (CCG) <https://gnso.icann.org/sites/default/files/policy/2025/correspondence/final…>, following the ICANN Board’s 19 May 2025 resolution <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> to continue the deferral of the ATRT4, and other Specific Reviews, pending community dialogue to inform next steps, and notwithstanding the timing mandated under the Bylaws for the commencement of ATRT4. The CCG will undertake the review of reviews per the Charter. 1. Council’s Standing Selection Committee will identify and select two (2) GNSO member participants of the CCG, at least one of whom should be a GNSO council member, for Council’s approval. 2. Recall that Council declined to support the ALAC’s Petition for an Empowered Community Reconsideration Request <https://www.icann.org/en/system/files/correspondence/alac-to-eca-19jun25-en…> and instead preferred the path of the CCG. Other than that: 7. Council discussion on *Privacy Proxy Services Accreditation Issues Implementation (PPSAI) *Work continues. 8. Council will draw learnings from a *Human Rights Impact Assessment (HRIA) *conducted on the recommendations in the Transfer Policy Review Working Group’s Final Report, such as the need for including a reference to HRIA in the GNSO Operating Procedures and as part of the GNSO Council Liaison to a PDP’s job description. 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…> ------

1 0

Re: SAC130: SSAC Comments on Name Collision Guidelines in the Proposed Language for the Draft Next Round Applicant Guidebook
by Justine Chew Aug. 6, 2025

Aug. 6, 2025

👍🏼 Justine Chew reacted via Gmail <https://www.google.com/gmail/about/?utm_source=gmail-in-product&utm_medium=…> On Wed, 6 Aug 2025 at 22:05, James Galvin <galvin(a)elistx.com> wrote: > Thank you Matthias. > > And now that we know from yesterday’s meeting that Topic 29 will be > discussed on 20 August at 18:30 UTC, I can confirm I will be there as > SSAC’s representative. > > I’m happy to answer any questions or have any discussion anyone may have > before then. > > Jim > > On 27 Jul 2025, at 6:04, Matthias M. Hudobnik wrote: > > Dear colleagues, see some infos between the lines. > > Best, > Matthias > > __________________________ > Ing. Mag. Matthias M. Hudobnik > FIP, CIPP/E, CIPT, DPO, CIS LA > matthias(a)hudobnik.at > http://www.hudobnik.at > @mhudobnik > > On 25.07.2025, at 01:39, Justine Chew <justine.chew.icann(a)gmail.com> > wrote: > > > Hi Avri, > > I understand SAC130 to be SSAC's public comment to the draft AGB public > comment proceeding that just closed. > > > Yes, see here: > https://www.icann.org/en/public-comment/proceeding/final-proceeding-for-pro… > . > > > NCAP Study 2 was an SSAC output. It doesn't go through the GNSO but the > recommendations (except one) was approved by the Board. These then went to > org for implementation. Hence the new Name Collision Management Framework > was established as it appears in the draft AGB, as discussed by the IRT. > > > Here the info: > https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… > . > > > What I understand from SAC130 is SSAC suggests the that implementation of > its NCAP Study 2 is either incomplete or hasn't gone far enough. I trust > this position will be discussed when the IRT reconvenes to review public > comments and we should once again have Jim Galvin for those IRT calls. > > > Yes, indeed. > > > > Kind regards, > Justine > --------- > > On Fri, 25 Jul 2025, 05:06 avri doria, <avri(a)doria.org> wrote: > >> Hi, >> >> Was this advice approved by anyone (i.e. GNSO & Board) and designated as >> part of the SubPro recommendations? Or does it have the nebulous status of >> most advice? Did the GNSO act on NCAP2 "recommendations?" >> >> As neither the Board nor the SSAC have policy making authority, I am >> curious. >> >> thanks >> >> avri >> On 7/24/2025 11:35, Justine Chew via ALAC wrote: >> >> Thanks for this, Matthias. I am hopeful that Jim Galvin will discuss >> these with the IRT when the IRT reconvenes to review input from the most >> recent public comment proceeding. >> >> Kind regards, >> Justine >> >> >> >> On Thu, 24 Jul 2025 at 21:28, Matthias M. Hudobnik via ALAC < >> alac(a)icann.org> wrote: >> >>> 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: >>> >>> 1. >>> >>> *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. >>> 2. >>> >>> *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. >>> 3. >>> >>> *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. >>> 4. >>> >>> *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 >>> _______________________________________________ >>> ALAC mailing list -- alac(a)icann.org >>> To unsubscribe send an email to alac-leave(a)icann.org >>> >>> At-Large Online: http://www.atlarge.icann.org >>> ALAC Working Wiki: >>> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… >>> _______________________________________________ >>> 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. >> >> >> _______________________________________________ >> ALAC mailing list -- alac(a)icann.org >> To unsubscribe send an email to alac-leave(a)icann.org >> >> At-Large Online: http://www.atlarge.icann.org >> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… >> _______________________________________________ >> 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