December 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

GAC Liaison Report for December 2025
by Joanna Kulesza Jan. 20, 2026

Jan. 20, 2026

Dear Colleagues, I respectfully submit my *GAC Liaison Report for the December 2025 ALAC Monthly Call*, circulated ahead of today’s meeting. With thanks for adjusting the meeting schedule to better accommodate Central European volunteers noted in my previous message, I would like to draw your attention in particular to the *action points highlighted in the report*, which require ALAC input. *Key action items for ALAC consideration include:* 1. *January 8 ALAC–GAC Regulatory Developments Briefing Session (WSIS+20)* Input and feedback are invited on the proposed agenda and structure for the 8 January 2026 session focusing on the outcomes of the WSIS+20 UN General Assembly High-Level Meeting. In particular, expressions of interest are sought from ALAC members willing to take the floor for a *10-minute intervention* on At-Large perspectives regarding WSIS+20 takeaways, priorities, and expectations. 2. *ICANN 85 ALAC–GAC Bilateral Agenda* Feedback is requested on the proposed scope of the ALAC–GAC bilateral meeting at ICANN 85. Specifically, do we wish to *revisit DNS abuse and WSIS+20* in the bilateral format, given recent and forthcoming exchanges on these topics, or should *alternative or additional issues* be prioritised to maximise the added value of the session? The full report is available on the *GAC Liaison webpage <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99710696/GA…>* and *below for ease of reference*. I look forward to your guidance and to discussing these points during today’s call. -- Kind regards, Joanna Kulesza ------------------- Joanna Kulesza, PhD Professor of International Law Lodz Cyber Hub / University of Lodz Law School / Poland www.cyber.uni.lodz.pl (EURALO ALS 341) ALAC / EURALO / ALAC Liaison to the GAC --- *GAC Liaison Report: ALAC Monthly Call* *By:* Joanna Kulesza, EURALO, ALAC Liaison to the GAC *Reporting Period:* December 2025 *Submitted:* 16 December 2025 ------------------------------ *1. WSIS+20 UN General Assembly High-Level Meeting Outcomes – January ALAC–GAC Briefing* In preparation for the *ALAC–GAC Regulatory Developments Briefing Session scheduled for 8 January 2026 (60 minutes)*, this section outlines the objectives, speakers, and timing of a dedicated session focusing on the outcomes of the *WSIS+20 UN General Assembly High-Level Meeting (16–17 December 2025)*. *Session Overview* *Title:* WSIS+20 UN General Assembly High-Level Meeting Outcomes *Date*: 8 January 2026, 16:00 UTC for 60 minutes The session will facilitate a structured exchange between ALAC, the GAC, and ICANN Org on the implications of WSIS+20 for Internet governance, with particular emphasis on end-user interests, the multistakeholder model, and ICANN’s technical coordination role. *Proposed Agenda and Speakers* 1. *Opening and Context Setting (5 minutes)* *Joanna Kulesza, ALAC Liaison to the GAC* Overview of session objectives, the WSIS+20 mandate, and the UN General Assembly High-Level Meeting process. 2. *WSIS+20 Outcomes – GAC Perspective (10 minutes)* *Zeina Bouharb, GAC (tbc)* Governmental perspective on WSIS+20 outcomes, including implications for multistakeholder governance, public policy priorities, and ICANN’s role within the broader UN digital cooperation landscape. 3. *Governmental Engagement and UN Processes (20–25 minutes)* *Alexey Trepykhalin, GAC Governmental Engagement Team* Assessment of WSIS+20 outcomes in the context of ongoing UN digital governance initiatives, including linkages with the Global Digital Compact and anticipated next steps at the intergovernmental level. 4. *Q&A and Interactive Discussion (10–15 minutes)* Moderated exchange between ALAC and GAC participants on areas of convergence, open issues, and opportunities for coordinated follow-up. 5. *Summary and Wrap-Up (5 minutes)* Key takeaways, identification of *next steps, and proposed coordination between ALAC and the GAC.* *References (Advance Reading)* 1. UN DESA, *WSIS+20 Process and Timeline* https://dig.watch/processes/wsis20-process 2. UN General Assembly, *WSIS+20 High-Level Meeting Overview* https://publicadministration.desa.un.org/wsis20/GA%20High-Level-Meeting 3. UN DESA, *WSIS+20 Zero Draft Outcome Document* https://publicadministration.desa.un.org/sites/default/files/2021-04/2025/W… 4. ICANN, *ICANN’s Commitment to WSIS+20: Progress and Opportunities* (5 February 2025) https://www.icann.org/en/blogs/details/icanns-commitment-to-wsis20-progress… 5. ICANN, *WSIS+20 Outreach Network* https://www.icann.org/en/government-engagement/wsis20-outreach-network ------------------------------ *2. GAC Correspondence: Protections for Names and Acronyms of Intergovernmental Organizations (IGOs) in gTLDs* On *12 December 2025*, the GAC submitted formal correspondence to the ICANN Board and ICANN Org concerning updated criteria and processes for the protection of *IGO names and acronyms at the second level in new gTLDs* (see: https://gac.icann.org/contentMigrated/protections-for-names-and-acronyms-of… ). *Key elements include:* · Updated criteria and procedures for adding and removing IGOs from the protection list, including qualification standards and list maintenance mechanisms. · A proposed moratorium on protections for IGO acronyms pending final implementation of relevant PDP Working Group recommendations. · Ongoing consideration of whether reserved IGO identifiers should be included in String Similarity Evaluations in the Next Round of new gTLDs. The correspondence recalls principles articulated in the Dublin Communiqué and requests guidance from the ICANN Board on engagement modalities where applications may conflict with reserved IGO identifiers. ------------------------------ *3. GNSO Council Review of the Dublin GAC Communiqué – Issues of Relevance to End Users* On *15 December 2025*, the GNSO Council transmitted its review of the Dublin GAC Communiqué, outlining intersections with current and planned gTLD policy work ( https://gac.icann.org/advice/correspondence/incoming/20251215/gnso-council-…) *Key issues of relevance to end users include:* *a. DNS Abuse* The GNSO confirms DNS abuse as a priority area, referencing follow-up work to the Preliminary Issue Report, including associated-domain checks, unrestricted API access, and coordination on DGA-based abuse. Effective mitigation is directly linked to end-user trust and security in the DNS. *b. Accuracy of Registration Data* The review addresses concerns regarding the timeliness and effectiveness of registration data validation and verification, noting ongoing work by the Accuracy Small Team and its relevance to accountability and consumer protection. *c. Urgent Requests for Disclosure of Registration Data* The GNSO acknowledges continued coordination on urgent disclosure mechanisms for cases involving serious threats, while noting that further positions are pending the outcome of relevant public comment processes. The GNSO positions its review *as an invitation for continued engagement with the GAC to align public policy concerns, technical feasibility, and end-user interests*. ------------------------------ *4. Scheduling and Draft Agenda for the ALAC–GAC Bilateral Meeting at ICANN 85 * This item outlines the proposed scheduling and draft agenda for the *ALAC–GAC bilateral meeting at ICANN 85*, to be held early in the meeting week to inform subsequent discussions. *Draft Agenda (60 minutes)* 1. *Opening and Introductions* o ALAC Chair (5 minutes) o GAC Chair (5 minutes) 2. *DNS Abuse (tbc)* o ALAC perspective (10 minutes) o GAC perspective (10 minutes) 3. *WSIS+20: Looking Ahead **(tbc)* o ALAC perspective (10 minutes) o GAC perspective (10 minutes) 4. *Discussion and Conclusions* o Q&A and identification of common positions and next steps (5 minutes) o Agreement on follow-up actions (5 minutes) The bilateral could once again focus on DNS abuse and WSIS+20, with the objective of informing strengthening coordination between ALAC and the GAC. *Feedback is explicitly sought from ALAC members* on the proposed scope and agenda, in particular: · whether DNS abuse and WSIS+20 should be discussed again in the bilateral format, given recent and upcoming ALAC–GAC exchanges on these topics; and · whether alternative or additional issues should be prioritised to maximise the added value of the ICANN 85 bilateral. This feedback will inform finalisation of the agenda and speaker balance.

