April 2026 - Ccnso-council - lists.icann.org

NEW: ICANN to Host Question-and-Answer Sessions for New gTLD Applicants
by ICANN Community Digest April 16, 2026

April 16, 2026

Email from ICANN Thursday, 16 April 2026 ICANN Community Digest Click here to learn more about the New gTLD Program 2026 Round Applicant Guidebook 2026 Round Vendor Sourcing Timeline The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org! Table of Contents Information Sharing NEW: Publication: ICANN and the IETF NEW: ICANN to Host Question-and-Answer Sessions for New gTLD Applicants NEW: You Said; We Listened: Public Comment Proceeding and Ombuds Office Improvements 2026 Round NEW: 2026 Round TAMS Webinars and Newly Available FAQs CLOSES MONDAY: Call for Expressions of Interest: 2026 Round Independent Objectors Key 2026 Round Updates and Resources Next Round Champions Toolkit Available in the Six ICANN Languages Webinars NEW: ICANN to Host Question-and-Answer Sessions for New gTLD Applicants Preview the ICANN FY27–31 Operating and Financial Plans 🚨 Action Items 🚨 CLOSES TOMORROW: ICANN86 Community Childcare Grants Program: Apply Now CLOSES SUNDAY: ICANN Board Seeks Input on Additional Funds for 2026 Round Applicant Support Program CLOSES SUNDAY: ICANN87 Fellowship Application Round Now Open ICANN Request for Proposal: Global Payroll Services ICANN Issues Request for Proposal: 2026 Round Auction ICANN Board Seeks Input on Additional Funds for 2026 Round Applicant Support Program ICANNWiki Seeking Volunteers Public Comment NEW: Public Comment Summary Report: Fundamental Bylaws Amendments on IANARelated Reviews and CSC Charter Update Draft Evaluation Guides for Community Priority Evaluation (CPE) Events These events occur in April 2026. Information Sharing NEW: Publication: ICANN and the IETF The Internet’s infrastructure is maintained by the coordinated efforts of many. The engagement of the Internet Corporation for Assigned Names and Numbers (ICANN) with the Internet Engineering Task Force (IETF) constitutes one essential thread in that fabric. Read more. NEW: ICANN to Host Question-and-Answer Sessions for New gTLD Applicants ICANN is hosting a new webinar series dedicated to answering questions about the TLD Application Management System (TAMS) and other aspects of the 2026 Round gTLD application process. TAMS is the online system used by applicants, ICANN staff, and evaluation panelists to manage, process, and submit new gTLD applications. While the focus of the webinars will be on how to use TAMS, potential applicants are invited to pose questions on other aspects of the gTLD application and evaluation processes as well. Pre-submitted questions will be prioritized during the four webinars. Attendees are invited to submit questions using this submission form. Read more. NEW: You Said; We Listened: Public Comment Proceeding and Ombuds Office Improvements I was very pleased to receive 11 submissions from individuals, organizations, and community groups with valuable suggestions for Ombuds Office improvement. Read more. 2026 Round NEW: 2026 Round TAMS Webinars and Newly Available FAQs TAMS is the online system that will be used by applicants, ICANN staff, and evaluation panelists to submit, manage, and process new gTLD applications. Read more. CLOSES MONDAY: Call for Expressions of Interest: 2026 Round Independent Objectors ICANN opened a Call for Expressions of Interest (EOI) to identify three individuals to serve as Independent Objectors, including one who will act as chair, as part of the New Generic Top-Level Domains (gTLD) Program: 2026 Round. The Independent Objectors will file Community and Limited Public Interest objections and appeals and participate in mediation, where appropriate. Although an individual may be affiliated with a firm, that person will be ultimately responsible for the processes described in this EOI. Individuals from the same firm will not be selected. Deadline: 20 April 2026 Read more. Key 2026 Round Updates and Resources Stay tuned for more information and updates as we approach the 30 April 2026 opening. Read more. Next Round Champions Toolkit Available in the Six ICANN Languages ICANN is working with the community to identify potential Applicant Support Program (ASP) applicants – especially in regions that are currently under-represented in ICANN. If you are interested in helping to raise awareness among your own contacts or communities, please use the materials in the Next Round Champions Toolkit. To stay up to date on the New gTLD Program: Next Round and ASP, join the mailing list: nextroundinfo(a)icann.org. ASP leads, targets, and ideas can be sent to engagement.newgTLDprogram(a)icann.org. Webinars NEW: ICANN to Host Question-and-Answer Sessions for New gTLD Applicants Dates: 21 April, 16:00 UTC | 21 April, 23:00 UTC | 12 May, 16:00 UTC | 26 May, 16:00 UTC Read more and register. Preview the ICANN FY27–31 Operating and Financial Plans Date: 23 April 2026 (15:00–16:00 UTC) Register. Action Items CLOSES TOMORROW: ICANN86 Community Childcare Grants Program: Apply Now ICANN opened the application round for its Community Childcare Grants Program for ICANN86 in Seville, Spain. The program facilitates the in-person participation of community members with children who are 12 years old or younger at ICANN Public Meetings and eligible ICANN events. Deadline: Friday, 17 April 2026 Read more. CLOSES SUNDAY: ICANN Board Seeks Input on Additional Funds for 2026 Round Applicant Support Program The ICANN Board is requesting community input via written correspondence on additional funds for the ASP. NEW Deadline: 19 April 2026 Read more. CLOSES SUNDAY: ICANN87 Fellowship Application Round Now Open ICANN is opening the application round for the ICANN Fellowship Program for ICANN87 Annual General Meeting. The ICANN87 meeting is scheduled for 17–22 October 2026 in Muscat, Oman. If ICANN87 is held virtually, the Fellowship Program also will be held virtually. The deadline to apply is 19 April 2026 at 23:59 UTC. Read more. ICANN Request for Proposal: Global Payroll Services ICANN's preference would be to contract with one provider that can support all in-scope countries; however, under certain considerations ICANN may be open to selecting multiple providers as part of this initiative. Deadline: 8 May 2026 Read more. ICANN Issues Request for Proposal: 2026 Round Auction The selected provider will implement the ascending-clock, second-price auction method and must have the capability to accommodate a high volume of auctions, including both direct and indirect contention sets. Deadline: 2 June 2026 Read more. ICANNWiki Seeking Volunteers ICANNWiki is seeking volunteers to assist with creating and editing articles and content for the site. Do you want to help? Getting started is as simple as requesting an account. Then, make sure to read the short content guide to get a feel for what belongs in the wiki. Also, feel free to take a look at some data source suggestions on where to find reliable data. Happy editing! Public Comment NEW: Public Comment Summary Report: Fundamental Bylaws Amendments on IANARelated Reviews and CSC Charter Update Draft Evaluation Guides for Community Priority Evaluation (CPE) Open for Submissions Date: Tuesday, 24 March 2026 Closed for Submissions Date: Monday, 04 May 2026 See upcoming proceedings. See other public consultations. Events These events occur in April 2026. To learn more, please visit our community engagement calendar. 1st African Preparatory Meeting for WTSA-28 CaribNOG 31 Regional Meeting USTTI Cybersecurity Leadership ARIN 57 48 Meeting of PCC.I ZANOG@iWeek 2026 Volume 8, Issue 26 | Archive | Next Issue: Monday, 20 April 2026 STAY INFORMED: Subscribe here ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 US Unsubscribe | Update Profile | Constant Contact Data Notice

