January 2026 - ALAC - lists.icann.org

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

April 24, 2026

Dear Colleagues, The SSAC welcomes the opportunity to comment on ICANN's Draft Applicant Guidebook (AGB) for the New gTLD Program: Next Round. Our comments focus on improving Section 6.7 on Name Collisions, with an emphasis on risks arising from collisions between DNS and alternative naming systems (e.g., blockchain-based systems), as outlined in the Name Collision Analysis Project Study 2 Report (NCAP2). SUMMARY OF KEY RECOMMENDATIONS: * Clarify TRT's Role in Initial Assessments AGB §6.7.2 does not clearly state that the Technical Review Team (TRT) conducts the initial name collision risk assessment. NCAP2 indicates TRT is responsible from the outset. _Recommendation:_ Explicitly assign the initial assessment to the TRT. * Enable Pre-Delegation Action on High-Risk Strings Current language suggests high-risk strings are identified only after temporary delegation. NCAP2 supports action based on existing data. _Recommendation:_ Allow TRT to recommend withholding delegation if early analysis shows high risk. * Broaden TRT's Assessment Scope Beyond DNS Data Limiting analysis to DNS logs misses collisions from alternative namespaces that resolve via DNS (e.g., users accustomed to _.wallet_ from blockchain). ➤ _Recommendation:_ Permit use of OSINT, qualitative assessments, and external data sources per NCAP2. * Allow TRT Flexibility to Evolve Assessment Methods AGB cites four NCAP2 methods (NI, CI, VI, VIN), but doesn't state whether TRT may adopt new techniques. _Recommendation:_ Affirm TRT's discretion to evolve methods to address future risks. These updates will better align the AGB with NCAP2 and ICANN Board guidance, while improving transparency, security, and technical rigor in handling name collisions. The SSAC appreciates the efforts of the ICANN org and Subsequent Procedures IRT, and we are available for further discussion. Link: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe…. Best, Matthias

3 4

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

April 21, 2026

Dear Colleagues, please find below my report. I apologize for not being able to attend the ALAC Monthly meeting on August 26th. Have a nice day! Best, Matthias Publications: SAC130: SSAC Comments on Name Collision Guidelines in the Proposed Language for the Draft Next Round Applicant Guidebook The SSAC welcomes the opportunity to comment on ICANN's Draft Applicant Guidebook (AGB) for the New gTLD Program: Next Round. Our comments focus on improving Section 6.7 on Name Collisions, with an emphasis on risks arising from collisions between DNS and alternative naming systems (e.g., blockchain-based systems), as outlined in the Name Collision Analysis Project Study 2 Report (NCAP2). SUMMARY OF KEY RECOMMENDATIONS: * Clarify TRT's Role in Initial Assessments AGB §6.7.2 does not clearly state that the Technical Review Team (TRT) conducts the initial name collision risk assessment. NCAP2 indicates TRT is responsible from the outset. _Recommendation:_ Explicitly assign the initial assessment to the TRT. * Enable Pre-Delegation Action on High-Risk Strings Current language suggests high-risk strings are identified only after temporary delegation. NCAP2 supports action based on existing data. _Recommendation:_ Allow TRT to recommend withholding delegation if early analysis shows high risk. * Broaden TRT's Assessment Scope Beyond DNS Data Limiting analysis to DNS logs misses collisions from alternative namespaces that resolve via DNS (e.g., users accustomed to _.wallet_ from blockchain). _Recommendation:_ Permit use of OSINT, qualitative assessments, and external data sources per NCAP2. * Allow TRT Flexibility to Evolve Assessment Methods AGB cites four NCAP2 methods (NI, CI, VI, VIN), but doesn't state whether TRT may adopt new techniques. _Recommendation:_ Affirm TRT's discretion to evolve methods to address future risks. These updates will better align the AGB with NCAP2 and ICANN Board guidance, while improving transparency, security, and technical rigor in handling name collisions. The SSAC appreciates the efforts of the ICANN org and Subsequent Procedures IRT, and we are available for further discussion. Link: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe…. Ongoing work parties: * DNSSEC Operational Considerations Work Party * Open-Source Software Work Party * Responsible Integration of External Technologies into the DNS * SSAC Workshop Work Party SSAC Membership Applications: The application deadline is closed now and potential candidates are being assessed by the Membership Selection Committee. SSAC Workshop: For SSAC members only, will be held in September in Mexico City.

2 6

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

Feb. 16, 2026

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

1 1

ccNSO Council Meeting #225 – Summary Report
by Laura Margolis Jan. 30, 2026