2 2

GNSO DNS Abuse PDP 1 Draft Charter as at 19 Dec 2025
by Justine Chew Jan. 6, 2026

Jan. 6, 2026

Dear ALAC colleagues, I thought I might provide an extracted update on the (impending) output of the GNSO Council GNSO DNS Abuse PDP 1 Charter Review Team. As at 19 Dec 2025, the draft charter is proposed to be as per in https://docs.google.com/document/d/1LianKX5OTgIdecUgPaCTDDqU3o-IvaAoNTFl8M4… where I have extracted the key parts and highlighted the changes in yellow for easier consumption. In short, 1. The charter questions have been made more high level, less prescriptive to allow the PDP WG some flexibility while still have enough guardrails to keep it tightly focused. 2. The PDP WG model has been revised to "Representative" (instead of "Representative+Open") to keep the WG numbers 'manageable' while still allowing a *handful* more people to participate: - The ALAC now is designated 2 Members, 1 Participant and 1 Alternate (+ infinite number of Observers) - Only Members will be involved in a consensus call; otherwise the Participants can engage as freely as Members - An Alternate can only participate if a Member is not on the call; an Alternate cannot stand in for an absent Participant - Consensus call will be based on participating groups and not number of Members in each participating group - thus, even though RrSG is designated 4 Members because of the argument that 4 would be needed to enable different registrar business models to be heard, RrSG will be considered as ONE group during consensus call. *Conclusion* It is my considered opinion that we can live with what's being proposed and to not add to any more delay in spinning up the PDP WG. We should just focus our energies on participating in the PDP, to help shape the outcomes we may want. Needless to say, we need to identify suitable persons to fill the 4 seats designated to ALAC while encouraging more to become Observers when the GNSO makes the call for volunteers in Jan 2026. Kind regards, *Justine Chew* ALAC Liaison to the GNSO GNSO Liaison Workspace <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Y…> ------

