NOTES ccNSO Council meeting 226 Thursday, 19 February 2026 | 21:00 UTC Background and supporting documents * Council workspace for this meeting: https://icann-community.atlassian.net/wiki/x/AQDWK * ccNSO correspondence: statements and responses: https://ccnso.icann.org/en/about/statements.htm ADMINISTRATIVE MATTERS 1. Welcome Alejandra: If you have not done so, please add Council to your Zoom ID Wiki page: https://icann-community.atlassian.net/wiki/x/AQDWK Any AOB we should be aware of? As I mentioned in a previous email I have one regarding GNSO’s PDP. no additional topics a. SOI updates Consult the ccNSO SOI Guideline<https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-21...> Complete the SOI template<https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQe...> Check the ccNSO Statements of Interest<https://community.icann.org/x/doAFEg> Alejandra: Any updates to your SOI we should be aware of? none b. Meeting quorum Claudia: apologies from ai-Chin. We are not yet quorate 2. Relevant Correspondence See: https://www.icann.org/en/ccnso/council/correspondence · Note to Russ Weinstein, SVP Policy Support re Implementation cc Review Mechanism (ccPDP3 RM), item 7 agenda · Letter of resignation from Molehe Wesi and Note to ICANN’s secretary re resignation of Stephen Deerhake and Molehe Wesi as ccNSO Councillors (item 9 c) Note two items: 1. response ccPAIG on question implementation team ccPDP3 RM and 2. resignation Molehe Wesi and notice to John Jeffrey resignation relevant to item 7 ccPDPs and Resignation of Molehe item 9c of the agenda. 3. Minutes & Action Items a. Minutes Meeting 225 Circulated to the Council mailing list on 9 February 2026 Any questions? None. Minutes are confirmed! b. Action Items All action items are completed except 225-06 on written procedure to select Fellowship related ccNSO appointees. Awaits action by the GRC, but they are aware. Suggest to close from a Council perspective. * Action item 225-01 The Council requests the ccNSO Domain Abuse Standing Committee (DASC) to nominate up to two (members), up to one (1) participant and an alternate, [to represent the ccNSO in GNSO PDP 1 DNS Abuse Associated Domain Name Check] and inform the ccNSO Council as soon as feasible, and no later than 30 January 2026. (Completed) * Action Item 225-02 The Chair of the Council is requested to inform the GNSO secretariat before 9 February 2026 of the nomination of the ccNSO representatives in GNSO PDP 1 DNS Abuse Associated Domain Name Check (Completed) * Action Item 225-03 The secretariat is requested to seek volunteers for the IGLC review as feasible to ensure the review can start in February. The Review team should include 3-5 members of which at least 3 Councillors. Members of the Review Team are not expected to be a member of the IGLC. (Completed) * Action Item 225-04 The ccNSO Chair is requested to inform the Fellowship Program of the ccNSO Mentor and Selection Committee appointments. (Completed) * Action Item 225-05 The GRC is requested to propose a procedure to select the ICANN Fellowship related positions taking into consideration that they need to be Councillors. (Completed) * Action Item 225-06 The ccNSO Guidelines Review Committee (GRC) is requested to review the Council Selection Process Guideline, taking into account the recommendations from the Selection Process Manager. (Pending) * Action Item 225-07 The Secretariat is requested to inform ICANN’s Secretary of the election results in accordance with section 10.4(i) of the ICANN Bylaws. (Completed) * Action Item 225-08 The ccNSO Chair is requested to respond to Eberhard on behalf of the Council with the decision to keep interpretation for Tech Day (Completed) UPDATES Written updates - if any - are published on the wiki space for this meeting. The draft written updates for items 4, 5 and 6 in our inboxes. In the meantime does anyone have any pressing comments? Peter: not pressing. Regarding the RSS GWG. i was appointed in 2022 for a 1-year term. The group will come to a close. Consensu call. Including report on public comments. There will be a session at ICANN85 to share the results. Depending on how the board deals with it, there will be a council for the Root Server Governance. ccNSO would have 6 seats. Can we brainstorm on how to deal with that? Alejandra: yes. Let’s do that during the prep call Peter: 6 persons is a challenge. No need to make selection now. 4. Update ECA & CSC (written updates) 5. Update Working Groups (written updates) a. ccPDP4-IDN (Dormant) b. DASC c. GRC d. IGLC e. MPC - item 14 (Adoption of Review) f. OMC - item 12 (Support mentoring program) 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 6. Update Liaisons (written updates) a. Update ccNSO Liaison to ALAC b. Update ccNSO Liaison to GNSO Council 7. Progress Board Consideration ccPDP4-IDN & Implementation ccPDP3 Informational Bart: you are quorate. Bart: regarding PDP4. Due to the board workshop, the group has not met since the previous council meeting. They will meet again next week. First review of the sections. Preparing for the full board consideration Alejandra: implementation ccPDP3? Bart: letter ccPAIG. Is related. ccPAIG met in January. The group developed a letter. The topic: having non-precertified reviewers. 3-person panel. Claimant and iana to use a pool. Non-precertified reviewer. Annex D suggested to do this. The group preferred not to do this. Assuming the pool of reviewers would be large enough. Was also the direction of travel from the implementation team. Re ccPDP3 Refer to question from Implementation Planning team to ccPAIG and outcome of discussion. ccPAIG responded that the proposal had to be related to the size and diversity of the pool of reviewers. If the pool would be small, need to find non pre-certified reviewers to allow choice to constitute a 3 members panel to review, and allow both the ccTLD manager and IANA to select a panelist. 8. Progress CCG Review of Reviews Informational Chris: prep meeting session, consultations in Mumbai, and then a plenary session. 5 buckets * Accountability and transparency * Continuous improvement * Structural review * (missing notes) * Ad hoc review Input received. ISPC, RySG. input also welcome at the meetings. 9. Update Chair, Vice-chairs, Councillors, Regional Organisations, Secretariat a. One-on-One ICANN CEO and ccNSO leadership Alejandra: topics discussed: * ccNSO participation in GNSO PDP DNS Abuse * ICANN’s outreach and messaging. Need for balanced messaging. b. Webinar AFTLD Alejandra: purpose and goal of the ccNSO. Introduction from some WGs. Hopefully inspired others to join Biyi: nothing to add. Engagement with African community. Sensitives the african community about the work of the ccNSO c. Resignation Molehe Wesi Alejandra: i notified the icann secretary regarding his resignation. I’d like to take this opportunity to thank Molehe for his work in the ccNSO Council. Your contributions were always towards grounding the conversation, ensuring we respected due process, and doing so with remarkable serenity. Wishing you all the very best in your next chapter. Alejandra: I received from LACTLD a request to fill a survey regarding their Strategic Planning Process 2026-2030 survey Suggestion is to let the LAC councillors reply. The due date is the end of the month. Everton: happy LACTLD reached out. Happy to answer from the region. But there are other councillors that are lactld members too. Invite them too, even if they are from other regions. Alejandra: agree. Please let us know if you wish to contribute Pablo: happy to volunteer. I am not from LAC region, but culturally would like to take part in the initiative Sean: i volunteer too. Alejandra: any other updates? ADMINISTRATIVE MATTERS & DECISIONS 10. Submit Council Statement public comment section 17, 18 and charter of CSC. For decision Alejandra: As you may have noted, the Board supported the change to Article 17 and 18 on the Frequency of IANA Function Reviews and CSC effectiveness reviews and, in addition, the change to membership structure of the CSC, allowing Alternates. The changes to CSC had also to be reflected in the Charter of the CSC. The public comment includes all the changes in parallel. https://www.icann.org/en/public-comment/proceeding/fundamental-bylaws-amendm... Note the Public comment closes 30 March These changes have been discussed by the Council at the end of 2025. Note the amendment of Article 17 and 18 are changes to a Fundamental Bylaws, requiring approval by the Decisional Participants. Timeline: * Public Comment: 11.Feb - 30.Mar. * Report Due: 13.Apr. * Board Consideration for approval. * Empowered Community Process - Fundamental Bylaws - Approval Action * Community Forum - Seville 8-11 June - ECA needs to request it. * 21 days after Community Forum (3 DP approval and not more than 1 objection) Suggest Council Statement, very light weight in support of the proposed changes. Peter: we should not remain silent. It was our initiative, we should respond. In favour of lightweight. Move? Sean Second? Peter Draft Resolution Decision The ccNSO Council requests its Chair to draft a Council statement in support of the proposed Bylaw changes and amended Customer Standing Committee Charter. The draft Statement is expected by Council Meeting 227, for adoption by Council. This decision becomes effective 7 days after publication. Questions? None All in favour 11. Introduction update SOI Guideline Informational and for review Material circulated 17 February 2026 Sean: introduces the Guideline and changes to it. Triggered by icann Code of Conduct. We completed the review last week. highlights: * Alignment with the ICANN CoC * Expanded info we ask for. E.g. country of residence. To keep it aligned. * More process and a structured escalation path. What happens if an SOI is not up to date? Escalation path up to suspension. Lively conversation: is there enough opportunity to update the SOI? Structural changes by the secretariat. Clear link to where to find the SOIs included in the agenda Automatic review in a 5-year period. Does not change the substance, but strengthening the language Claudia: on the wiki, there is a link to the new website Bart: next steps. Today was the intro of the new guideline. Please review. Respond to GRC or secretariat. GRC to review the guideline if needed. Then go to membership. Alert Councillors to review the draft over next week until 26 February, to allow GRC to update draft and alert community to Guideline in Mumbai. Approval by April meeting Jordan had to leave, the meeting is no longer quorate. ?We can discuss, but decisions need to be taken offline after the call. 12. Approval OMC mentor/mentee program For Decision Material circulated 17 February 2026 Alejandra: Form Background -The ccNSO onboarding and mentoring committee (OMC) is tasked with the onboarding, mentoring and engaging newcomers in the activities of the ccNSO. As part of these tasks the OMC wants to launch a mentoring program building on the previous very successful program (refer to Eyitayo and Mary). Tayo is now our NomCom appointee. Biyi: reference to success from the previous programme. Bart: oversight role for OMC. preferably mentor/mentee from the same region. Not limited to one mentor/mentee. Alejandra: online decision Draft Resolution Background The ccNSO onboarding and mentoring committee (OMC) is tasked with the onboarding, mentoring and engaging newcomers in the activities of the ccNSO. As part of these tasks the OMC has updated the 2018 mentoring program, developed under auspices of the ccNSO Onboarding and Involvement Standing Committee (OISC), which has been formally closed. Due to the pandemic and its aftermath, the OISC mentoring program was never carried forward beyond an initial start in 2019. Although the OMC was mandated to launch and oversee a mentoring program, the OMC seeks Council support for the program, to ensure broader support and visibility. Decision The ccNSO Council supports the ccNSO mentoring program as proposed by the ccNSO Onboarding and Mentoring Committee. The secretariat is requested to inform the OMC of this decision and publish as soon as possible. This decision becomes effective upon publication and the Council wishes the OMC success with the program. 13. Update and closure 360 Councillors review Draft resolution Background Per Council decision at meeting 225, the ccNSO Council 360 review was launched on 23 January 2026, and closed 18 February. The results were circulated to the Council members on 18 February. The Council notes that a minimum 11 Councillors have completed the survey and have concluded the survey in time. Alejandra: 1 on 1 are happening or scheduled. The process is done. Any questions or comments? None Decision The ccNSO Council formally closes the January - February 2026 360 Councillors survey. This is a Council administrative decision and becomes effective upon publication. 14. Update MPC Review Informational/for decision Material circulated 17 February 2026 Sean: second time we did the review. We learned a lot on this. How our meeting structure helps and hinder this process. In interviewing people, the passion comes out. Really good. Something to build upon. That goes to the leadership. Everton, Alejandra, Katrina, Gudrun. Good group. Support from the secretariat shows. Recommendations: * Continue MPC * Improve: what the MPC does, align it with reality Find a way to be more involved where you can be involved ccTLD News is so well accepted. Refine for the 3rd review. Peter: agree. The review taught me a lot about the committee. Change focus a bit, and continue to deliver the great work Olga: agree. Especially regarding ccTLD News. Everton: review process is important to MPC. look into the ccNSO work itself. Structures that are perpetual. Happy to be part of this. Bart: if you start reviewing this. What is important, going forward, is the annex. Documentation regarding the agenda-setting process. Of the overall ccnso program during ICANN meetings. Please read it critically. Interplay between ccnso leadership, mpc, staff, and leadership of other committees. It clarified the role of the MPC in representing the community, and set the agenda. It is an empowerment of the community. Ensure it is useful for all. Alejandra: Next steps: we will take a decision online, to give your time to assess the outcome. You will be asked to support the findings and recommendations. Note this recommendations include update of charter of MPC and 2021 Guideline: ccNSO meetings (https://itp.cdn.icann.org/en/files/resources/guidelines-council-meetings-31m...) 15. Approval ccNSO membership application .ly For Decision ccNSO membership application General Authority of Communication and Informatics, ccTLD Manager .ly (Libya) Joke: Following the transfer of the .LY (Libya) top-level domain to the General Authority of Communications and Informatics (GACI), membership in the ccNSO of the former ccTLD manager ended at the end of October 2025. The current ccTLD manager applied to become a ccnso member. IANA Services team reviewed the application: there are no concerns or pending actions to be brought to Council’s attention. Alejandra: questions? Good that it was so quick. We lost a member, but the ccTLD re-joined. That is good Draft resolution Decision The ccNSO Council approves membership of the General Authority of Communication and Informatics, the ccTLD Manager of .ly (Libya) and welcomes the General Authority of Communication and Informatics as member 180 of the ccNSO. The Chair of the ccNSO is requested to formally welcome the General Authority of Communication and Informatics as member. This resolution becomes effective upon publication. 16. Appointments to committees or working groups, if any For decision Standard item: this time membership DASC and Appointment IGLC Review Team. Candidate from the AFTLD webinar. Good result of our outreach. Any questions on the topic? Resolution Decision The ccNSO Council appoints the following persons as Members of the following committees, study groups or working groups: § Idrissa Sarr (.ng) - Member DASC § Jenifer Lopez, Alejandra Reynoso, Sean Copeland (all Councillors), and Nick Wenban-Smith (.uk) as members of the IGLC Review Team 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. Barrack and Joke: affiliation is .sn SUBSTANTIVE MATTERS & DECISIONS 17. Planning for ICANN85 Informational a. Draft ccNSO schedule Joke: For information about the ccNSO at ICANN85, go to https://www.icann.org/en/ccnso/meetings Claudia: go to https://icann85.sched.com/ and create your own agenda Alejandra: see council prep on roles and responsibilites. We will also discuss how to elect Chair and Vice Chair b. Preparing for Roles and responsibilities: https://docs.google.com/spreadsheets/d/1fmToQ3l3nrj78jgwy8RpFGLF4qfq7jrW/edi... https://itp.cdn.icann.org/en/files/resources/roles-responsibilities-council-... Bart: first a nomination and a secondment at the meeting, vote only if more than one candidate. Vote by the current councillors only. Think about the future leadership team and discuss. Alejandra: chair and vice chair need to be from different regions Claudia: no public zoom link. You will receive them in your inbox 24 hours prior to meeting start 18. Any Other Business (AOB) Alejandra: Earlier today forwarded a message where Paul McGrady, the preliminary Chair of the Working Group, has approached me requesting early written input from the ccNSO. My proposal is to reply to Paul, referring to the ccNSO Council Resolution 225-01, which states that “[...] the ccNSO does not have a view, nor holds a position on the matter addressed through the PDP, nor do the members represent a view or position of ccTLDs in general.” 19. Next Council Meetings · 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 - Sevilla, 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 - Muscat, Meeting 234 · 19 November 2026 | 18:00 UTC, Meeting 235 · 17 December 2026 | 12:00 UTC, Meeting 236 20. Adjourn Thank you all. Joke Braeken joke.braeken@icann.org<mailto:joke.braeken@icann.org>