[ccnso-council] NOTES | ccNSO Council meeting 228 | Thursday, 16 April 2026

NOTES ccNSO Council meeting 228 Thursday, 16 April 2026 Background and supporting documents * Council workspace for this meeting: https://icann-community.atlassian.net/wiki/x/AYDZK * ccNSO correspondence: statements and responses: https://ccnso.icann.org/en/about/statements.htm ADMINISTRATIVE MATTERS 1. Welcome Welcome by Alejandra. On Zoom: shorter version of the agenda, to fit into mentimeter. We will use mentimeter for voting. AOB: * Peter - Sounding board for IANA/Root Servers related liaisons * Everton - Oman planning? 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? none b. Meeting quorum Claudia: tentative apology from Jordan Apology from Charles. You are not quorate yet: missing from North America Alejandra: hope they join later. Decisions later 2. Relevant Correspondence See: https://www.icann.org/en/ccnso/council/correspondence No relevant correspondence since meeting 227. 3. Minutes & Action Items a. Minutes Meeting 227 Circulated to the Council mailing list on 8 April 2026 Alejandra: questions? None Welcome to Russ Introduces himself. Took on the role in January 2025, following up from David and Sally. Joined ICANN in late 2012 for the first round of the new gTLD program. He worked on that program on the operational side. Set up evaluation panels and pre-delegation procedures. Familiar with birthing of new gTLDs. He supervised the engagement team. Supporting registries in gTLD space. Familiar with the gTLD space. Learning about the ccTLD experience and the role of ccTLDs in the ICANN community. Very grateful for role of the ccTLDs in the ICANN space, including support of the MSM model. Alejandra helping the SO/ACs to collaborate better. Better facilitate cross-community work. Talking about common agendas and priorities. Working together. Thank you for all you do, and your contribution to the model. You deserve our support, and thank you for the time you commit. Alejandra: approaches ccTLDs have, compared to the gTLD registries. Welcome Pablo and others joined. We are now quorate b. Action Items Alejandra: all completed. Any questions? none * Action item 227-01 The secretariat is requested to inform the ICANN secretary of the election of Alejandra Reynoso as ccNSO Council Chair and post an announcement on the ccNSO Website. (Completed) * Action item 227-02 The secretariat is requested to inform the ICANN secretary of the election of Adebiyi Oladipo and Jordan Carter as ccNSO Council Vice-Chairs and post an announcement on the ccNSO Website. (Completed) * Action item 227-03 The secretariat is requested to publish the overview of roles and responsibilities and their assignments on the ccNSO website as soon as possible. (Completed). * Action item 227-04 The Council requests its Chair to publish the comments on the proposed change of Articles 17, 18 and the charter of CSC. (Completed) * Action item 227-05 The Council requests the ccNSO Universal Acceptance Committee (UAC) to draft a comment on ICANN’s Universal Acceptance Expert Group’s draft Guidelines for Advancing UA Adoption and to submit it in the related public comment forum on their own behalf. (Completed) * Action item 227-06 The secretariat is requested to publish FY 26-27 Portfolio Activities and the February 2026 quarterly overview (Completed) * Action item 227-07 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 227-08 The secretariat is requested to confirm on whether the Council would submit a comment on the Standard Bylaws Amendment – Transition Article on Specific Reviews Public Comment. (Completed) 4. Intermeeting decisions a. Appointment of participants to the Chairing Skills Pilot Training b. No Comment on Standard Bylaws Amendment – Transition Article on Specific Reviews Questions or comments? none 5. Triage Committee decisions since Council meeting 227 Chris: updates to its working methods. Will be presented to Council at the upcoming meeting Bart: by ICANN86 there will be an updated version of the 2-year working plan. UPDATES Written updates - if any - are published on the wiki space for this meeting. Joke: streamlining the written updates More news at next meeting Peter: we finished the final report of the RSS GWG. the formal closure has not been announced. Likely after input from board. Alejandra: we will mark it as dormant for the time being. Chris: will be challenged seen work with RoR Alejandra: will mark as action item to replace Chris in Planning Prioritisation Group 6. Update ECA & CSC (written updates) 7. Update Working Groups (written updates or taken from the meeting) 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 8. Update Liaisons (written updates) a. Update ccNSO Liaison to ALAC b. Update ccNSO Liaison to GNSO Council 9. Progress Board Consideration ccPDP4-IDN & Implementation ccPDP3 Bart: * ccPDP4. Caucus nearly completed its assessment. Planning activities undertaken. * The implementation of ccPDP3: planning itself - ccPAIG played a role in interpretation of the policy. Used in the assessment. Implementation planning concluded. The focus now moved from Russ and his team to GDS. ongoing work. It awaits the actual implementation work. The implementation plan: org expects that the ccPAIG remains available, in case something comes up. Alejandra: noted that ccPAIG needs to remain in place Patricio: not much to add what Bart said. The caucus is almost done with the reading of policy. Next steps regarding implementation. Likely after the next workshop, at the end of the month. 10. Progress CCG Review of Reviews Alejandra: will be part of the written updates Chris: by Monday latest all SO/AC chairs will receive doc with the current position. It is building on the chart you saw in Mumbai. We reduced the number of buckets. 3 instead of 5. Webinar coming soon. ccNSO can submit comments. In at least some of the cases there will be scoping groups. Based on the SO/AC leaders group. We will suggest a chat directly with them, to ensure the workload is clear, and avoid any concerns. We will have a prep week webinar. Doc for comments will be adjusted, and turned into the draft proposal which will be sent out for comments and talked through in Sevilla. Alejandra: plenary session. But no ccNSO session Chris: plenary on Monday. We are happy to meet with SO/ACs, but appreciate the schedule may be full. But plenary is the main opportunity to say what people want to say. 11. New standing item: Update GNSO DNS Abuse Mitigation PDP1 Alejandra: should it move to the written updates? Nick was appointed vice chair. With that, the Charter allows us to appoint a new member. See call for volunteers https://www.icann.org/en/ccnso/news-and-announcements/documents/call-for-vol... Any other updates? No hands raised Alejandra: remain as standing item? Or move to written updates? Peter: proposal to keep in the agenda. I am an observer Dynamic at the moment. Ambitious schedule. Let’s keep it until it is less dynamic. 12. Update Chair, Vice-chairs, Councillors, Regional Organisations, Secretariat a. Update Chair Alejandra: We are coordinating the agenda for Sevilla. Chairs are working towards making icann more effective and efficient. 1-on-1 with the CEO will be held in May. I had a meeting with .es welcoming them to the ccNSO and giving them a brief introduction. Their membership application is on the agenda later today Russ announced he needed to drop off Working on Webinar jointly with APTLD to raise awareness about work. Once a date is set, Councillors from AP region, could you reach out to your contacts in the region to alert people. Goal is to raise awareness of work ccNSO does, and how to participate ranging from attending sessions remotely to becoming Councillor b. Update secretariat Bart: I am retiring on 1 October. Seville will be my last meeting. Do not be surprised if you see related notifications, e.g. I joined in 2007 in March - just before the Lisbon meeting - when I took over from Donna Austin. 20 years with ICANN, not entirely 20 years with ccNSO I am 69, and I have 5 grandchildren. There are other nice challenges. I need to address some medical issues. I do not want to be a burden to the team, seeing the experience a few years ago. Announcing now, so you can get used to it, and we ensure continuity. Joke and Claudia remain available. Nigel: I briefly lost connection. Bart: I am retiring on 1 October. Seville will be my last meeting. Alejandra: feels different now that it is formal. Your impact will be felt long after day. Celebrate your remarkable journey. “Dear Bart, You and I have talked about your possible retirement for some time, and while I’ve had time to adjust knowing it was coming, it feels different now that it’s been formalized. Your impact on all of us is already clear and will continue to be felt long after today. As you share your plans for retirement, it gives us both a chance to celebrate your remarkable journey and a bit more time to appreciate having you with us. Your dedication, integrity, and steady leadership have shaped not only the work we do, but the way we do it. You have set a standard that is both inspiring and humbling to follow. What stands out most is not just your extraordinary professional accomplishments of making the ccNSO what it is today, but the way you’ve shared your knowledge, supported others, and led by example. Many of us here are better at what we do because of your guidance, and I count myself among them. I’m very grateful for that. Pablo: Thanks for all you learned from us. Thank you for your work ethics Joke: i am sure there will be many goodbye speeches. Very grateful for all you learned us, glad you are staying around a couple more months. We will miss our friend” Pablo: Thanks for all you learned us. Thank you for your work ethics. I will think about you when i spot articles that i believe you should read. Joke: i am sure there will be many goodbye speeches. Just wanted to say thank you on the record for all you did for the ccNSO and for us at the Secretariat. Very grateful for all you learned us, glad you are staying around a couple more months. I will miss my friend. ADMINISTRATIVE MATTERS & DECISIONS 13. Approval Membership .es ccNSO membership application RED.ES , ccTLD Manager .es (Spain) Draft resolution Decision The ccNSO Council approves the membership of RED.ES, the ccTLD Manager of .es (Spain) and welcomes RED.ES as member 181 of the ccNSO. The Chair of the ccNSO is requested to formally welcome the RED.ES as a member. This resolution becomes effective upon publication. Joke: membership application was submitted. IANA services team confirmed: No issues to bring to Council’s attention. ready for approval Patricio: were they a member previously? Joke: no. gvt related, which made things a bit slower. ccNSO work is open to all ccTLDs, regardless of membership status. Move? Olga Second? Pablo Voting via mentimeter: 16 votes in favour. No abstentions, no-one against. 14. Approval ccNSO Guideline Statement - and Conflict of Interest For Decision Draft Resolution Background Following the adoption of ICANN’s Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-particip...> by the ICANN Board in September 2025 an update of the 2023 ccNSO Statement of Interest Guideline<https://itp.cdn.icann.org/en/files/resources/ccnso-internal-procedure-genera...> was considered necessary, to align the 2023 Guideline with the 2025 ICANN Code of Conduct. The GRC developed the updated version, which was circulated to Council for review in February 2026 and ccNSO Members. No suggestions were made To align with the ICANN Code of Conduct the following changes to the 2023 ccNSO Guideline were made: · Include Explicit reference to the ICANN Code of Conduct and clarify their relationship. · Add the provision about non-participation when disclosure cannot be made. · Include familial relationships in the list of interests to disclose. · Expand examples to cover more scenarios (researchers, patent holders, consultants with multiple clients). Excluded from the update are: · Allow for issue-specific supplemental disclosures when interests differ by topic · Add training and education commitments for ccNSO participants. Decision The ccNSO Council adopts the proposed ccNSO Guideline General Statement of Interest & ccNSO [Council] Conflict of Interest (version 2, April 2026). The Secretariat is requested to post the Guideline and this decision on the ccNSO website, and inform the various Committees and Working groups of the update of the Guideline. This decision becomes effective seven (7) days after posting of the decision. Sean: SOI and COI by ccNSO done a few years ago. In the meanwhile ICANN came up with documentation. We did an alignment process. Procedural changes. More detailed questioning. Aligned with the community as a whole. Move? Everton Second? Olga 14 in favour 1 abstention Can be published and will be effective 7 days later. 15. Shadowing fellowship mentor For information and action Proposed action: Request GRC to update selection procedure (https://ccnso.icann.org/sites/default/files/field-attached/guidelines-ccnso-...) to select fellowship mentor and alternate/shadow mentor. Jenifer has been our Fellowship Mentor for a few years now and she has expressed that this would be her last year in this role. We have agreed that the person to be a Fellowship Mentor should be a councillor (to ensure someone who is on top of all things ccNSO and broader ICANN) and preferably someone who has been a fellow. As most of you know, I started my ICANN journey through the fellowship program in 2011 and I was the fellowship mentor for the ccNSO before Jenifer. When the time came to introduce a new mentor, to ease the transition Jenifer (who had also been a fellow) shadowed me in my last year as mentor. This time, Everton has indicated interest in the mentor role and, having been a fellow himself, it's a good match for the position. Everton: When I was a fellow, Alejandra was my mentor. I would be pleased to be considered for this role Jenifer: I appreciate the trust placed in me and to have been allowed to take on the role. Trust that Everton will do a great job Pablo: As a reminder, the GRC has been requested to put in writing the selection process of the fellowship mentor and (as an action item) it should include the alternate/shadow mentor into account for completeness. 16. Appointments to committees or working groups, if any · Desiree Miloshevic (.gi) to IGLC · Others tbd’ed Draft Resolution Decision The ccNSO Council appoints the following persons as Members of the following committees, study groups or working groups: · Desiree Miloshevic (.gi) to IGLC The secretariat is requested to inform the leadership team of the IGLC and persons appointed and enable their participation in the respective teams. This resolution becomes effective upon publication. Move? Peter Second? Pablo Questions or comments regarding the resolution? None Olga and Nigel mentioned that menti is not working Alejandra: for the sake of time, let’s use the old ways. Bart: It was an experiment, but it turned out not to be stable enough. Let’s use the old method. Green ticks in zoom - reactions. Or red. If you abstain, please let me know explicitly. 16 votes in favour approved. SUBSTANTIVE MATTERS & DECISIONS 17. ICANN86 a. Draft Block Schedule Joke: introduction high level schedule ccNSO sessions Reminder call for presenters for ccTLD News https://www.icann.org/en/ccnso/news-and-announcements/documents/call-for-pre... Bart: study groups will present their results to date. They need to inform the broader community. This is a draft schedule. Let’s see. Might also impact the casual meet-up Chris: why not an open session? Half a slot for each of the SGs? Bart: that is the idea. Chris: they need their working sessions. But the update to the community is more important. b. Council meeting Alejandra: This is a policy forum, no time for prep meeting in Seville. Suggest we do a prep call ahead of the meeting: major item will be assignment of session/prepping for the meeting. Check if people want. c. ccNSO Cocktail sponsorship Alejandra: we still seek sponsors. If you know about anyone, please reach out to Claudia 18. Any Other Business (AOB) Peter: see my email to Council. RSS GWG. we spoke about it in the prep session at ICANN85. There might be a need for better coordination when the structure is in place. See also RZERC, CSC, IANA functions review. Committee of councillors as a sounding board? I shared the idea with a few people. I got positive feedback from one liaison appointee. Others are present. Any suggestions? Not sure what the next step would be? To be handed over to the GRC? Feedback appreciated. Alejandra: something for Triage to consider. I appreciate the proposal. Everton: I would like to express my concern about ICANN87. The persistent instability in the region makes it vital to prioritize the continuity of an in-person meeting. To ensure ICANN87 remains a face-to-face event, and we’re just 6 months away from it, ICANN Org should leverage its current flexibility to secure a viable alternative location. I suggest the Council formally request a defined communication strategy and contingency timeline from ICANN Org. This will ensure participants remain informed and can proceed with stable travel and budget planning during these challenging times. Patricio: org and board are aware of the issues. Alejandra through the SO/AC leadership, in close contact with Kurtis and org. Chris: I understand, ICANN has until a date in June, up to which it can pull the contract with Oman. Last year it was pure good fortune Dublin could happen. Not likely we can find another venue, if we are not going to Oman. likely we will have an online meeting. Pablo: I can imagine a lot of work is happening that we are not aware of. Referring to zika virus experience and the impact on the icann meeting. Sami: what Everton proposes is a good proposal. Wellness perspective. Oman is not involved in the conflict. Travelling: it is what it is. Generally, Oman is the safest for this region, for now. Thanks for all who checked in on us. We are all safe. Alejandra: thanks to Sami. hope everyone stays safe. Aware of the concerns. We trust ICANN to work on solutions. On the safety side of things. Concerns grow. We have not heard anything. Are they considering options? The silence keeps us unaware and leaves room for us to speculate on possible consequences. We can bring those concerns to the leadership. Will raise it with the other SO/AC chairs. See if we can get a message from ICANN regarding their thoughts for the future. Perhaps write sth to the Board. 19. Next Council Meetings · 21 May 2026 | 15:00 UTC, Meeting 229. Note the changed time due to overlap with pre-ICANN86 policy webinar Alejandra: please note the time change. · 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>