2 2

ccNSO Council Meeting #224 Report
by Laura Margolis Dec. 23, 2025

Dec. 23, 2025

Dear ALAC colleagues, Please find below a summary of the ccNSO Council meeting #224, held on Thursday, 18 December 2025 at 18:00 UTC. Agenda and Background Materials <https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/103124011/…> Working Groups written updates December 2025 <https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/10841066…> In order to make it easier for you to read, I would like to highlight the main topics informed and discussed during the meeting. *Main Topics:* 1. Launch of the new ccNSO Website 2. ccNSO participation on GNSO DNS Abuse PDP 3. ccNSO email list archive 4. Tech Day interpretation removal 5. Council Elections *1. **Launch of the New ccNSO Website* The Council formally marked the launch of the new ccNSO website earlier this week. Members of the Website Steering Committee and the ICANN staff team presented key features, including improved content taxonomy, enhanced navigation, a new subscription function based on topic selection, and a timeline view of ccNSO activities. The Council expressed strong appreciation to the ICANN team and the Steering Committee for their collaboration and sustained effort throughout the project. *2. **ccNSO participation on GNSO DNS Abuse PDP* The Council held an initial discussion on whether and how the ccNSO should participate in the upcoming GNSO DNS Abuse PDPs, following the GNSO Council’s adoption of the Issue Report and the expected launch of two PDPs once the working group charters are finalized. Councilors noted potential benefits of participation, including the opportunity to share ccTLD operational experience, highlight the comparatively low levels of abuse within the ccTLD space, and contribute constructively to the multistakeholder process with the aim of reducing DNS abuse overall. At the same time, several concerns were raised. These included the significant resource commitments typically required by GNSO PDPs, as well as the risk of misunderstandings regarding the ccNSO’s role, particularly in relation to policy authority and the distinction between ccTLD and gTLD spaces. Some Councillors also emphasized the importance of ensuring that participation would not create expectations that PDP outcomes would be applicable to ccTLDs. The Council agreed to approach the discussion in two phases: first, determining whether the ccNSO should participate in principle, and second, if participation is supported, considering what form such participation should take. No decision was taken at this stage, and the Council agreed to revisit the matter in January 2026, once further clarity is available. *3. **Mailing list archive* The Council discussed the current status of the ccNSO Council mailing list archive, which is presently accessible only to subscribed members. For transparency and accountability reasons, the Council considered whether the archive should remain closed or be made publicly accessible, noting that other SO/ACs maintain public archives for similar bodies. Concerns were raised regarding the handling of confidential or sensitive materials; however, it was noted that closed meetings and confidential communications could continue to be managed through alternative channels. Following discussion, the Council agreed to open the Council mailing list archive going forward and also supported allowing observers to the mailing list. Implementation details will be communicated once finalized. *4. **ICANN84 Tech Day Report and possible Interpretation Removal* The Council discussed feedback from ICANN84 Tech Day, particularly regarding session pacing and the continued provision of interpretation. Broad support was expressed for maintaining interpretation to ensure inclusiveness and accessibility, especially for non-native English speakers. The topic will be revisited in January. *5. **Council Elections 2026* The Council addressed the special selection process for the African region seat, noting that Ingabire Grace Mwikarago (.rw) accepted her nomination. The Council agreed that a candidate Q&A was not required in this case. The Council also adopted the Council Election Process Report for the AP, EU, LAC, and NA regions, confirming the election of: - Sami Mohamed Ali (AP), - Chris Disspain (EU), - Alejandra Reynoso (LAC), - Charles Noir (NA). The Council requested the Guidelines Review Committee to review the Council Selection Process Guideline based on recommendations from the Election Process Manager. This is all for now. I would be happy to answer any questions or provide additional information if needed. Thank you for reading and *Happy Holidays* *for everyone!* Kindest 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

