October 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

About Llatin Diacritics
by Sergio Salinas Porto Oct. 28, 2025

Oct. 28, 2025

Dear all, I wish to express my concern about the absence of a placeholder in the current draft of the ICANN Applicant Guidebook for the outcome of the Latin Script Diacritics Policy Development Process. This PDP addresses the ability for end-users to see their languages correctly represented in the Domain Name System (DNS), including the use of diacritics in Latin labels. This is not a theoretical issue: it affects how entire language communities write their names and identify themselves online. We are not requesting any extensions for the next round of applications or changes to the published timeline. This request is specific and procedural: that the Applicant Guidebook include a clear clause stating that if the Latin Script Diacritics PDP submits its recommendations within the expected timeframe, they will be incorporated into this round. We view this as a reasonable accommodation of ongoing community work that has a direct impact on linguistic and cultural accuracy for users. My two cents regards *Sergio Salinas Porto**Presidente Internauta Argentina - LACRALO/ICANN <https://atlarge.icann.org/ralos/lacralo>**Asociación Argentina de Usuarios de Internet <http://www.internauta.org.ar/>/FeTIA <http://www.fetia.org.ar/>**FUILAC- Federación de Usuarios de Internet de LAC <https://fuilac.org>**facebook: salinasporto <http://www.facebook.com/salinasporto> **twitter: sergiosalinas <http://twitter.com/sergiosalinas>**Mobi:+54 9 223 5 215819**"Ojalá podamos ser desobedientes, cada vez que recibimos órdenes que humillan nuestra * * conciencia o violan nuestro sentido común" Eduardo Galeano*

5 7

Re: [ALAC-Announce] Renewal of Liaisons
by Abdulkarim Oloyede Oct. 26, 2025

Oct. 26, 2025

