The Council requests the secretariat to publish the response to the request for public comments on the proposed model for Root Server System Governance on the ccNSO website correspondence page. (Completed)

· Action item 221-02

The secretariat is requested to inform the leadership teams of the various working groups and committees and persons appointed, and enable their participation in the respective teams. (Completed)

· Action Item 221-03

The ccNSO Chair to remind the Council to share proposed topics to discuss with the ICANN Board in Dublin, on the mailing list. (Completed)

· Action Item 221-04

The ccNSO Secretariat to inform the Tech WG Chair of the outcome of his request to revise the ToR of the ccNSO Study Group on Disaster Recovery. (Completed)

· Action Item 221-05

The GRC to review ICANN’s Code of Conduct along with the ccNSO SOI guideline by the end of this year (2025). (Informing GRC Completed, GRC to report back by December 2025 Council meeting)

4. Intermeeting Council Decisions (since meeting 221, September 2025)

None

5. Intermeeting Decisions Triage Committee since Council meeting 221

Triage Committee accepted quarterly monitor

UPDATES

Written updates - if any - are published on the wiki space for this meeting.

6. Update ECA & CSC (written updates)

7. Update Working Groups (written updates)

a. ccPDP4-IDN (Dormant)

b. DASC

c. GRC

d. IGLC

e. MPC

f. OMC

g. SOPC

h. Tech WG

i. TLD-OPS SC

j. Triage Committee (reported)

k. UAC

l. CIP-CCG

m. Planning Prioritization Process group

n. RZERC

o. RSS GWG

p. CCG Review of Reviews (item 11)

8. Update Liaisons (written updates)

a. Update ccNSO Liaison to ALAC

b. Update ccNSO Liaison to GNSO Council

9. Update ccNSO Website redesign

Informational: Website to be launched mid December 2025

10. Progress Board Consideration ccPDP4-IDN

Informational

The fourth ccNSO Policy Development Process (ccPDP4) provides a framework to ICANN and the broader community to (i) (de-) select an IDN country code Top-Level Domain (ccTLD) strings and related variants, (ii) the delegation, transfer, revocation, and retirement of the selected IDN ccTLD string and its variants, (iii) the use of the review mechanism pertaining to decisions concerning the delegation, transfer, revocation, and retirement of IDN ccTLDs.

The proposed policy is currently under Board consideration.

11. Progress Review of Reviews

Informational

Background

ICANN's bylaws require periodic reviews of its supporting organizations, advisory committees, and other structures to ensure accountability and effectiveness. Past reviews have faced institutional lethargy, missed deadlines, and a failure to fully implement recommendations before the next review cycle begins. The current effort, formally initiated in May 2025 with a proposed Cross-Community Group (RoR CCG), seeks to break this cycle by addressing the procedural challenges within the review process itself.

12. Progress “How we meet” CCG

Informational

Background

· PURPOSE | The "How We Meet" project was initiated to review and update the implementation of the 2014 ICANN Public Meetings Strategy. The review was prompted by significant geopolitical shifts, social changes, and rising costs over the last decade, which have made it increasingly difficult to secure suitable and affordable meeting locations.

· PROCESS | A discussion group, composed of experienced community members and ICANN staff, was formed to conduct a high-level review. The group analyzed cost data, reviewed past practices, and developed a set of proposals. These proposals were then presented to the broader community for feedback through a plenary session at ICANN82, a formal Public Comment period, and further discussion at ICANN83.

· CURRENT STATUS | Following ICANN83, the How We Meet Discussion Group finalised its report, which was shared with the ICANN President and CEO.

· NEXT STEPS | An implementation plan based on the decision of the ICANN President and CEO’s decision will be developed. This plan will include clear timelines and the transparent implementation of the decision. The implementation plan is expected to be shared with the community ahead of ICANN84. A key element of this plan is the inclusion of a feedback mechanism for each change, enabling the organization to monitor outcomes and make adjustments or reversals if any measure proves ineffective or counterproductive. With the start of implementation, the Discussion Group will be formally dissolved.

13. Update Chair, Vice-chairs, Councillors, Regional Organisations and Secretariat

ADMINISTRATIVE MATTERS & DECISIONS

14. Progress Nomination process Board seat 11 & 2025 Council Election

a. Progress Board Seat 11 Nomination

Informational

Background

The current term of Patricio Poblete, the ccNSO-nominated Director for ICANN Board Seat 11, will conclude at the ICANN87 Annual General Meeting in October 2026. To ensure sufficient time for due diligence and the bylaw requirements regarding appointments, the Council initiated the nomination process in July 2025. This timeline allows the community to engage with the candidate during a Question-and-Answer session at the ICANN84 Annual General Meeting in Dublin. Patricio Poblete was duly nominated, seconded, and accepted his nomination before the deadline, in full compliance with the applicable rules. In accordance with ccNSO Council decision 219-02, an election is not required when only one candidate is nominated.