Fwd: The latest ccNSO news for you | December 2025
by Laura Margolis Dec. 19, 2025

Dec. 19, 2025

Dear All: Please have a look at the last ccNSO Newsletter. December 2025 [image: Screenshot 2021-08-02 at 12.51.32.png] [image: ccNSO_Lockup_W_B_bg_RGB.jpg] ccNSO News December 2025 | Issue 61 The new ccNSO website is now live! With a clearer layout and improved navigation, it’s built to make engaging with the ccNSO easier and more enjoyable. Sincere thanks go to all whose hard work, dedication, and collaboration made this launch possible! Read more <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> Check out the new ccNSO website, and let the ccNSO Secretariat <ccnsosecretariat(a)icann.org> know your thoughts. We would love to hear from you! Keep informed about the work of the ccNSO In preparation of each ccNSO Council meeting, a written update regarding the work by the various working groups and committees is drafted. It includes information about the current status, next steps and what the activities are about. The December edition is out now. Read more <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> [image: Screenshot 2021-09-27 at 15.21.09.png] Seamless Participation in ccNSO Activities Do you already have an ICANN Account? To streamline the management of ccNSO membership and ensure compliance with applicable laws, the ccNSO is using ICANN's Community Engagement System (CES) to manage stakeholder participation. This unified platform enhances collaboration and improves efficiency in how we engage with the ccTLD community. To facilitate the transfer and to ensure that data is processed in compliance with applicable laws, we ask you to create and maintain a personal ICANN Account if you do not already have one. Read more <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> Share Your Local and Regional Perspectives Internet Governance: hot topics? The ccNSO Internet Governance Liaison Committee (IGLC) invites all with an interest to share emerging Internet governance issues and trends in your region since ICANN81. Insights on policy, regulatory, or legislative developments affecting ccTLDs or the wider Internet ecosystem are welcome. How to contribute Complete the survey by 12 January <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> Next steps The IGLC will review all input during its mid-January meeting to help map regional priorities and guide its work. About the IGLC The ccNSO Internet Governance Liaison Committee (IGLC) supports ccTLDs in navigating Internet governance issues. In June 2024, it released “Towards WSIS+20: The GDC, SDGs, and Why They Matter to ccTLDs <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> ”, examining the implications of WSIS+20 and the Global Digital Compact. The committee also created the Internet Governance Heat Map <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> to track regional priorities and emerging topics, and participates in ICANN meetings and other events to address issues such as geographical indications, the digital divide, how ccTLDs contribute to sustainable development goals, and more. Planning for ICANN85 The ICANN85 Community Forum <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> will be held 7-12 March 2026 in Mumbai, India. Bookmark now Read more about the ccNSO at ICANN85 <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> Share your ccTLD news at ICANN85 This session provides a platform for sharing updates, insights, and discussions on ccTLDs. Both in-person and virtual participation will be available, with simultaneous interpretation in English, French, and Spanish. Presentation Topics Including, but not limited to: - Case studies on ccTLD initiatives - Collaboration & partnerships within the ccTLD community - Recent updates and developments in ccTLD operations - Policy & legislative impacts on ccTLDs - Best practices in registry management, marketing, and engagement Apply for a speaking slot by 31 January! Read more <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> APPLY NOW <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> ccNSO Council Updates Council changes New and returning Councillors The three-year term for five ccNSO Council members will end in March 2026. Elections were held to fill the seat in the Australia/Asia/Pacific region. The elected candidates are: - Africa: Ingabire Grace Mwikarago (.rw) – newly elected - Australia/Asia/Pacific: Sami Mohamed Ali (.bh) – newly elected - Europe: Chris Disspain – reappointed - Latin America/Caribbean: Alejandra Reynoso – reappointed - North America: Charles Noir (.ca) – newly elected In March 2026, Grace, Sami, and Charles will replace Molehe Wesi, Ai-Chin Lu, and Stephen Deerhake respectively. The Council adopted the regular election report at meeting 224 on 18 December. The report for the special African region election will be presented in January. The elected candidates’ term begins at the close of the ICANN85 Community Forum in March 2026, in Mumbai, India. Read more <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> Retired from the role Stephen Deerhake (.as) stepped down from the ccNSO Council at the conclusion of ICANN84, held in October 2025, bringing to a close a decade of dedicated service. Over the years, he offered institutional knowledge and a steady commitment to help shape policy discussions and strengthen collaboration within the ccTLD community. The ccNSO thanks Stephen for his service and wishes him well. Highlights December '25 ccNSO Council Meeting ccNSO Council held its 224th meeting on Thursday, 18 December. For further details, including background materials and the agenda, go to the Council workspace <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> . - celebration of the launch of the new ccNSO website - approval meeting minutes Council meeting 223 - update on "How We Meet": Implementation by staff has started - update by Council Vice Chair Biyi Oladipo, who attended the African Engagement Forum held earlier this month in Ghana - discussion regarding the settings of the Council mailing list - ccNSO membership update: As a result of a transfer, membership of the former ccTLD manager for .ly (Lybia) ended administratively. - progress ccNSO Council Selection Process African region - adoption Election Report regular ccNSO Council Selection Proces - appointment of members to ccNSO working groups and committees, including one member to MPC, two new members to SOPC and 10 members to join the newly established Study Group on IANA public records. Following a call for volunteers and a Council selection process, Frederico Neves (.br) was appointed as ccNSO representative to RZERC. - ccNSO participation in GNSO DNS Abuse Policy Development Processes. The GNSO Council has adopted the Issue Report and will launch two PDPs. Working Group charters are in development, with a call for volunteers expected in January 2026. ccNSO participation will be decided once the charters are finalized. The ccNSO Council will meet again on Thursday, 22 January for its 225th meeting. Closer to the meeting, more details will be posted on the Council workspace <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> . Happy holidays from the ccNSO! We wish you and your family a happy and safe holiday season. Best wishes for 2026! ICANN will be closed from 24 December to 2 January. The ccNSO Secretariat will be back on 5 January, ready to help you. country code Names Supporting Organisation https://ccnso.icann.org <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> | ccnsosecretariat(a)icann.org <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> [image: Facebook] <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> [image: Twitter] <https://danh45uab.cc.rs6.net/tn.jsp?f=0010EJz_q-zV9BiF9cHRKoNbifGiXufqyqjvt…> ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 US 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…>