Jan. 30, 2026

Dear All: The last ccNSO meeting #225 took place on Thursday 22nd. January 2026 at 12:00 UTC Agenda and Background Documents <https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/683016247/…> Written Updates January 2026 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99711461/AL…> ccNSO correspondence: statements and responses <https://ccnso.icann.org/en/about/statements.htm> The ccNSO has launched a *new website <http://ccnso.icann.org/>*, much easier to navigate and find information, please check it: http://ccnso.icann.org *ccNSO Council Meeting #225* *Key Discussions and Decisions* *1. Participation of the ccNSO in the GNSO PDP on DNS Abuse* The Council held an extensive discussion on whether and how the ccNSO should participate in the GNSO PDP on Associated Domain Name Checks related to DNS Abuse. - The Council agreed that the benefits of participation outweigh the potential risks, particularly in terms of sharing ccTLD expertise, supporting the multistakeholder model, and contributing to DNS abuse mitigation across the ecosystem. - It was acknowledged that the ccNSO does not hold an official position on the matters addressed by the PDP, nor do ccTLDs constitute a homogeneous group. - The Council *approved participation with two members and one alternate,* noting the importance of transparency, clear mandates, and regular feedback to the Council and the broader ccNSO community. - The *DNS Abuse Standing Committee (DASC)* was tasked with identifying suitable candidates, taking into account expertise, time commitment, and the PDP charter requirements. - The resolution was unanimously adopted, with a nomination deadline of 30th. January 2026, and notification to the GNSO Secretariat by 9th. February 2026. *2. Minutes and Action Items* - The minutes of Council Meeting #224 were approved without comments. - Most action items from the previous meeting were confirmed as completed. Outstanding items relate primarily to the African Region special election process and guideline reviews. *3. Updates* Written updates from Committees, Working Groups, and Liaisons were acknowledged and published on the meeting workspace. Additional highlights included: *DASC (DNS Abuse Standing Committee) <https://ccnso.icann.org/en/workinggroups/dasc.htm>* DASC members have been invited to participate in an NCUC-organized webinar on DNS abuse mitigation and its impact on civil society and end users, scheduled for 11th. February at 15:00 UTC; an invitation to the At-Large community will follow. In line with the Council decision to participate in the GNSO PDP on DNS Abuse, DASC, together with the Council, will support the evaluation of candidates for member, participant, and alternate roles. The Committee is also discussing a request from WIPO for observer status and will consult the full DASC membership via a survey outlining arguments for and against a time-limited observership. In preparation for ICANN85, a joint *ccNSO–RySG* session is planned, focusing on ongoing PDPs and their potential spill-over effects on ccTLDs. The next DASC survey is planned for July–August 2026. *IGLC (Internet Governance Liaison Committee) <https://www.icann.org/en/ccnso/committees-and-working-groups/internet-gover…>* The IGLC meeting focused on recent Internet governance developments and priorities for the 2026 workplan. Updates covered WSIS+20, and early preparations for the ITU Plenipotentiary Conference that will take place this year in Qatar, highlighting revised resolutions on access, IPv6, multilingualism, and the recognition of the technical community. Members noted the growing prominence of regulatory and online safety issues and their potential relevance for ccTLDs. The Committee reviewed past work and initial input for 2026 planning. Despite limited survey engagement, members agreed that key topics remain the same, with the future of Internet governance, sovereignty, resilience, and online harms emerging as priority areas, subject to impact-effort assessment and coordination with related ccNSO work An update from the *OMC <https://www.icann.org/en/ccnso/committees-and-working-groups/onboarding-and…>* on onboarding and mentoring initiatives, including plans to reinvigorate the mentoring programme and organize newcomer engagement activities at ICANN85. Progress updates on *ccPDP4-IDN* (Board consideration ongoing) and *ccPDP3-RM implementation*, with further discussion anticipated with ICANN staff. *If you would like to see updates on the rest of the working groups and committees, please click here <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99711461/AL…>* *4. Councillor 360 Review* The Council approved the timeline for the next round of Councillor 360 reviews: - Survey launch: 23 January 2026 - Survey closure: 13 February 2026 - Results shared: 19 February 2026 Bart Boswinkel was appointed as Survey Process Manager. *5. IGLC Review* The Council adopted the Terms of Reference for the effectiveness and efficiency review of the IGLC and requested the Secretariat to seek volunteers to ensure the review can commence in February 2026. *6. Appointments* - Jennifer Lopez was appointed as Fellowship Program Mentor. - Pablo Rodriguez was appointed as Member of the Fellowship Selection Committee. No additional applications for committee or working group appointments were received since the previous meeting. *7. African Region Special Election* The Council adopted the Selection Report for the African Region and formally confirmed the election of *Grace Ingabire*, with the term commencing at the conclusion of ICANN85 in Mumbai. *8. Planning for ICANN85* - A draft ccNSO schedule was reviewed. - The Council agreed to *continue providing interpretation services during Tech Day*, emphasizing the importance of inclusiveness and effective participation across regions and languages. This is all for now, if you need any additional information or you have any questions, I will be happy to answer. Thank you. 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…>