1 0

NOTES | ccNSO Council meeting 228 | Thursday, 16 April 2026
by Joke Braeken April 16, 2026

April 16, 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-2…> Complete the SOI template<https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQ…> 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-vo… 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-partici…> 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-gener…> 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-pr… 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(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Apols likely for tonight
by Jordan Carter April 16, 2026

April 16, 2026

Dear council colleagues I fear I’m probably an apology tonight - the meeting is at 10pm here but I’m up for an early flight at 5am. I’ll attend if I can but if not, please have a good meeting and I’ll see you on the May call. Cheers Jordan

3 2

April ccNSO Council Teleconference (228) | 16 April at 12:00 UTC
by ccNSO Calendar April 16, 2026

April 16, 2026

***REMINDER*** Dear Council, The April ccNSO Council Teleconference (228) is scheduled for 16 April at 12:00 UTC. The agenda will be circulated prior to the call. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/95356618704?pwd=b9q3ALVvwuLFodFNgAmNKTPkKhma7p.1 Meeting ID: 953 5661 8704 Passcode: ccNSO-0228 Wiki page: https://icann-community.atlassian.net/wiki/x/AYDZK Thank you!

1 0

f'up from Mumbai: proposal for Council 'sounding board' for liaison appointees
by Peter Koch April 15, 2026

April 15, 2026

Dear Colleagues, following our disscussion in Mumbai regarding a potential future request to work in a RSS GS (root server system governance structure), here is a proposal for a broader approach: ----------------------------------------------------------------------------- The ccNSO appoints various liaison (and similar) positions into other ICANN structures and cross community committees and groups. Some of those are other SOs, some are more leaned to the governance of technical funtions. The latter are CSC [regular appointments] RZERC [regular appointments] IANA Functions Review (reocurring 1-2 yrs after every 5 yrs) (Root Server System Governance Structure Council, TBD) The liaisons/appointees report back to the Council formally, by written reports or, occasionally, by ad hoc calls or invitations to a Council session. This is lightweight and has worked reasonably well, but the feedback and interaction could be improved. Inspired by, but not copying the ICANN Board's Board Technical Committee (BTC), it is proposed to the Council to form a structure (name TBD), comprised of a subset of Councillors (3-6, details TBD) to act as a 'sounding board' for appointees to share observations, raise issues or ask for guidance. It is meant as an offer to the appointees and is supposed to enhance the communication between the appointees and the council and, optionally, also between the appointees. It should remain lightweight and as informal as possible with the focus on facilitating the communication. The need for staff support should be minimal accordingly. As a potential add on, the group of councillors could have a leading role in identifying and assessing future appointees. ----------------------------------------------------------------------------- I'd appreciate your feedback! It might be a bit too close to Thursday's council session, so I am not asking for an agenda item, but maybe we could have it under AOB or defer it to the GRC. Best regards Peter

2 1

May ccNSO Council Teleconference (229) | 21 May at 15:00 UTC
by ccNSO Calendar April 15, 2026

April 15, 2026

***TIME CHANGED TO 15:00 UTC*** Dear Council, The May ccNSO Council Teleconference (229) is scheduled for 21 May at 18:00 UTC. The agenda will be circulated prior to the call. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/96045201002?pwd=NN5YqkaXLm6UQOPQpR1ww4POCxKDDe.1 Meeting ID: 960 4520 1002 Passcode: ccNSO-0229 Wiki page: https://icann-community.atlassian.net/wiki/x/AYDaK Thank you!

1 0

Reminder | Call for presenters: ccTLD News ICANN86
by Joke Braeken April 15, 2026

April 15, 2026

Hello All, Here is a reminder about the possibility to apply for a speaking slot at the ICANN86 ccTLD News Sessions. Read more: https://www.icann.org/en/ccnso/news-and-announcements/documents/call-for-pr… Best, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> From: Joke Braeken <joke.braeken(a)icann.org> Date: Thursday, 9 April 2026 at 11:47 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org>, ccnso-council <ccnso-council(a)icann.org> Subject: Call for presenters: ccTLD News ICANN86 Call for presenters: ccTLD News ICANN86 9 April 2026 The ccNSO Meetings Programme Committee (MPC) invites proposals for the ccTLD News Session at the ICANN86 Policy Forum, held 8-11 June 2026 in Seville, Spain. This time, MPC considers organising 2 ccTLD News Sessions, thus offering slightly more speaking slots than usual. This session provides a platform for sharing updates, insights, and discussions on country code top-level domains (ccTLDs). Both in-person and virtual participation will be available, with simultaneous interpretation in English, French, and Spanish. Presentation Topics: Including, but not limited to: * Case studies on ccTLD initiatives * Collaboration & partnerships within the ccTLD community * Recent updates and developments in ccTLD operations * Policy & legislative impacts on ccTLDs * Best practices in registry management, marketing, and engagement Submission Guidelines: * Provide a title, abstract (a few sentences), presenter name, ccTLD affiliation, and contact details. * Submit by Friday, 1 May 2026 (23:59 UTC) via this submission link: https://forms.gle/ENqnekcz2haoM2cm6 Selection & Notifications: Proposals will be reviewed by the MPC, considering diversity and limited slots. Applicants will be notified latest by mid-May 2026. Selected presenters will receive a briefing and be invited to pre-session (21 May) and a rehearsal meeting (28 May). Why Present? * Showcase expertise and leadership in the ccTLD community * Engage with industry peers and stakeholders * Contribute to best practices and knowledge-sharing * Gain visibility for your ccTLD or initiative For inquiries, contact joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> The MPC looks forward to your proposals and an engaging session! Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Deadline extended | Call for one Volunteer: ccNSO participation in GNSO PDP on Associated Domain Check (DNS Abuse Mitigation PDP 1)
by Joke Braeken April 14, 2026

April 14, 2026

Dear All, The ccNSO Council has tasked the ccNSO DNS Abuse Standing Committee (DASC) with identifying one (1) additional volunteer to represent the ccNSO in the GNSO PDP on Associated Domain Check (DNS Abuse Mitigation PDP 1). The call for volunteers is still open. Please find more information, including detailed instructions on how to apply, here: https://www.icann.org/en/ccnso/news-and-announcements/documents/call-for-vo… Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Agenda and Draft resolutions meeting 228 | 16 April 2026 noon UTC
by Bart Boswinkel April 14, 2026

April 14, 2026

Dear all, Please find included the agenda and draft resolutions for the upcoming Council call. As follow-up from the previous Council meeting, voting will again be tested with Mentimeter. The details to join will be circulate closer to meeting in separate message. Kind regards, Bart AGENDA ccNSO Council meeting 228 Thursday, 16 April 2026 Table of contents Background and supporting documents 2<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> ADMINISTRATIVE MATTERS 2<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 1. Welcome 2<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 2. Relevant Correspondence 2<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> See: https://www.icann.org/en/ccnso/council/correspondence 2<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 3. Minutes & Action Items 2<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 4. Intermeeting decisions 3<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> UPDATES 3<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 6. Update ECA & CSC (written updates) 3<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 7. Update Working Groups (written updates or taken from the meeting) 3<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 8. Update Liaisons (written updates) 4<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 9. Progress Board Consideration ccPDP4-IDN & Implementation ccPDP3 4<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 10. Progress CCG Review of Reviews 4<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 11. New standing item: Update GNSO DNS Abuse Mitigation PDP1 4<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 12. Update Chair, Vice-chairs, Councillors, Regional Organisations, Secretariat 4<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> Informational 4<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> ADMINISTRATIVE MATTERS & DECISIONS 4<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 13. Approval Membership .es 4<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 14. Approval ccNSO Guideline Statement - and Conflict of Interest 4<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 15. Shadowing fellowship mentor 5<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 16. Appointments to committees or working groups, if any 5<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> SUBSTANTIVE MATTERS & DECISIONS 6<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 17. ICANN86 6<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 18. Any Other Business (AOB) 6<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 19. Next Council Meetings 6<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 20. Adjourn 6<https://docs.google.com/document/d/1bbeNZbp0-VVSuj2cv-HO01S1F8C6dKklt0om3SE…> 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 a. SOI updates Consult the ccNSO SOI Guideline<https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-2…> Complete the SOI template<https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQ…> Check the ccNSO Statements of Interest<https://community.icann.org/x/doAFEg> b. Meeting quorum 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 b. Action Items * 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 5. Triage Committee decisions since Council meeting 227 None 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 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 Informational 10. Progress CCG Review of Reviews Informational 11. New standing item: Update GNSO DNS Abuse Mitigation PDP1 Informational 12. Update Chair, Vice-chairs, Councillors, Regional Organisations, Secretariat Informational a. Update Chair b. Update secretariat 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. 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-partici…> 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-gener…> 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. 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. 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. SUBSTANTIVE MATTERS & DECISIONS 17. ICANN86 a. Draft Block Schedule b. Council meeting c. ccNSO Cocktail sponsorship 18. Any Other Business (AOB) 19. Next Council Meetings · 21 May 2026 | 15:00 UTC, Meeting 229. Note the changed time due to overlap with pre-ICANN86 policy webinar · 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

1 0

Please review: written updates
by Joke Braeken April 14, 2026

April 14, 2026

1 0