b. Progress Council selection process

For information and decision

Current status - the following candidates have accepted their nomination:

AP region - Boyoung Kim and Sami Mohamed Ali

EU region - Chris Disspain

LAC region - Alejandra Reynoso

NA region - Charles Noir

The only nominee from the African region has not accepted the nomination, hence the timeline for a new call for nomination needs to be adopted and Election process manager appointed. Suggested dates are: call for nominations starting Thursday 13 November and closing Thursday 4 December 2025. Acceptance starting Friday 5 December and closing Friday 12 December 2025. If more than one candidate the election is scheduled for 22 January to 4 February 2026.

Background

The ccNSO Council has five seats whose current three-year terms will expire in March 2026.The announcement regarding a Call for Nominations to fill these upcoming vacancies was posted on the ccNSO website and shared on the ccNSO members and Council mailing lists. The Nomination period opened on Tuesday, 9 September 2025, 00:01 UTC and closed on Tuesday, 30 September 2025, 23:59 UTC. The deadline for the nominees to accept their nomination and accept all required materials was Friday, 10 October 2025 (23:59 UTC).

If there are more candidates than seats in a region, an election will be held from 13–27 November 2025. A Q&A session for candidates will take place 29 October 2025, 14:00-15:00 UTC at ICANN84.

15. Adoption quarterly monitor ccNSO FY26-27 portfolio

For discussion and adoption

Background

The Triage committee is tasked to report quarterly on progress of ccNSO activities against planning. In that process the portfolio of activities is also updated to include new work items and if needed adjust schedules.

Background material:

· Overview of updates ccNSO FY26-27 portfolio of activities

· First quarterly monitor FY 26-27 portfolio.

16. Support CSC related Bylaw change and related amendment of CSC Charter.

For discussion and decision

Background

The 2nd CSC Effectiveness Review recommended to:

1. Develop a Framework for a regular general review of the SLAs for the IANA Naming Function Services.

2. Adjust the frequency of CSC Effectiveness Reviews from every 3 years to 5 years after conclusion of the previous review.

3. Allow for Alternates for both members and liaisons in the roster of the CSC.

The first item was completed in September 2025 with publication of the amended SLA change procedure.

To implement the other two items, the change of a Fundamental Bylaw (section 17) and amendment of the CSC charter are required.

To change the CSC charter, the RySG and ccNSO Council need to agree on the proposals, which then have to go through a public comment period. After the public comment,the final changes need to be ratified by both the GNSO and ccNSO Councils.

Background material:

· Proposed changes to the section 17 of the ICANN Bylaws

· Draft amended charter (clean and redline)

17. Update Overview policies, related guidance, and practices relevant for ccTLDs

With adoption of the final Report and letters from the Council chair to ICANN and reply from ICANN’s CEO & President, the 2013 needs to be replaced with the 2025 Guideline on ccTLD Voluntary Financial contributions to ICANN.

18. Appointment members, or chairs/vice chairs to committees or working groups, if any

Draft resolution

Decision

The ccNSO Council appoints the following people to the respective roles as specified:

· ccNSO nominees for the 2026 ICANN Leadership Program: add name

The Council needs to agree on appointment of various persons to external groups.

· ccNSO Nominees to various external groups

(https://docs.google.com/spreadsheets/d/1NdPoBTmQUVlPhMy1PsoZr6rUxUxHzRDQ/edit?gid=868409716#gid=868409716)

The secretariat is requested to inform the leadership teams of the various working groups and committees and persons appointed, and enable their participation in the respective teams. This resolution becomes effective upon publication.

19. Call for volunteers SOPC & Study Group IANA Whois Accuracy

SUBSTANTIVE MATTERS & DECISIONS

20. Any Other Business (AOB)

21. Next Council Meetings

· 20 November 2025 | 12:00 UTC, Meeting 223

· 18 December 2025 | 18:00 UTC, Meeting 224

· 22 January 2026 | 12:00 UTC, Meeting 225

· 19 February 2026 | 21:00 UTC, Meeting 226

· 12 March 2026 | ICANN85 - Mumbai, Meeting 227

· 16 April 2026 | 12:00 UTC, Meeting 228

· 21 May 2026 | 18:00 UTC, Meeting 229

· 11 June 2026 | ICANN86, Meeting 230

· 16 July 2026 | 12:00 UTC, Meeting 231

· 13 August 2026 | 21:00 UTC, Meeting 232

· 17 September 2026 | 12:00 UTC, Meeting 233

· 22 October 2026 | ICANN87, Meeting 234

· 19 November 2026 | 18:00 UTC, Meeting 235

· 17 December 2026 | 12:00 UTC, Meeting 236