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

See item 15 on the agenda today

UPDATES

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

Any pressing comments, also regarding the assigned sessions at icann84: any comments?

None

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

Alejandra: in December the new website will be launched. Very excited 🙂

Reminder to Council members on site regarding headshots taken after this meeting. Go to ccNSO room.

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.

Bart: speaking on behalf of the staff support team. Almost at the end of the policy. De-selection of idn ccTLDs. Add-on to the trigger event for the de-selection of ccTLDs. Also Review Mechanism. Major hurdles have been taken, regarding validation procedures and IDN variants.

Patricio agrees with the update.

11. Progress Review of Reviews

Informational

Alejandra: 2 plenaries and our own perspectives. We are really on our way. CCG is in fact-finding mode.

Chris: good open mic session this afternoon. Call next Tuesday to see if changes are needed to the purpose doc. It is a living doc until the end of the process. On 18 nov there will be 2 online sessions regarding the challenges and successes of previous reviews. Part of the fact finding. 2 different slots. There may be other session between now and 19 Dec. all is online, check wiki and register as an observer.

Everton: should council members subscribe? Or reach out to you?

Chris: it will help inform your thinking, please subscribe. At some point we will come to the SO/ACs. Recommendations regarding structure of the ccNSO?

Olga: estimated time?

Chris: Mumbai and the middle-of-the-year meeting. Goes to Board on 1 September.

Alejandra: icann staff and Board members are also part of the group. The wider community is responsible for making this a success. Please subscribe, and be informed.

Jordan: 2 public comment processes. Can we skip one of these?

Chris: if board did not have to repeat that exercise, would be good.

See also info on the wiki. If you have input, please email us

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

Alejandra: From the roundtable:

Staff will come back to the SOAC leaders with the CEO's views on the recommendations and their implementation.
Staff is working through the recommendations and considering their impact on the current situation, including on a few venue contracts that have been negotiated.
Staff had an initial discussion regarding the recommendation for a new session for board / community interaction. That topic seemed to need more discussion, and Mary and Sally will bring that back to the How We Meet team.

There was also a request for updating the Meeting Strategy Document to bring it to current practice particularly if recommendations from How We Meet cause divergence. The team will examine how best to do this, given the Strategy was developed by the community.

Jaijit: Are some voices not on the table? Challenges regarding .af, sanctions. Domains are expiring and domains cannot be renewed.

Alejandra: We are on a different topic. Also, it is not the role of the ccNSO to tell ccTLDs how to run their TLDs.

Biyi: out of remit for the ccNSO. Policies related to IANA.

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

Alejandra: Update from Roundtable and meeting with the Board

Roundtable Agenda:

(15 min) How we meet: update and next steps.

(15 min) Review of reviews: update and next steps.

(20 min) Proposed Bylaw amendments drafts.

(30 min) Effectiveness & Efficiency improvement.

(10 min) Code of Conduct.

Joint meeting with the Board:

Topic: Unresolved issue from previous joint meetings
Action item: Review the bylaw change playbook
Submitted prior to the meeting
Discussed with the Board.
The expectation is to provide feedback at the end of November.
Action Item: SO/AC Chairs Requests Tracker

In this context discussed to maintain a repository of agreed actions between ccNSO and ICANN org and Board

See later discussion on mailing list. Was there a deadline for comments?

Bart: guess around mid November. To initiate a process for public comment, they need to go to Board first.

The CoC was adopted. We are already implementing our own guideline. Could be considered implemented, but GRC will check nonetheless.

Effectiveness and efficiency improvement: problem statement that icann is not efficient/effective in terms of time, processes, outcomes. We want to reflect on this. Can the SO/AC chairs help, or suggest improvements? We believe things could be improved.

Re unresolved issues: we have the bylaw playbook. Submitted just prior to the meeting. Now we have an action item to review it.

Bart: see email by Russ sent on Monday. Only one option now. But tight deadline.