3 2

At-Large Board Member Selection
by Alan Greenberg Jan. 27, 2026

Jan. 27, 2026

As you may know, Leon Sanchez is term-limited as the ICANN Director Selected by At-Large and the process to name his replacement is ongoing. The candidates are (in alphabetical order by surname): Sebastien Bachollet, Justine Chew, Maureen Hilyard and Lito (Rafael) Ibarra. The candidate’s Statements as well as their Expressions of Interest (their application forms) have been posted. - Candidate Statements <https://icann-community.atlassian.net/wiki/spaces/ABMS/pages/770211889/2025…> - Expressions of Interest <https://icann-community.atlassian.net/wiki/spaces/ABMS/pages/760020998/2025…> There will be two public ways to interact with the candidates. - You may ask questions that will be answered in writing and posted. Questions may be targeted at all candidates, or particular candidates. Candidates are not obliged to respond, but historically, they do. Questions may be merged with others if they are on the same topic, or otherwise edited by the chair/members of the Board Member Selection Process Committee (BMSPC <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/398163969/B…>). Please specify if a question is for a specific candidate(s). - There will be a public Candidates’ meeting, most likely at the end of the week of 09 February 2026. Each candidate will be asked to respond to a few questions. If you have a suggestion for these questions, please let us know. Please send questions to At-Large Staff <staff(a)atlarge.icann.org> and me <greenberg.alan(a)gmail.com>. Questions should be submitted no later than Friday, 06 February 2026. Alan Greenberg Chair, BMSPC

1 0

REMINDER- Office of Ombuds Framework and Process - Open for comments until Wednesday Jan 28th
by Silvia Vivanco Jan. 27, 2026

Jan. 27, 2026

Dear OFB and ALAC members, This is a kind reminder, as per the timeline, the Draft statement “Office of Ombuds Framework and Process<https://www.icann.org/en/public-comment/proceeding/icann-office-of-ombuds-f…>“ is open for comments until Wednesday 28th January 19 UTC. The small team will present the Final Draft at the OFB call on Thursday 29 January. Please comment directly in the DRAFT ALAC statement google doc, using the “comment” function, see draft at : “ ICANN Office of Ombuds Framework and Process<https://docs.google.com/document/d/1Q0xiTQ838RAVjhLha23aj0dVl50N_tMujasw-nY…>” Statement Timeline: 1. First draft presentation - OFB call 22 Jan 2. Community: Comment on Draft Statement 22-28 Jan– 3. Presentation- Final Draft - 29 January 4. ALAC: Vote on Final Statement –Friday 30 Jan - 02 Feb Staff: Submission of ALAC Statement – by 10 Feb Thank you very much! Silvia

1 0

REMINDER- Draft ALAC statement open for comment until Wednesday Jan 28th - ICANN FY27–31 Operating & Financial Plan, ICANN/IANA FY27 Op Plans & Budgets
by Silvia Vivanco Jan. 27, 2026

Jan. 27, 2026

Dear OFB and ALAC members, This is a kind reminder, as per the timeline, the Draft statement “ICANN FY27–31 Operating & Financial Plan, ICANN/IANA FY27 Op Plans & Budgets<https://www.icann.org/en/public-comment/proceeding/icann-fy2731-operating-f…> “is open for comments until Wednesday 28th January 19 UTC. The small team will present the Final Draft at the OFB call on Thursday 29 January. Please comment directly in the DRAFT ALAC statement google doc, using the “comment” function, see draft at : “ICANN FY27–31 Operating & Financial Plan, ICANN/IANA FY27 Op Plans & Budgets<https://docs.google.com/document/d/1EDlc8AMoYmjtcu762HUYRFbkvMIXrrCSvaSJFKu…>” Statement Timeline: 1. First draft presentation - OFB call 22 Jan 2. Community: Comment on Draft Statement 22-28 Jan– 3. Presentation- Final Draft - 29 January 4. ALAC: Vote on Final Statement –Friday 30 Jan - 02 Feb Staff: Submission of ALAC Statement – by 12 Feb Thank you very much! Silvia Silvia Vivanco Senior Manager, At-Large Regional Affairs Website: atlarge.icann.org<http://atlarge.icann.org/> [signature_3739878956]