2 1

Fwd: [Reviewsccg] Closing out 2025 - Progress update & next steps statement
by Justine Chew Dec. 19, 2025

Dec. 19, 2025

*Apologies for any receipt of duplicates due to cross-posting.* Sharing an update https://icann-community.atlassian.net/wiki/x/LQC-KQ on the work of the Review of Reviews Cross-Community Group (RoR CCG). Kind regards, Justine ---------- Forwarded message --------- From: Alice Jansen via Reviewsccg <reviewsccg(a)icann.org> Date: Fri, 19 Dec 2025 at 01:10 Subject: [Reviewsccg] Closing out 2025 - Progress update & next steps statement To: Alice Jansen via Reviewsccg <reviewsccg(a)icann.org> Dear Reviews CCG, As we conclude 2025, a status update has been posted on the wiki outlining current progress and planned next steps. The 18 December 2025 Reviews CCG Progress/Status Update [icann-community.atlassian.net] <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/LQC…> was circulated to the SO/AC Leaders list earlier today, on behalf of Co-Chairs. Please consider sharing with your groups and lists as well. Thanks! Best regards Alice _______________________________________________ Reviewsccg mailing list -- reviewsccg(a)icann.org To unsubscribe send an email to reviewsccg-leave(a)icann.org

1 0

