The chair of the ccNSO Council is requested to share the final report of the second ccNSO Finance Working Group with ICANN’s CEO and President, specifically the Principles and Banded Model in Annex A. The chair of the Council is also requested to suggest to ICANN to use a segmented and personalized conversation regarding the voluntary financial contribution by ccTLDs as contemplated in the Final Report.

Action item 220-02 (completed)

The secretariat is requested to replace the 2013 Guideline with the 2025 Principles and Banded Model, when the decision to adopt the final report of the second ccNSO Finance Working Group becomes effective.

Action item 220-03 (completed)

The secretariat is requested to publish the resolution regarding the adoption of the 2nd IFRT recommendations as soon as possible.

Action item 220-04 (completed)

The secretariat is requested to inform the ccNSO appointee on the CCG, upon publication of the resolution to support the transfer of IANA intellectual property rights from the IETF Trust to the IETF IPMC.

Action item 220-05 (completed)

The Council requests Peter Koch and Luis Diego Espinoza, the ccNSO appointed members to the RSS GWG, to advise the drafters of the ccNSO submission in response to the request for comments on the proposed Functional Model for Root Server System Governance.

Action item 220-06 (completed)

The secretariat is requested to seek volunteers from Council to join a drafting team of the ccNSO submission in response to the request for comments on the proposed Functional Model for Root Server System Governance, and start the drafting process as soon as possible

Action item 220-07 (completed)

The ccNSO Secretariat is requested to publish the updated review schedule for ccNSO working groups and committees. The secretariat is requested to seek volunteers for the MPC review starting in September, and is requested to update the ccNSO workplan accordingly.

Action item 220-08 (completed)

Regarding the appointment of the members to the various working groups and committees, the secretariat is requested to inform the respective working groups and enable the appointees to fulfil their role. The secretariat is requested to publish this resolution as soon as possible on the ccNSO website.

4. Intermeeting Council Decisions (since meeting 220, August 2025)

None

5. Intermeeting Decisions Triage Committee since Council meeting 220

None

UPDATES

Written updates are available, or will be coming soon. Anything we should be aware of?

None

Skipping to item 9

6. Update ECA, IFRT & 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

k. UAC

l. CIP-CCG

m. Planning Prioritization Process group

n. RZERC

o. RSS GWG

p. ICANN How We Meet Group

q. CCG Review of Reviews

8. Update Liaisons (written updates)

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

a. Update ccNSO Liaison to ALAC

b. Update ccNSO Liaison to GNSO Council

9. Update ccNSO Website redesign

Informational

2nd part of the proofreading has been completed.

Everton: looking forward to the new website

10. Progress Board Consideration ccPDP4-IDN

Informational

Patricio: 2nd reading validation procedure has been completed. Next meeting: items that require in depth analysis. We are making progress.

Alejandra: looking fwd to completing this task

Patricio: same!

Background