1 0

Re: REMINDER- ALAC Draft statement -Open for comments until Wednesday 28 January 19 UTC - DRAFT PTI FY27 Operating Plan and Budget
by Silvia Vivanco Jan. 26, 2026

Jan. 26, 2026

Dear OFB and ALAC members, This is a kind reminder, as per the timeline, the Draft statement “Draft PTI FY27 Operating Plan and Budget<https://icann-community.atlassian.net/wiki/spaces/alacpolicydev/pages/70546…>“ is open for comments until Wednesday 28th January 19 UTC. The small team will present the Final Draft at the OFB call on Thursday 29 January. Please comment directly in the DRAFT ALAC statement google doc, using the “comment” function, see : Draft PTI FY27 Operating Plan and Budget<https://docs.google.com/document/d/19pP2f5bzNau-4McKTwXmE0wTFqRGR9REGhdt_RO…>“ Statement Timeline: 1. First draft presentation - OFB call 22 Jan 2. Community: Comment on Draft Statement 22-28 Jan– 3. Presentation- Final Draft - 29 January 4. ALAC: Vote on Final Statement –Friday 30 Jan - 02 Feb Staff: Submission of ALAC Statement – by 12 Feb Thank you very much! Silvia Silvia Vivanco Senior Manager, At-Large Regional Affairs Website: atlarge.icann.org<http://atlarge.icann.org/> [signature_3739878956] From: Silvia Vivanco <silvia.vivanco(a)icann.org> Date: Thursday, January 22, 2026 at 5:08 PM To: OFB-WG <ofb-wg(a)icann.org>, "alac(a)icann.org" <alac(a)icann.org> Cc: At-Large Staff <staff(a)atlarge.icann.org> Subject: ALAC Draft statement - DRAFT PTI FY27 Operating Plan and Budget - Open for comments until Wednesday 28 January 19 UTC Dear OFB and ALAC members, As per the timeline, the Draft statement “Draft PTI FY27 Operating Plan and Budget<https://icann-community.atlassian.net/wiki/spaces/alacpolicydev/pages/70546…>“ is now open for comments until Wednesday 28th January 19 UTC. The small team will present the Final Draft at the OFB call on Thursday 29 January. Please comment directly in the DRAFT ALAC statement google doc, using the “comment” function: Draft PTI FY27 Operating Plan and Budget<https://docs.google.com/document/d/19pP2f5bzNau-4McKTwXmE0wTFqRGR9REGhdt_RO…>“ Statement Timeline: 1. First draft presentation - OFB call 22 Jan 2. Community: Comment on Draft Statement 22-28 Jan– 3. Presentation- Final Draft - 29 January 4. ALAC: Vote on Final Statement –Friday 30 Jan - 02 Feb Staff: Submission of ALAC Statement – by 12 Feb Thank you very much! Silvia Silvia Vivanco Senior Manager, At-Large Regional Affairs Website: atlarge.icann.org<http://atlarge.icann.org/> [signature_3739878956]

1 0

ALAC Draft statement - DRAFT PTI FY27 Operating Plan and Budget - Open for comments until Wednesday 28 January 19 UTC
by Silvia Vivanco Jan. 22, 2026

Jan. 22, 2026

Dear OFB and ALAC members, As per the timeline, the Draft statement “Draft PTI FY27 Operating Plan and Budget<https://icann-community.atlassian.net/wiki/spaces/alacpolicydev/pages/70546…>“ is now open for comments until Wednesday 28th January 19 UTC. The small team will present the Final Draft at the OFB call on Thursday 29 January. Please comment directly in the DRAFT ALAC statement google doc, using the “comment” function: Draft PTI FY27 Operating Plan and Budget<https://docs.google.com/document/d/19pP2f5bzNau-4McKTwXmE0wTFqRGR9REGhdt_RO…>“ Statement Timeline: 1. First draft presentation - OFB call 22 Jan 2. Community: Comment on Draft Statement 22-28 Jan– 3. Presentation- Final Draft - 29 January 4. ALAC: Vote on Final Statement –Friday 30 Jan - 02 Feb Staff: Submission of ALAC Statement – by 12 Feb Thank you very much! Silvia Silvia Vivanco Senior Manager, At-Large Regional Affairs Website: atlarge.icann.org<http://atlarge.icann.org/> [signature_3739878956]

1 0

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