APRALO Bytes - APRALO on Regional Internet Registry Governance, 11 Dec 2025
by Justine Chew Dec. 16, 2025

Dec. 16, 2025

Dear all, Here is the next *APRALO Byte*, which is on the topic of *Regional Internet Registry Governance*, in particular the *APRALO's position on the Second RIR Governance Document*, published at https://icann-community.atlassian.net/wiki/spaces/APRALO/pages/412844037/AP… (click on 'Read more'). Kind regards, APRALO Leadership Team ---------------------- *APRALO Bytes* (see: https://icann-community.atlassian.net/wiki/x/BYCbG) is aimed at *keeping the community apprised *of issues or topics of importance to the At-Large and/or APRALO community in a manner that is *issue/topic-focused, informative yet lightweight, while encouraging community interest and discourse* in such issues/topics. Feedback and contributions are welcomed; please reach out if you wish to contribute a Byte.

1 0

GNSO Council 11 December 2025 meeting agenda is out
by Justine Chew Dec. 16, 2025

Dec. 16, 2025

Dear all, Please be informed that the agenda for the GNSO Council Meeting of December 2025, is as follows: *GNSO Council Meeting held on 11 December 2025 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/265846872/G…>* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/UKafBg>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/CKifBg>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/ZKifBg> - *Item 1: Administrative Matters* - 1.1 - Roll Call - 1.2 - Updates to Statements of Interest - 1.3 - Review / Amend Agenda - 1.4 - Minutes - Part 1 <https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> and Part 2 <https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> Minutes of the GNSO Council Meeting on 29 October 2025 were posted on 15 November 2025. - Minutes <https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 13 November 2025 were posted on 27 November 2025. - 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 GNSO Empowered Community Representative - Confirm Standing Selection Committee (“SSC”) Members and Leadership - Confirm Standing Predictability Implementation Review (“SPIRT”) Leadership - GNSO Review of the GAC Communiqué - *Item 4: COUNCIL VOTE - Final Issue Report on a Policy Development Process for DNS Abuse* - *Item 5: COUNCIL VOTE - Registration Data Request Service (RDRS) Standing Committee Findings Report * - Item 6: COUNCIL DISCUSSION - Preparation for 2026 Strategic Planning Session (SPS) - Item 7: Any Other Business - 7.1 - SPS Logistics For more details on the marked agenda 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 *11 December 2025 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/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1> Thanks for reading / considering. *Justine Chew* ALAC Liaison to the GNSO GNSO Liaison Workspace <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Y…> ------