*Hi,* 2021 to 2026 — that’s 5 years!!! That is a long time in a community like ICANN. I think we need to give opportunities to others. I think it’s okay to renew those appointed in 2023 but not those appointed in 2021. It’s totally unfair, and At-Large seems like a circle... Anyway, it is a reflection of most of the RALOs. By the way. Since I know ALAC, it has always been a rubber stamp to WHATEVER the chair does. So I'm not surprised. The circle favours some people, and they always manage to use them to have their way, using various 'nice' tactics. I recall trying to change this narrative when I was on ALAC, with the support of a few other ALAC members; we almost achieved it once or twice, but never secured the majority. Why do I care? I have refrained from commenting on the mailing list, but this is too much for me to ignore. AK *Prof. Abdulkarim Ayopo Oloyede*. *Full Professor of Wireless Telecommunications* *Department of Telecommunications Science, University of Ilorin, Nigeria* *Director, Centre for Research Development and In-House Training (CREDIT) University of Ilorin * On Sat, Oct 25, 2025 at 8:52 AM Jonathan Zuck via ALAC-Announce < alac-announce(a)icann.org> wrote: > Dear All, > > > > On 14 October, I sent a note to the ALAC recommending that the ALAC > re-appoint current ALAC Liaisons to the ccNSO, GAC, GNSO, and SSAC for > another year. > > > > This recommendation was made using Article 18.2 of the *ALAC Rules of > Procedure [icann-community.atlassian.net] > <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/downl…>* (ROP) > allows the ALAC to reappoint ALAC Liaisons without a new call for > volunteers if we believe that the incumbent is doing a good job and that > the ALAC is well served by their continuing in that role. Experience has > shown that it is extremely important that the Liaison develop/maintain a > good working relationship with the target Supporting > Organization/Advisory Committee. > > > > The ALAC Liaisons are noted below along with their first appointment > dates: > > > > - GAC: *Joanna Kulesza* (October 2021) > > > *Joanna,* as the ALAC Liaison to the GAC brings with her significant > familiarity with the protocols of the GAC. She has developed excellent > working relations with the GAC Chair and the GAC Liaison to the ALAC and > continues to actively facilitate intersessional cooperation between the > ALAC and the GAC. She will continue to serve the ALAC well in her role as > the ALAC Liaison to the GAC. > > > > - GNSO: *Justine Chew* (October 2021) > > *Justine*, in her role as the ALAC Liaison to the GNSO, has been > extremely productive in ensuring that the interests of the of ALAC are > understood in the GNSO. Justine has gained and shared her significant > expertise in the GNSO policies and processes by explaining issues and > discussing them with the members of the CPWG and ALAC. She will continue to > serve the ALAC well in her role as the ALAC Liaison to the GNSO. > > > - ccNSO: *Laura Margolis *(October 2023) > > *Laura, *in her role as the ALAC Liaison to the ccNSO, utilizes her > experience as a ccNSO Council Member in her work as the ALAC Liaison. She > has explained and reported on ccNSO policy activities in a clear and > comprehensive manner since being appointed in 2023,identifying areas that > might benefit from an end-user perspective to the ALAC. Laura will continue > to serve the ALAC well in her role as ALAC Liaison to the ccNSO. > > > > - SSAC: *Matthias Hudobnik * (October 2023) > > *Matthias, *in his role as ALAC Liaison to the SSAC, has grown into his > role very successfully through his work with the SSAC. He has taken to > distilling new SSAC publications for easier comprehension by non-technical > readers and providing regular updates, even explanations,on SSAC > activities. Matthias will continue to serve the ALAC well in his role as > ALAC Liaison to the SSAC. > > > All the liaisons have agreed to continue for one more year. > > > > I received support from the ALAC for my recommended re-appointments. > > > > Accordingly, the current ALAC Liaisons to the GAC, GNSO, ccNSO, and SSAC > have been re-appointed for the period of one year starting at the close of > ICANN84 on 30 October 2025 and ending at the close of ICANN87 on 22 October > 2026. > > > > Please note that until such time as an ALAC Appointee Metrics framework is > adopted by the ALAC, the ALAC Appointed-Liaisons will be requested by the > ALAC Leadership to participate in selected ALAC/At-Large activities. He/She > may also be requested to provide periodic reports on his/her liaison work. > Such reports may be verbal or in written form, and notice will be given to > the ALAC Appointee on the timing of such reports. > > > > Thank you! > > > > Jonathan > > ALAC Chair > > > > > _______________________________________________ > ALAC-Announce mailing list -- alac-announce(a)icann.org > To unsubscribe send an email to alac-announce-leave(a)icann.org > > At-Large Official Site: http://www.atlarge.icann.org > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on. -- Website <http://www.unilorin.edu.ng>, Weekly Bulletin <http://www.unilorin.edu.ng/index.php/bulletin> UGPortal <http://uilugportal.unilorin.edu.ng/> PGPortal <https://uilpgportal.unilorin.edu.ng/> HelpDesk <http://www.unilorin.edu.ng/index.php/more-resources/e-notices/6845-how-to-r…>

7 9

[ALAC-Announce] Renewal of Liaisons
by Maureen Hilyard Oct. 25, 2025

Oct. 25, 2025