Alejandra: We will give our feedback one week later, and maybe discuss in November?

Bart: small group to review the doc, they prepare a response to be adopted by Council in November.

Alejandra: ok. Offline. Follow up with call for volunteers on mailing list

Regarding the request tracker.

Jordan: discovered they did not have one…. Maybe we can do that for them

AI #1: call volunteers

AI #2: joint tracker. Google doc. To see all pending items

Jordan: member of WSIS+20 dialogue group. The group met with the Kenyan Ambassador. Peter was there too. Pleasant meeting. Personal view. Challenges regarding participation in IGF. also gvt participation. Makes it hard for civil servants. A formally negotiated text of an outcome doc? Distill the dialogue that happens at an IGF, could provide more value to the gvt and other stakeholders. I spoke in the interest of disclosing what i said.

ADMINISTRATIVE MATTERS & DECISIONS

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

a. Progress Board Seat 11 Nomination

Joke: Q&A yesterday. Report by November meeting

Bart: with the adoption of the report, the process concludes. Fwd to ECA.

Patricio: thank you all once again. Deeply honoured for the trust in me. I wish to fulfil your hopes. I am a board member for the whole cooperation, but i will remember this community.

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

Joke: 3 regions without elections, AP region with election (2 nominees), AF region needs new call for nominations

Bart: use eballot. Tally phased out

Joke: Emissaries

Move? Sean

Second? Pablo

All in favour

For information and decision

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.

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. Therefore, a timeline for a new call for nomination needs to be adopted, and an Election Process Manager appointed.

Proposed timeline:

· Call for nominations: Thursday, 13 November – Thursday, 4 December 2025

· Nomination acceptance period: Friday, 5 December – Friday, 12 December 2025

· Election period (if more than one candidate): Thursday, 22 January – Wednesday, 4 February 2026

Draft Resolution

Background

The only nominee from the African region has not accepted the nomination. Therefore, a timeline for a new call for nomination needs to be adopted, and an Election Process Manager appointed.

Proposed timeline:

· Call for nominations: Thursday, 13 November – Thursday, 4 December 2025

· Nomination acceptance period: Friday, 5 December – Friday, 12 December 2025

· Election period (if more than one candidate): Thursday, 22 January – Wednesday, 4 February 2026

Decision

The ccNSO Council appoints Joke Baeken as Election Process Manager for the Council election of a Councillor from the African Region and the Council adopts the timeline as proposed. The secretariat is requested to publish this resolution. This decision becomes effective upon publication.

15. Adoption quarterly monitor ccNSO FY26-27 portfolio

For discussion and adoption

Bart: 2 reports. All in green, but it does not capture what happened since the adoption. Portfolio has been adopted in 3 out of 4 areas. Board adopted the PDP, implementation on its way, of the review mechanism. Call for volunteers post icann84 for the iana accuracy study group.

Move? Olga

Second? Ali

Any questions regarding the decision? None

All in favour

Background

Draft Resolution

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. The overview of changes to the portfolio and the quarterly update were provided by email.

Decision

The ccNSO Council supports the update to the FY26-27 Portfolio of Activities and accepts the quarterly overview. The secretariat is requested to publish the resolution, the decision becomes effective upon publication.

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

We have been asked to support the direction of travel of the proposed bylaw change and charter amendment.

The changes are needed to implement the recommendations of the 2nd CSC effectiveness review.

Bart: implementation complicated. Bylaw change track and CSC charter change track. Council has an important role.

Goal is to have everything ready by March, possibly June. will take time, but it is on track.

Stephen: regarding the CSC charter change, board approval needed?

Bart: no. starts with RySG and ccNSO Council launching the process. Hence the resolution today. You want this back to back with the bylaw change, because they refer to eachother. Both ccnso and gnso councils need to adopt the charter

Move? Pablo

Second? Sean

All in favour

Draft Resolution

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.