This fourth ccNSO Policy Development Process (ccPDP4) will provide a framework to ICANN and the broader community for (i) the selection of IDN country code Top-Level Domain (ccTLD) strings and variants thereof, (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

Alejandra: see email by Chris with link to the wiki. No co-chairs appointed yet. Impression that this goes slower than we would like. But at least the process started, let’s wait for the next meeting, and what they will prepare for us by Dublin.

Note: prep week session, and 2 plenaries in Dublin.

Bart: in addition, a ccNSO internal session on Tuesday afternoon. Opportunity for the ccnso appointed members to solicit views from the ccTLD community.

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: We invested quite some time on this. Consultations, a public comment period. The next steps are the development of an implementation plan, based on input received from the sessions and the public comment.

Molehe asked to provide info on current status, but he lost connectivity.

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. Progress Nomination process Board seat 11

Informational

Joke: On 4 September, ICANN Legal informed the Council chair and the nomination process manager

that the due diligence has now been completed for Patricio, and
that the due diligence report does not contain anything that would lead them to raise any red flags with the ccNSO leadership.

Alejandra: early congratulations to Patricio

Patricio: thank you very much! Relieved.

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.

14. Progress Council selection process

Informational

Joke: Status to date:

There has been at least one nomination from each geographic region, except for two regions: Latin America/Caribbean and North America (so far).
Among the nominations received, the candidate from the African region and the European region have been seconded to date. A nomination must be seconded by the Representative of another ccNSO member from a different territory but from the same geographic region.

The candidate from the European region was nominated by an individual who is not the representative. As per the current Council Selection Guideline, the election process manager reached out the Representative, and sought confirmation, which is still pending.

Alejandra: nomination period closes 30 September. But let’s not wait until the last minute. Please talk to your region

Stephen: The North American region will have a candidate within the next week. We are discussing internally.

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 closes: Tuesday, 30 September 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. Update Chair, Vice-chairs, Councillors, Regional Organisations and Secretariat

a. Chair update

i.Planning webinar: ccNSO update to LACTLD

Planning is ongoing

ii. ccNSO update to APTLD

SOPC was showcased. It went well. One additional volunteer stepped forward. Let’s hope this works as well for the LACTLD region

iii. Monthly SO/AC Chairs meeting

Thinking about some of the topics that were raised previously, but were not properly addressed. E.g. risk aversion, use of tools and timeline for implementation, what are the plans for how we meet, when will the current meeting guideline be reviewed to reflect current and future practices, and review on reviews.

Bart: Yesterday was the first meeting by the ccPAIG on the Review Mechanism. The board adopted the proposed policy in Prague. ICANN is planning implementation and consulted with ccPAIG. Went very well, from both sides. There will be more meetings forthcoming.

16. CSC related matters

a. Selection of Membership

Informational

The full slate was approved by ccNSO Council Selection Committee. ICANN Staff and GNSO Council was informed.

Bart: GNSO also approved the full slate. Term starts 1 oct.

b. Bylaw and Charter Update to accommodate Adjustment frequency of reviews and Alternates

Informational

Bart: ICANN org asked about the alternate, and the text in the bylaws on the frequency. Staff prepared discussion points for you to look at. These were put in draft text, with the charter and the bylaws. Waiting for feedback from icann legal, and next steps. Both councils have an important role in the charter of the CSC, mainly on the alternates.

Alejandra: Will sth happen before Dublin?

Bart: crystal ball

ADMINISTRATIVE MATTERS & DECISIONS

17. Adoption draft response to request for comments Root Server System Governance Working Group

Alejandra: I circulated the comment yesterday. Concise and to the point.

Jordan: concern around the number of volunteers. Nothing controversial in the comments

Peter: agree. The number of people is a result of all the root server operators being present. Currently 12. Other parties to represent the ccTLDs and gTLDs to balance that out. Would be great if the RS operators could find a way for representation. A committee of 24 would be too big. My role is on both sides, so I prefer to abstain.

Background

A public comment proceeding presents the Functional Model developed by the Root Server System (RSS) Governance Working Group (GWG) in response to Root Server System Advisory Committee (RSSAC) advice. The document describes the RSS Governance Structure and provides recommendations on how to implement it. The document also introduces the governance principles that will ensure consistency in execution and decision-making.

Draft Resolution

Decision

The ccNSO council resolves to adopt the response to the request for public comments on the proposed model for Root Server System Governance. The Council requests its chair to submit the response that was drafted for that purpose, after this resolution becomes effective. The ccNSO Council wholeheartedly thanks the drafting team. The Council requests the secretariat to publish the response on the ccNSO website correspondence page. This resolution becomes effective upon publication.

Questions/comments on the resolution? None

Move? Pablo

Second? Sean

Abstain? Peter

All in favour

Bart: session in Dublin on Wednesday at the end of the day. Joint session with RSSAC. Peter will introduce the RSS for the ccTLD community

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:

· Member MPC Effectiveness Review Team: Olga Cavalli (NomCom Councillor), Irina Danelia (.ru), Khaled Khelifi (.tn), Peter Koch (.de), Sean Copeland (.vi)

· Member SOPC: Mostofa Al Mahmud (.bd)

· Member ccNSO Study Group IANA disaster recovery: Peter Koch (.de), Antonia Chu (.cn), Barrack Otieno (AFTLD), Irina Danelia (.ru), Katrina Sataki (.lv), Jodi Anderson (.nz)

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.

Questions/comments on the resolution? None

Abstain? Sean, Peter

Move? Everton

Second? Pablo

All in favour

Wafa: Khaled Khelifi (.tn) was a newcomer at ICANN83. Happy he joined.

Alejandra: our onboarding activities show effect! thank you Wafa

SUBSTANTIVE MATTERS & DECISIONS

19. ICANN84

Informational and for discussion

a. Reminder ccNSO-relevant programme

Bart: We extensively discussed the agenda last time.

Some highlights

b. Joint session ccnso & RSSAC

b. Joint session ccNSO & GAC on domain abuse. It is a joint effort. Same format as in Seattle. Breakout sessions, 2 or 3 rounds. GAC has proposed a few topics. So did the DASC, for discussion in smaller groups

b. WIPO will present during the Welcome session on the services they provide to ccTLDs

b. Review of Reviews

b. GRC World Cafe on CI: invitees are WG/C leaders, councillors, and others, on the principles adopted to assess the effectiveness and functionality of the ccnso. Continuous improvement work

b. Iana Study Group will meet on Saturday.

b. The iana and disaster recovery on wednesday. Sharing different perspectives. What is in place? What was the issue raised by iana during the PGA work?

b. Council prep and meeting itself

j. Topics for discussion during joint session with Board

Alejandra: please start thinking about it. Homework for all. Please share topics on the mailing list. I will remind all early next week

k. Reminder about the calls for presentation proposals

Joke: reminder earlier this week. It had an effect. Currently enough proposals for an interesting session

Peter: WSIS+20 developments. we have IPC2, RSS GWG, own PGA stuff … issues on the radar of the GAC. make sure the board has an eye on that. Connect different dots happening in different communities.

These are the operational internet governance things. IG in action. Within ICANN, the poster child for MSM IG. Send consistent messages. How this contributes to the success messages. Make sure we are all on the same page. Message to the board

Joke: IGLC organises a session on WSIS+20 and beyond. With ccTLD presentations in support of the MSM, IGF LP panel participation, and Kenyan Ambassador appointed by UN to the WSIS review.

20. Any Other Business (AOB)

i. buddy program

Bart: OMC launched a buddy program. Started in prague. Survey among buddies and newcomers. It has been updated. Shortly you will receive an invite to become a ccNSO buddy to support ccNSO newcomers as they attend ICANN84 sessions, and begin participating in our work. Additionally, please alert your network about ways to help get newcomers to the ccNSO started:

Newcomer webinar on 7 october
Newcomer info package for ICANN84
Casual ccNSO newcomer meet up at ICANN84

Announcements coming soon to your inboxes!

Everton: deadline? Expectation to let the committee know who from the organisation are willing to, expected to attend the icann meeting?

How long in advance?

Bart: The sooner the better, the more we can prep.

Wafa: very complete

Biyi: agree

ii. Council to revise the Terms of Reference of the ccNSO Study Group on the IANA role in Disaster Recovery to add Tech WG Chair or a Vice-Chair as an ex-officio member.

Request by Eberhard, Tech WG Chair

The charter was adopted in June 2025.

The purpose of the Tech WG is to organize meetings to provide the country code Top Level Domain (”ccTLD”) community and the broader community with advice and to share information on the technical and operational aspects of, and related to, operating a Top Level Domain (“TLD”).

Note: Tech Day WG is tasked with organizing Tech Day, at times members of Tech WG are asked to work together with SOPC to comment on aspects of the PTI budget, operating plan and strategy, and are not member ex-officio.

Note that the TLD-OPS chair is appointed ex-officio to the Study Group.

Peter: struggle to understand what extra benefit or burden the ex officio membership provides. We are usually open to the community? Other avenues are more than open.

Alejandra: nothing really different. Ex-officio means almost “voluntold”. We expect the person to participate. The call for volunteers was open. There were no restrictions. No reason not to apply, even if it was not part of the terms of reference

Jordan: every time there is a technically related topic, expectation. We should get volunteers who want to be involved. The focus is on organising Tech Day. suddenly making ex officio appointments?

Peter: We should not widen the scope or the impression of the scope of the Tech WG by giving it a blessing/importance/role that goes beyond what it has. TLD-OPS is much closer to the topic. More a policy topic, than a technical topic. I would respectfully decline the suggestion.

Wafa: i support the request of the Tech WG chair. Same rationale as TLD-OPS chair. He must have a rationale for his request. Perhaps we can ask him what the position would add? Anyone who wants to join gives an added value

Alejandra: the chair did not apply to become a member. He requested a change of the ToR. of the ccNSO Study Group on the IANA role in Disaster Recovery to add Tech WG Chair or a Vice-Chair as an ex-officio member.

The call was open to all. They could have applied, but they did not. We would have appointed them today. They asked to change the ToR. not to join.

Jordan: I support him (or anyone) joining the study group.. just not a formal recognition of an ex officio membership

Alejandra: Do we agree to decline this request politely? Green tick. Red if you disagree

Only green ticks.

iii. ICANN adopted a Code of Conduct for community participation

https://www.icann.org/en/system/files/files/adopted-icann-community-participant-code-of-conduct-14sep25-en.pdf

Bart: the SO/ACs are expected to implement it. The level of implementation will be reviewed after 2 years. Good idea for GRC to review this, and the ccNSO SOI guideline

Sean: before Dublin? Before the end of the year?

Bart: Dublin is very tight

You have the board removal on your dance card. Maybe as your next project.

Sean: does not look overly burdensome.

Bart: end of the year is probably ok. 2 meetings after Dublin.

Peter: IFRT. retrospective. Some items will come back. Suggestions made to change the frequency. Bylaws change, and we would have to vote on it again. Both ccnso and gnso councils voted. Now in the hands of the board. Needs to digest, and make suggestions on how to progress. Great team, great staff support. Different than the 1st time. Thanks for appointing me as co-chair. If all works well, we have the frequency change.

Alejandra: thank you

Peter: Ashley Heineman as co-chair was fundamental in shaping this, at this speed.

Alejandra: bylaw amendment. Make sure they do not overlap with the CSC reviews.

21. Next Council Meetings

· 26 October 2025 | 08:00-09:00 UTC | Council prep (ICANN84)

· 30 October 2025 | 14:00-15:00 UTC, Meeting 222 (ICANN84)

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

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

22. Adjourn

Thanks all.

Joke Braeken

joke.braeken@icann.org