Hi Jonathan I totally support the current Liaison holders to retain their positions. They are all very active in their liaison roles as well as within At-Large. This is important to maintain a consistent and relevant interactive knowledge-based relationship. I believe that these relationships have also been strengthened due to the committed and mutually respected connections these individuals have made between At-Large and our other key organisations within ICANN. Im sure that if they are willing to do another year, we need to thank them and let them get on with it. Maureen On Sat, 25 Oct 2025, 8:52 am Jonathan Zuck via ALAC-Announce, < alac-announce(a)icann.org> wrote: > Dear All, > > > > On 14 October, I sent a note to the ALAC recommending that the ALAC > re-appoint current ALAC Liaisons to the ccNSO, GAC, GNSO, and SSAC for > another year. > > > > This recommendation was made using Article 18.2 of the *ALAC Rules of > Procedure [icann-community.atlassian.net] > <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/downl…>* (ROP) > allows the ALAC to reappoint ALAC Liaisons without a new call for > volunteers if we believe that the incumbent is doing a good job and that > the ALAC is well served by their continuing in that role. Experience has > shown that it is extremely important that the Liaison develop/maintain a > good working relationship with the target Supporting > Organization/Advisory Committee. > > > > The ALAC Liaisons are noted below along with their first appointment > dates: > > > > - GAC: *Joanna Kulesza* (October 2021) > > > *Joanna,* as the ALAC Liaison to the GAC brings with her significant > familiarity with the protocols of the GAC. She has developed excellent > working relations with the GAC Chair and the GAC Liaison to the ALAC and > continues to actively facilitate intersessional cooperation between the > ALAC and the GAC. She will continue to serve the ALAC well in her role as > the ALAC Liaison to the GAC. > > > > - GNSO: *Justine Chew* (October 2021) > > *Justine*, in her role as the ALAC Liaison to the GNSO, has been > extremely productive in ensuring that the interests of the of ALAC are > understood in the GNSO. Justine has gained and shared her significant > expertise in the GNSO policies and processes by explaining issues and > discussing them with the members of the CPWG and ALAC. She will continue to > serve the ALAC well in her role as the ALAC Liaison to the GNSO. > > > - ccNSO: *Laura Margolis *(October 2023) > > *Laura, *in her role as the ALAC Liaison to the ccNSO, utilizes her > experience as a ccNSO Council Member in her work as the ALAC Liaison. She > has explained and reported on ccNSO policy activities in a clear and > comprehensive manner since being appointed in 2023,identifying areas that > might benefit from an end-user perspective to the ALAC. Laura will continue > to serve the ALAC well in her role as ALAC Liaison to the ccNSO. > > > > - SSAC: *Matthias Hudobnik * (October 2023) > > *Matthias, *in his role as ALAC Liaison to the SSAC, has grown into his > role very successfully through his work with the SSAC. He has taken to > distilling new SSAC publications for easier comprehension by non-technical > readers and providing regular updates, even explanations,on SSAC > activities. Matthias will continue to serve the ALAC well in his role as > ALAC Liaison to the SSAC. > > > All the liaisons have agreed to continue for one more year. > > > > I received support from the ALAC for my recommended re-appointments. > > > > Accordingly, the current ALAC Liaisons to the GAC, GNSO, ccNSO, and SSAC > have been re-appointed for the period of one year starting at the close of > ICANN84 on 30 October 2025 and ending at the close of ICANN87 on 22 October > 2026. > > > > Please note that until such time as an ALAC Appointee Metrics framework is > adopted by the ALAC, the ALAC Appointed-Liaisons will be requested by the > ALAC Leadership to participate in selected ALAC/At-Large activities. He/She > may also be requested to provide periodic reports on his/her liaison work. > Such reports may be verbal or in written form, and notice will be given to > the ALAC Appointee on the timing of such reports. > > > > Thank you! > > > > Jonathan > > ALAC Chair > > > > > _______________________________________________ > ALAC-Announce mailing list -- alac-announce(a)icann.org > To unsubscribe send an email to alac-announce-leave(a)icann.org > > At-Large Official Site: http://www.atlarge.icann.org > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on.

2 1

GNSO Council 29 October 2025 meeting agenda @ ICANN84 is out
by Justine Chew Oct. 18, 2025

Oct. 18, 2025

Dear all, Please be informed that the agenda for the GNSO Council Meeting taking place during ICANN84, is as follows: *GNSO Council Meeting held on 29 October 2025 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/265846872/G…> * *Full Agenda (Part 1)* <https://icann-community.atlassian.net/wiki/x/QKafBg>* | **Agenda (Part 2* <https://icann-community.atlassian.net/wiki/x/T4AuGQ>*) | **Documents* <https://icann-community.atlassian.net/wiki/x/LJqfBg>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/VKifBg> - *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: COUNCIL VOTE: New gTLD Subsequent Procedures PDP - Interpretation of Intent for Select IGO/INGO PDP Recommendations* - *Item 4: COUNCIL DISCUSSION - Celebrating GNSO Accomplishments between ICANN Meetings* - *Item 5: COUNCIL DISCUSSION - Council PPSAI Small Team Responses to Threshold Questions* - *Item 6: COUNCIL DISCUSSION - Prioritization of Upcoming Work* - *Item 7: Open Mic* - *Item 8: Any Other Business* - *8.1 - Update to Council on Latin Diacritics PDP Timeline * - *8.2 - Proposed Updates to ICANN Bylaws and Customer Standing Committee (CSC) Charter* - 8.3 - Farewell to Outgoing Councilors For more details on the marked agenda items (except for AOB items), please visit *this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/265846872/G…>* and click on 'Matters of Interest' This Council meeting will take place on *29 October 2025 at 13:15 UTC for 2 hours* and, except for item 7 Open Mic, is open to observers both in-person and remotely in observation / listen-only mode. Please check the ICANN84 Schedule <https://icann84.sched.com/event/29QND> for venue details and Zoom link (only published 24 hours prior to the meeting) Thanks for reading / considering. *Justine Chew* ALAC Liaison to the GNSO GNSO Liaison Workspace <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Y…> ------