Decision

The ccNSO Council supports the proposed changes to the CSC charter, and to the extent necessary the proposed Bylaw changes to Article 17. The chair is requested to inform the RySG and CSC accordingly. The secretariat is requested to inform ICANN legal and other relevant ICANN staff, and publish this resolution. This Decision becomes effective upon publication.

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

In August we adopted the 2025 Guideline voluntary financial contributions and I informed ICANN accordingly. In October we received a reply form ICANN’s CEO & President, recognizing the Guideline.

As you may know the Guideline is also included in the ccNSO overview of policies, related guidance and practice relevant for ccTLDs. We now need to update the overview.

Any questions?

We have a resolution

Mover : Stephen

Seconder: Jenifer

No questions or comments

All in favour

With adoption of the final Report by the second Finance Working Group (FIN2 WG) and letters from the Council Chair to ICANN and the response from ICANN’s CEO & President, the 2013 Guideline by the ccNSO needs to be replaced with the 2025 ccNSO Guideline on ccTLD Voluntary Financial contributions to ICANN.

Draft Resolution

Decision

The ccNSO Council adopts the updated version of the overview policies, related guidance, and practices, to include the 2025 ccNSO Guideline on ccTLD Voluntary Financial contributions to ICANN and related exchange of letters between the chair of the ccNSO Council and ICANN’s CEO& President. The secretariat is requested to publish the updated overview and archive the previous version. The secretariat is also requested to publish this resolution. The decision becomes effective upon publication.

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

Excellence Award: Wafa and Demi

Any other comments?

Move? Stephen

Second? Olga

Bart: 2 people stepped forward. One for sopc and tld ops

· Jack Zack (.ca) - TLDS OPS

· Crystal Isaac (.vi) - SOPC

All in favour

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.

Draft resolution

Decision

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

· ccNSO nominees for the 2026 ICANN Leadership Program: Jordan Carter .au) and Marta Moreira Dias (.pt).

· Demi Getschko (.br) and Olaga Cavalli (ccNSO Councilor) as members of the 2026 Excellence Award Nominating Committee

· Members of the following committees, study groups or

This resolution becomes effective upon publication.

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

Draft Resolution

Decision

The ccNSO Council requests the secretariat to launch the following calls for volunteers:

a. A member of the Root Zone Evolution Review Committee.for a term of 3 years starting, starting

b. Members for the Strategic and Operational Planning committee, 11 November until 25 November 2025.

c. Study group IANA Whois Accuracy Study Group, by 20 November 2025, until 4 December.

1 january. Correction

Move? Pablo

Second? Wafa

All in favour

SUBSTANTIVE MATTERS & DECISIONS

20. Any Other Business (AOB)

Biyi: Ghana meeting 8-9 December. ccNSO invited to give an update. I will be there in person. Welcome to join.

Stephen: I am ending my term on Council at the end of this meeting. Privilege to work with you. I will pop up now and then. Not in Mumbai. I will resign from all WG, except from GRC and Tech WG. do i need to be reappointed?

Alejandra: no need

Stephen: it has been a wild ride.

Bart: at time you have been a real pain, regarding accountability and delivering on time. I feel a stomach ache when you listed dates and times, but thanks for this. It made a difference. Pleasure working with you, off and online. Bart hands over bottle of wine from Burgundy.

Stephen: board took a long time and laughed about the time we took to develop retirement

Alejandra: thank you for all your contributions

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

22. Thank You and Welcome

Thank you Desiree
Welcome Nacho

Thank you to .ie and the Contracted Party House for hosting a very special ccNSO Cocktail.

Thank you to the volunteers for organising sessions.
Thank you to the Secretariat, in-room staff and interpreters.
Thank you for participating either in person or remotely.

2 announcements

See following meetings in agenda
Headshots of councillors in ccnso room

23. Adjourn

Joke Braeken

joke.braeken@icann.org