2 4

Fwd: [ALAC-Announce] Meeting invitation: ALAC Monthly Call on Tuesday, 23 December 2025 at 16:00 UTC
by Joanna Kulesza Dec. 12, 2025

Dec. 12, 2025

Dear all, Please note my apologies for not being able to join this call. I have followed the discussion on national and religious holidays with care. While I agree that volunteering involves personal choices about time and commitments, holding this meeting on the afternoon of 23 December will likely make it difficult for many community members to participate meaningfully. For many of us, this is an important period for family traditions and preparations for one of the major Christian holidays. From the perspective of affected volunteers, this scheduling gives the impression that our ability to engage meaningfully is being limited and at times may even appear to be intentionally so. It also creates the unintended impression that members of the Catholic community, for whom this period holds particular significance, may be placed at a disadvantage. More broadly, it raises the question of whether we are, even unintentionally, creating conditions in which colleagues with family responsibilities, fulfilling careers, or other personal commitments may find it harder to participate fully. I do not believe this is the kind of culture we aim to promote. As we are developing volunteer metrics that include meeting participation, these concerns become even more important. Scheduling meetings during widely observed holidays risks disadvantaging committed volunteers and does not support the inclusive participation that is central to the At-Large community. I respectfully encourage colleagues to reconsider how we schedule meetings and how we support volunteers, so that our practices reflect the diversity and realities of our community. I will submit my liaison report before the meeting, and I kindly ask you to accept my sincere apologies for my absence. I look forward to the meeting in January. Kind regards, Joanna pt., 12 gru 2025 o 04:47 ICANN At-Large Staff via ALAC-Announce < alac-announce(a)icann.org> napisał(a): > Dear all, > > You are invited to the next *ALAC Monthly Call* which will be on *Tuesday, > 23 December 2025 from 16:00 – 17:30 UTC.* > > > > For other times: <https://tinyurl.com/3rfzbjhn>HERE > <https://tinyurl.com/2rv5s5d5> > > > > The agenda and call details are available at: > https://icann-community.atlassian.net/wiki/x/AYB_K > > > > > > *Join Zoom > Room: https://icann.zoom.us/j/98353238091?pwd=AV7pk4YUVhwjmRWqVfb7q8NdFadAXb.1 > <https://icann.zoom.us/j/98353238091?pwd=AV7pk4YUVhwjmRWqVfb7q8NdFadAXb.1> * > *Password:** %ALAC123!!* > > > > > > *Real time transcription (RTT) link: **(subject to availability)** : https://www.streamtext.net/player?event=ICANN > <https://www.streamtext.net/player?event=ICANN>* > > > If you require a dial-out please contact At-Large staff at: *staff(a)atlarge.icann.org > <staff(a)atlarge.icann.org>* > > > > Thank you. > > Kind Regards, > > At-Large Staff > > ICANN Policy Staff in support of the At-Large Community > > www.icann.org > > > > > > _______________________________________________ > 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