1 0

ICANN84 Participation and Travel Details
by Alan Greenberg Oct. 16, 2025

Oct. 16, 2025

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/ICANN84-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

5 7

SSAC has published SAC132: The Domain Name System Runs on Free and Open Source Software (FOSS)
by Matthias M. Hudobnik Oct. 14, 2025

Oct. 14, 2025

Hi colleagues, the SSAC has published SAC132. ### SSAC has published SAC132: The Domain Name System Runs on Free and Open Source Software (FOSS): Overview • The Domain Name System (DNS) is critical infrastructure, mapping names to IP addresses for nearly all online activity. • Research confirms the DNS overwhelmingly relies on FOSS. o 9 of 12 root server operators use FOSS exclusively. o 9 of the 10 largest TLD providers use FOSS. • FOSS dominance comes from its economic efficiency, transparency, collaborative security, and resilience. • FOSS is not inherently more or less secure than proprietary software; outcomes depend on processes and maintenance. • However, the FOSS development model differs fundamentally from proprietary supply chains, raising unique risks. 1. Introduction • Policymakers are increasingly intervening in software security (UK voluntary code, US attestation, EU Cyber Resilience Act and NIS2, China’s IT plan). • Risk: regulations designed for proprietary models may harm critical Internet infrastructure if applied to FOSS without adaptation. • Aim: provide context to policymakers to recognize FOSS’s role and avoid destabilizing interventions. 2. DNS Primer • DNS = “address book of the Internet.” • Functions: o Registration: registries manage the authoritative database of domain names. o Publication: authoritative servers publish DNS records. o Resolution: resolvers fetch IP addresses for users. • Structure: Root → TLDs → individual domains. • Resolvers answer ~90% of queries from cache; authoritative servers publish definitive records. 3. The FOSS Model: Characteristics and Implications • Key roles: o Maintainers: guide project direction. o Contributors: submit code/docs/bug fixes. o Operators: deploy and run software. • Four freedoms: use, study, share, change. • Unique characteristics: o Global collaborative development. o No contractual relationships. o Funding decoupled from use. o Often no single responsible legal entity. • Proprietary systems also depend on FOSS components. • Strengths: o Transparency & collaborative security . o Stability & long-term support by non-profits/companies. o Resilience via software diversity. o Enabler of innovation and digital autonomy. • Risks : o Financial sustainability & maintainer burnout. o Shared dependency risks. o No warranties or support guarantees. o Operational risks in deployment. 4. Prevalence of FOSS in DNS • Registration: Platforms like FRED, Nomulus, CoCCA widely used. Large registries use proprietary extensions but built atop FOSS. • Publication: Root and TLD servers overwhelmingly use FOSS. 9 of 12 root operators rely on FOSS. • Resolution: BIND, Unbound, Knot Resolver, CoreDNS common. ISPs, enterprises, and cloud resolvers widely deploy FOSS. 5. Contemporary Cases in FOSS Regulation • Policymakers are adapting rules to reflect FOSS realities. • Examples: o US 2023 Cybersecurity Strategy: exempts volunteer maintainers; responsibility on deployers. o UK 2025 Code of Practice: voluntary guidance. o EU CRA/NIS2: introduces “FOSS steward” role, avoids treating maintainers as suppliers, harmonizes obligations. • Policy lessons: 1. Allocate responsibility to those best able to act. 2. Incentivize cross-industry collaboration on maintenance. 3. Avoid supply chain assumptions based on proprietary models. 4. Avoid conflicting regional obligations. 6. Key Findings 1. FOSS is the foundation of DNS; proprietary is the exception. 2. FOSS model is fundamentally different from proprietary software supply chains. 3. FOSS is not inherently more/less secure; security depends on processes. 4. DNS FOSS strengths: transparency, collaborative security, diversity, long-term stability. 5. Risks: sustainability, burnout, shared dependencies — not solvable by proprietary regulations. 6. Traditional liability is ill-suited: imposing burdens risks discouraging maintainers and harming infrastructure. 7. FOSS enables autonomy and innovation: lowers entry barriers, supports local industry, diversifies markets, reduces cloud dependence. 7. Actionable Guidelines for Policymakers 1. Acknowledge the Critical Role of FOSS o Explicitly recognize in law/regulation that critical infrastructure depends on FOSS; treat it as a strength to preserve. 2. Consult the FOSS Community o Engage maintainers, contributors, non-profits, and companies in policymaking. 3. Make Use of Contemporary Cases o Apply lessons: responsibility on deployers not maintainers, support FOSS steward models, avoid proprietary assumptions, prevent conflicting regional regimes. 4. Incentivize FOSS Sustainability o Promote public/private funding of critical FOSS projects as investments in shared goods. 5. Address Systemic Risks Collectively o Fund ecosystem-wide resilience (dependency tooling, research, security initiatives) instead of overburdening individuals. Conclusion The SSAC concludes: • The DNS runs on FOSS, a global public good central to Internet stability. • Policymakers must avoid treating FOSS with proprietary assumptions. • Following the five guidelines — acknowledge, consult, learn, incentivize, collaborate — ensures security and sustainability of DNS and the Internet as a whole. Link to the report: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe…. Have a nice day! Best, Matthias ______________________________ Ing. Mag. Matthias M. Hudobnik FIP • CIPP/E • CIPT • DPO • CIS LA matthias(a)hudobnik.at http://www.hudobnik.at @mhudobnik

3 3

APRALO Bytes - Regional Internet Registry Governance, 14 Oct 2025
by Justine Chew Oct. 14, 2025

Oct. 14, 2025

Hello everyone, Here is the latest *APRALO Byte*, which is on the topic of *Regional Internet Registry governance*, published at https://icann-community.atlassian.net/wiki/spaces/APRALO/pages/412844037/AP… (click on 'Read more'). In brief, we draw attention to the ongoing *review of the Internet Coordination Policy - 2 (ICP-2) Document *by the Address Supporting Organization (ASO) and the ALAC's position on the second version of the draft “Governance Document for the Recognition, Operation, and Derecognition of Regional Internet Registries” to update the ICP-2. More details are in the Byte. 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

2025-2026 ALAC Leadership Team
by Heidi Ullrich Oct. 13, 2025

Oct. 13, 2025

Dear All, Following up on the Call for Nominations for the ALAC Leadership Team (ALT) positions, as of the deadline of 9 October 2025 the nominations received were: * Africa – Adebunmi Akinbo<https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99694573/Ad…> * Asia, Australia and Pacific Islands – Justine Chew<https://community.icann.org/display/atlarge/Justine+Chew+SOI> * Europe - Natálie Terčová<https://community.icann.org/display/atlarge/Natalie+Tercova+SOI> * Latin America and Caribbean Islands – Claire Craig<https://community.icann.org/display/atlarge/Claire+Craig+SOI> As noted previously, Jonathan Zuck, ALAC Chair, automatically assumes the position of ALT Member from North America. All nominees accepted their nomination by 3 October 2025. Therefore, in accordance with ALAC Rules of Procedure Rule 16.3<https://community.icann.org/display/atlarge/Rules+of+Procedure?preview=/226…>, the nominees noted above have been appointed to the ALT by acclamation. The one-year terms of the ALT will begin at the end of the 2025 AGM taking place at ICANN84 and end at the 2026 AGM taking place at ICANN87. Jonathan Zuck has asked Justine Chew and Claire Craig to continue in their roles as ALAC co-Vice Chairs. Please see the 2025 ALAC and RALO Elections, Selections, and Appointments Workspace<https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/162332709/2…> additional information. Kind regards, At-Large Staff At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/>

1 0