- Ccnso-council - lists.icann.org

NEW: A Preview of the ICANN86 Policy Forum
by ICANN Community Digest May 21, 2026

May 21, 2026

Email from ICANN Thursday, 21 May 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 ICANN86 Prep Week Schedule PRSP Pre-ICANN86 Briefing NEW: A Preview of the ICANN86 Policy Forum 2026 Round New gTLD Program: 2026 Round Opens Today ICANN Opens Second Application Period for the 2026 Round RSP Evaluation Program ICANN 2026 Round Application System User Guide, Support Model Available Webinars NEXT WEEK: ICANN to Host Question-and-Answer Sessions for New gTLD Applicants NEXT WEEK: Webinar Series on 2026 Round Objections and Appeals Processes 🚨 Action Items 🚨 NEXT WEEK: Call for Expressions of Interest: ICANN 2027 NomCom Chair and Chair-Elect ICANN Extends Deadline for Expressions of Interest: 2026 Round Independent Objectors ICANN Issues Request for Proposal: 2026 Round Auction ICANN Board Seeks Input on Additional Funds for 2026 Round Applicant Support Program ICANN Request for Proposal: 2026 Round Financial and Operational Evaluation ICANNWiki Seeking Volunteers Public Comment Additional Reference Label Generation Rules and Related Updates Events These events occur in May 2026. ICANN86 Prep Week Schedule PRSP Pre-ICANN86 Briefing ICANN86 Policy Outlook Report NEW: A Preview of the ICANN86 Policy Forum Thank you for making the considerable commitment of time and effort to attend ICANN86, either in person or remotely. Whether you are a longtime ICANN community member, an occasional contributor, or joining us for the first time, I encourage you to take an active role. Read more. 2026 Round New gTLD Program: 2026 Round Opens Today New gTLDs have demonstrated their benefits in building brand trust, creating vibrant local digital ecosystems, and providing more intuitive navigation for users. 2026 Round Launch Page Press Release Announcement ICANN Opens Second Application Period for the 2026 Round RSP Evaluation Program The second application period for the RSP Evaluation Program runs from 30 April to 12 August 2026. Read more. ICANN 2026 Round Application System User Guide, Support Model Available ICANN has made several resources available to help prospective applicants familiarize themselves with ICANN's TLD Application Management System (TAMS). This online system will be used by all applicants, evaluation panelists, and ICANN staff to submit, manage, and process new gTLD applications. These resources are available to help prospective applicants prepare for the application completion and submission process through TAMS: System user guide Frequently Asked Questions Demo videos Q&A webinar recordings Read more. Webinars NEXT WEEK: ICANN to Host Question-and-Answer Sessions for New gTLD Applicants Date: 26 May, 16:00 UTC Read more and register. NEXT WEEK: Webinar Series on 2026 Round Objections and Appeals Processes Introduction: 26 May, 06:00 UTC WIPO, Dispute Resolution Service Provider: 27 May, 06:00 UTC International Chamber of Commerce, Dispute Resolution Service Provider: 28 May, 06:00 UTC Read more and register. Action Items NEXT WEEK: Call for Expressions of Interest: ICANN 2027 NomCom Chair and Chair-Elect The Chair position blends time management and negotiation skills with the practical aspects of conducting a worldwide search for individuals to fill various ICANN leadership positions. Deadline: 29 May 2026 Read more. ICANN Extends Deadline for Expressions of Interest: 2026 Round Independent Objectors The Independent Objectors will file Community and Limited Public Interest objections and appeals, and participate in mediation, where appropriate. Deadline: 01 June 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: 02 June 2026 Read more. ICANN Request for Proposal: 2026 Round Financial and Operational Evaluation The Financial and Operational Evaluation occurs during the applicant evaluation phase of the New gTLD Program, expected to begin in Q3 2027. Deadline: 12 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 Additional Reference Label Generation Rules and Related Updates Submissions Opening Date: Tuesday, 12 May 2026 Submissions Closing Date: Tuesday, 23 June 2026 See upcoming proceedings. See other public consultations. Events These events occur in May 2026. To learn more, please visit our community engagement calendar. RIPE 92 DNSSEC workshop in Yamoussokro, Cote d'Ivoire Africa Tech Policy Summit Nordic Domain Days LACNIC 45 Fórum da Internet do Brasil ITU Regional Development Forum and the Second Africa Preparatory Meeting (APM) for the 2026 ITU Plenipotentiary Conference (PP-26). 2026 Round Objections and Appeals Processes - ICANN hosts 2 of 2 Volume 8, Issue 36 | Archive | Next Issue: Monday, 25 May 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

ICANN Ombuds announced the first Service Quality Survey
by Joke Braeken May 21, 2026

May 21, 2026

All, The ICANN Ombuds announced the first Service Quality Survey, to use community input to strengthen and improve the Ombuds Office. Read more: * March blog<https://www.icann.org/en/blogs/details/you-said-we-listened-public-comment-…> * Announcement: https://www.icann.org/en/blogs/details/helping-the-ombuds-office-learn-and-… Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> ccNSO at ICANN86: https://www.icann.org/en/ccnso/meetings

1 0

NOTES ccNSO Council meeting 229 Thursday, 21 May 2026 | 13:00 UTC
by Joke Braeken May 21, 2026

May 21, 2026

NOTES ccNSO Council meeting 229 Thursday, 21 May 2026 | 13:00 UTC 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 Alejandra: Welcome all to the Council meeting. Please identify yourself in zoom (screen name), for easy identification in voting Wiki page: https://icann-community.atlassian.net/wiki/x/AYDaK Any AOB we should be aware of? none 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 asks if there are any updates to the SOI we should be aware of. No hands raised. Jordan in chat: I updated mine but you all know what that’s about (my SoI / employer change) b. Meeting quorum Claudia: apologies from Chris Disspain You are quorate 2. Relevant Correspondence See: https://www.icann.org/en/ccnso/council/correspondence · Request for input Co-Chair’s draft Review of Review · Response Council to request for input Note: We have some relevant correspondence since our last meeting. To be discussed later. 3. Minutes & Action Items a. Minutes Meeting 228 Circulated to the Council mailing list on 6 May 2026 Any questions? If none, Minutes are confirmed! b. Action Items All due action items are completed, any questions? * Action Item 228-01 The Secretariat is asked to launch a call for volunteers for a new member to the Planning Prioritization Process group. (Completed, see item 15) * Action Item 228-02 The Chair of the ccNSO is requested to formally welcome the RED.ES as a member. (Completed) * Action item 228-03 The secretariat is requested to publish the membership approval of RED.ES, the ccTLD Manager of .es. (Completed) * Action item 228-04 The secretariat is requested to publish the adoption of the ccNSO Guideline Statement and Conflict of Interest. * Action item 228-05 The secretariat is requested to inform the leadership team of the IGLC and persons appointed and enable their participation in the respective teams. (Completed) * Action Item 228-06 The Secretariat to send a calendar invite for the ICANN86 Council prep call. (Completed) * Action Item 228-07 The Triage committee to evaluate the proposal of defining and establishing a small group of councillors to act as a sounding board for ccNSO-appointed liaisons to technical groups (CSC, RZERC, IFR, future RSS Governance Council, etc.), including agreeing on its structure, scope, and level of informality, and exploring whether it should also support the identification and assessment of future appointees (To be scheduled). 4. Intermeeting decisions since meeting 228 (April 2026) a. Approval comments on the Co-Chair’s Review of Reviews Refined Outline We have taken one decision 5. Triage Committee decisions since Council meeting 228 The Triage committee has reviewed 3 requests for action with following decisions: · Not to take action on request to expression for interest in becoming chair and chair-elect for the 2027 NomCom · Referred action on Approval Action and Rejection Action to the Rejection and Approval Action manager · Secretariat to alert community members to respond to survey ICANN’s Ombuds, if they received the Survey. Bart: change in procedure. Decision by Triage will stand. Charter still needs to be updated. Changed mandate for the Triage Committee Peter: further discussion Bart: change itself will be documented. Is already in its mandate Peter: can Triage decide by themselves Bart: the mandate to take certain decisions. The decisions you see here were already in the mandate of the Triage Committee. Peter: ok. Let’s take that offline. UPDATES Joke: not much has changed in the written updates themself. But display in agenda did change. Idea is to give monthly overview of current status, next steps, what it is about. Councillors like it 6. Written updates <https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/10841066…> If any - since meeting 228 from the following groups can also be found on the wiki space for this meeting. Governance Groups: * ECA * CSC * RZERC * Planning Prioritization Process * RSS GWG (Dormant) Liaisons: * ccNSO Liaison to ALAC * ccNSO Liaison to GNSO Council ccNSO WG and Committees: * ccPDP4-IDN (Dormant) * DASC * GRC * IGLC * MPC * OMC * SOPC * Tech WG * TLD-OPS SC * UAC 7. Progress Board Consideration ccPDP4-IDN & Implementation ccPDP3 Informational Bart: caucus will meet again. Detailed assessment of the pdp (all 14 sections of the policy) will then be completed. Checking on implementability and risk. The caucus will discuss 4 potential questions for the ccNSO, to clarify language in the policy, and confirm implementation. Follows the pattern around the questions of the review mechanism. Only 4 questions. And not 40, like was the case with ccPDP3-RM. The detailed assessment by staff and the presentation of that assessment to caucus is foreseen to be completed next week. It will then go for consideration to the full board. Alejandra: only 4 questions is good. Let’s create a small team to answer those questions. 8. Progress CCG Review of Reviews Informational Although also included in written updates, Alejandra provides information on the planning the next weeks (Seville and beyond, public comment) 9. Update GNSO DNS Abuse Mitigation PDP1 Nick was elected Vice Chair. ccNSO representatives appointed to this effort: * Member: Eberhard Lisse (.na) | AF * Member: Nick Wenban-Smith (.uk) | EU * Member: Diego Ernesto Luna-Quevedo (.co) | LAC * Alternate: Bruce Tonkin (.au) | AP * Participant: Mira Fajriyah (.id) | AP 10. Update Chair, Vice-chairs, Councillors, Regional Organisations, Secretariat Informational a. Update Chair i.Update on Jordan's confirmation on the council after change of affiliation Alejandra: Report that No objections from AP region re Jordan’s continuation as Councillor. Jordan: please with the support. No objections raised. I will keep working. Congratulations to Jordan expressed in zoom via reactions and chat ii. 1-on-1 meeting with ICANN’s CEO and President Alejandra: Note meeting was deferred due to personal reasons from Kurtis. To be rescheduled. Alejandra gives overview of topics at SO/AC Roundtable in Seville * How we meet: Status check * Review of Reviews: Status check with the RoR Leadership * Where are we in the timeline? * Are we achieving the goals set in the Charter? * Will an extension of time be necessary? * DNSABUSE PDP1: Status check with the PDP Leadership * Interesting topic This is a proposal on how to get things done faster in ICANN, is it working? * Debrief on the Board’s prep week session re: Code of Conduct * Are there action items or areas that would benefit from work by the SOAC leaders? * Are there action items or areas that would benefit from work by the Org or Board? * What are the next steps? * Tour de table to share our priorities/focuses for the ICANN Meeting b. Update Vice-chairs, Councillors, Regional Organizations, Secretariat, if any Everton: just to let you know .br joined CENTR last year, and first time we attended CENTR events was at jamboree LACTLD will hold workshop next week Alejandra: we were asked to present on study group progress and next steps at lactld workshop Jordan: People may be interested also to know that APTLD will meet in Australia, slated for February 2027 ADMINISTRATIVE MATTERS & DECISIONS 11. Adoption ccNSO Board Director Removal, NomCom Board Director Removal and Board Recall Guidelines The ccNSO Guideline Review Committee has prepared a draft Guideline to detail the role and responsibilities of the ccNSO as one of the five Decisional Participants with respect to the removal of ccNSO appointed Board member(s), NomCom appointed Board member(s) and recall of the full Board. The Guidelines were circulated to Council and members of the ccNSO to review, and no changes were proposed. Sean: glad there was no critical feedback. Diagrams have been added. Hope the guideline is now a lot easier to understand, and the process easier to follow. No questions Move? Pablo Second? Wafa Questions on the decision? None Draft Resolution Background The ccNSO Guideline Review Committee has prepared a draft Guideline to detail the role and responsibilities of the ccNSO as one of the five Decisional Participants with respect to the removal of ccNSO appointed Board member(s) and NomCom appointed Board member(s) and recall of the full Board. The Guidelines were circulated to Council and members of the ccNSO to review, and no changes were proposed. Decision The ccNSO adopts the Guidelines with respect to the ccNSO Board Director Removal, NomCom Board Director Removal and Board Recall as proposed by the ccNSO GRC. The secretariat is requested to post the Guidelines on the ccNSO website and publish this decision as soon as possible. This decision becomes effective 7 days after publication. 12. From the Triage Committee a. Update Triage Process Bart: more to follow in Seville b. ccNSO Portfolio of Activities i.Quarterly Monitor ccNSO Portfolio Informational Bart: updated workplan. Introduced to community in Seville. DR SG will not meet the original deadline of the Seville meeting. Both study groups aim to finalise the final reports by ICANN87. Both SG will provide an update in Seville. The GRC has been very active. The board nomination process guideline for adoption by Seville or latest Mid-July. They made progress on the implementation of the CIP. that had an impact on the quarterly monitor. No questions on the quarterly monitor. To-Do for secretariat: post may 26 monitor and replace the February monitor ii. Update ccNSO Work plan: FY27- FY28 Portfolio of Activities Informational Triage started looking at ClickUp What still needs to be done: Bart to propose the balance between workload and capacity. First to be discussed by Triage. Will be on your plate at ICANN86. The CIP will need to be implemented. Starts in July. will take effort by GRC and staff. Bart: issues as of 1 October, when he retires, for at least 6 months, the secretariat will need to reorganise. If 1/3rd of the secretariat is gone. Will have an impact on current initiatives, but definitely regarding new initiatives. Suggestion to wait launching new initiatives. Thus, pause the committee reviews, and the launch of new study groups. Allow the new secretariat to find new footing and get adjusted. 13. Launch call for volunteers for a ccNSO appointee to the NomCom Draft Resolution Background The ccNSO Council was informed that the ccNSO NomCom appointee (Eyitayo Iortim) second one-year term ends in July 2026, and is therefore not eligible to be re-appointed. Questions about the topic? Mover? Charles Seconder? Wafa Decision The ccNSO Council requests the secretariat to launch a call for expression of interest before ICANN86, in accordance with section 4 and 8 of the Guideline: ccNSO Appointment Procedures<https://ccnso.icann.org/sites/default/files/field-attached/guidelines-ccnso…> and including the requirements for a ccNSO NomCom appointee, to serve on the NomCom, preferably for two 1-year terms. The Council requests the secretariat to publish this decision as soon as possible. This decision becomes effective on publication. Questions about the decision? none Vote. only green marks in zoom. approved. 14. Re-consideration scheduled start time Council calls Considering the current timezones in which Councillors live, it is proposed that starting with meeting 231, all Council calls will all start at 13:00 UTC (6:00am for Sean and 9:00pm for Jiankang) Peter: understand the considerations. During my working day. Likelihood with collisions is thus raising. There might be more apologies. Alejandra: noted. Let’s try, and see how it works. Can adjust later. Calendar invites will be changed for all meetings post ICANN86. 15. Appointments to committees or working groups, if any · Luis Diego Espinoza, vice-chair (.na) Tech WG · Irina Danelia (.ru, vice-chair SOPC) and Charles Noir (.ca, member of Triage Committee) as member and alternate Planning Prioritization Process Group · Grace Mwikarago Ingabire to MPC Questions about the topic? none Mover? Pablo Seconder? Wafa For Decision Draft resolution Decision First, as required under its Charter the Tech WG has nominated Luis Diego Espinoza (.na) as Vice-Chair of the Tech WG. Following the nomination the ccNSO Council appoints Luis Diego Espinoza (.na) as Vice-Chair of the Tech WG. Secondly, at the request of ICANN’s planning team, the ccNSO Council appoints Irina Danelia as member and Charles Noir as alternate of the ICANN Planning Prioritization Process Group. Thirdly, the ccNSO Council appoints Grace Mwikarago (.rw) as member of the MPC. The Secretariat is requested to inform the Tech WG, ICANN Planning, the MPC and the candidates accordingly and publish this decision as soon as possible. This decision becomes effective upon publication. Charles: should i abstain, as being part of the decision? Alejandra: ok Charles: I abstain. No other abstentions, no other objections. Biyi: we have 3 decisions to take. Charles is affected by just one of the 3. But he abstains from all 3. Bart: In the past, each decision was separate. At request of council those decisions were combined for efficiency reasons Personal assessment on when to abstain. In future, we could separate the decisions out, whenever there is a councillor involved? Pragmatic decision in the past. Everton: in this case add a note to the decision. Abstain from the affected decision, but not the others? As a quick solution. Sean: On an omnibus issue that I abstain from, I will note my support of the others; it puts it in the record without asking for separation. As Bart says, its personal preference Nigel: COI. there is no conflict here. Down to the individual to decide. There are extremely clear-cut cases. Sean: COI training I took here in Canada. Have a different experience. I chose to abstain when there is a GRC decision. Bart: regarding Nigel’s point. The SOI guideline also includes info about potential COI of Councillors. In case the situation Nigel alluded to arises. Biyi: interesting to look at the balance between being efficient and correct. Agree with Sean and Everton. Pablo: if you abstain, assume it refers to the part that affects you. Alejandra: complicated. Better to keep decisions separated. Abstain and object is not the same Bart: suggestion to record in the minutes the motivation for abstention. If we separate the decisions again, it will be complicated. Depends on whether a councillor is involved. Also depends on personal preference of the councillor, and your own background. This is not about COI, but about personal preference. Just record in minutes what you support, what you abstain. Jordan: We have already spent more time on this than its importance demands, but an easy solution is to propose each decision/person as a separate resolution, but the Chair can generally move them as a block, if you want to be absolutely beyond doubt. I don’t mind any sort of approach at all. Basically - “if you are abstaining, say why for the record” SUBSTANTIVE MATTERS & DECISIONS 16. Introduction updated Board Nomination Guideline Informational As you may recall we asked the GRC to review and update the Board Nomination Guideline to include the recommendations from the Nomination Process manager and to align the text of this Guideline with the latest version of the Council Election Guideline. As you will also know, in the July/August timeframe we will need to launch the next cycle of the Board Seat Nomination Process. So the goal is to have this Guideline approved by mid-July by Council. Today Sean will introduce major changes, and then following today’s meeting you are requested to review the updated guideline. Closing date will be 29 May, to provide the GRC an opportunity to adjust the draft if you have any comments, before consulting the membership Sean: main changes * Better definitions * Better alignment across the election process with council selection * Responsibilities are clearer now. Easier for Council. Please review the language. Important for us as Council and the community. Process to be fair to anyone. Any questions? None Alejandra: deadline for comments is 29 may. Please write to GRC. eventually will be circalted to membership, and then back to council for approval 17. Update ICANN86 a. Prep call Alejandra: Thursday 13.00 UTC: to discuss * assigning rapporteurs and * update FY 27-28 Portfolio, and * other business Biyi: public holiday in Nigeria Alejandra: will be recorded. Also a holiday for Wafa and Sami. major Muslim holiday. b. Council meeting Topics: * Conditional Approval CSC Charter * Timeline Approval Action c. Block Schedule Claudia: no changes compared to last time you saw this Joke: ccNSO at ICANN86: https://www.icann.org/en/ccnso/meetings The detailed agendas, speaker list etc are available on the wiki. Also, you can download the block schedule there Alejandra: Thursday, block 1 community forum Jordan: Thursday work sessions are rather for the committee. Observers are welcome. Claudia: Thursday meetings will be in smaller rooms 18. Any Other Business (AOB) none 19. Next Council Meetings · 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 Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> ccNSO at ICANN86: https://www.icann.org/en/ccnso/meetings

1 0

Re: May ccNSO Council Teleconference (229) | 21 May at 13:00 UTC
by Alejandra Reynoso Barral May 21, 2026

May 21, 2026

Dear Councillors The time for our council call today is at 13:00 UTC. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Thu, 21 May 2026, 08:31 Nigel Roberts, <nigel(a)channelisles.net> wrote: > The invite is for 1300z but the text says 1800z > > Confirm it's the former, as in the calendar item?? > > On 5/21/26 07:02, ccNSO Calendar wrote: > > ***REMINDER*** > > > > 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 <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 <https:// > > icann-community.atlassian.net/wiki/x/AYDaK> > > > > Thank you! > > > > ccNSO Calendar has invited you to May ccNSO Council Teleconference (229) > > | 21 May at 13:00 UTC > > Title: May ccNSO Council Teleconference (229) | 21 May at 13:00 > UTC > > Location: https://icann.zoom.us/j/96045201002? > > pwd=NN5YqkaXLm6UQOPQpR1ww4POCxKDDe.1 > > When: Thursday, May 21, 2026, 14:00 – 15:30 > > > > > > Organizer: > > ccNSO Calendar <ccnso-calendar(a)icann.org> > > Description: > > ***REMINDER*** > > > > 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! > > > > > > > > Attendees: > > > > * > > ccNSO Council <ccnso-council(a)icann.org> > > * > > Nacho Amadoz <nacho(a)amadoz.cat> > > * > > Charles Noir <Charles.Noir(a)cira.ca> > > * > > Grace INGABIRE <grace.i(a)ricta.org.rw> > > * > > Sami Mohamed Ali <sali(a)tra.org.bh> > > * > > Chris Disspain <chris.disspain(a)identity.digital> > > * > > Jenifer Lopez <jenifer.lopez(a)utp.ac.pa> > > * > > Barrack Otieno <otieno.barrack(a)gmail.com> > > * > > Jordan Carter <jordan.carter(a)auda.org.au> > > * > > Biyi Oladipo <biyioladipo(a)gmail.com> > > * > > Peter Van Roste <peter(a)centr.org> > > * > > Joke Braeken <joke.braeken(a)icann.org> > > * > > wafa Dahmani <wafatn7604(a)gmail.com> > > * > > Alejandra Reynoso Barral <alejandra.reynoso(a)gmail.com> > > * > > Olga Cavalli <olgacavalli(a)gmail.com> > > * > > Pablo Rodriguez <pablor1961(a)gmail.com> > > * > > Patricio Poblete <patricio.poblete(a)gmail.com> > > * > > ALI Hadji Mmadi <alihadji90(a)gmail.com> > > * > > Everton - Assessoria > > < > fca73f59dbfa7813b46ac3024b8130ef009be883000aaceaead5f7d53464de2f(a)group.calendar.google.com > > > > * > > Laura Margolis <margolisl(a)gmail.com> > > * > > Jordan Carter <jordan(a)jordancarter.org.nz> > > * > > Kenechukwu Okekenta <kavtech1(a)gmail.com> > > * > > David Inem, FNSIG, MNCS <inemdavid(a)gmail.com> > > * > > Jordan Carter <Jordan.Carter(a)nominet.uk> > > * > > Nigel Roberts <nigel(a)channelisles.net> > > * > > Claudia Ruiz <claudia.ruiz(a)icann.org> > > > > > > > > -- > Dr Nigel Roberts BSc LLB CEng CITP FBCS FRSA, Director > CHANNELISLES.NET, Maison Postel, Ollivier St, Alderney GY9 3TD > +44 1481 822800 (office) or +44 20 7100 4319 (direct line) > +44 7973 263842 (mobile) nigel(a)channelisles.net > >

1 0

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

May 21, 2026

***REMINDER*** 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

Draft Agenda Meeting 229 - Thursday 21 May 2026 at 13:00 UTC
by Claudia Ruiz May 21, 2026

May 21, 2026

Dear all, Please find included the draft agenda for the upcoming Council meeting #229. Kind regards, Claudia Ruiz *********************************************************************************** AGENDA ccNSO Council meeting 229 Thursday, 21 May 2026 | 13:00 UTC Background and supporting documents 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> ADMINISTRATIVE MATTERS 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 1. Welcome 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> a. SOI updates 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> b. Meeting quorum 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 2. Relevant Correspondence 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 3. Minutes & Action Items 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> a. Minutes Meeting 228 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> b. Action Items 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 4. Intermeeting decisions since meeting 228 (April 2026) 3<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 5. Triage Committee decisions since Council meeting 228 3<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> UPDATES 3<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 6. Written updates 3<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 7. Progress Board Consideration ccPDP4-IDN & Implementation ccPDP3 3<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 8. Progress CCG Review of Reviews 3<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 9. Update GNSO DNS Abuse Mitigation PDP1 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 10. Update Chair, Vice-chairs, Councillors, Regional Organizations, Secretariat 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> a. Update Chair 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> b. Update Vice-chairs, Councillors, Regional Organizations, Secretariat, if any 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> ADMINISTRATIVE MATTERS & DECISIONS 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 11. Adoption ccNSO Board Director Removal, NomCom Board Director Removal and Board Recall Guidelines 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 12. From the Triage Committee 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> a. Update Triage Process 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> b. ccNSO Portfolio of Activities 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 13. Launch call for volunteers for a ccNSO appointee to the NomCom 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 14. Re-consideration scheduled start time Council calls 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 15. Appointments to committees or working groups, if any 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> ● Luis Diego Espinoza, vice-chair (.na) Tech WG 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> SUBSTANTIVE MATTERS & DECISIONS 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 16. Introduction updated Board Nomination Guideline 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 17. Update ICANN86 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> a. Prep call 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> b. Council meeting 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> c. Block Schedule 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 18. Any Other Business (AOB) 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 19. Next Council Meetings 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 20. Adjourn 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 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 Complete the SOI template Check the ccNSO Statements of Interest b. Meeting quorum 2. Relevant Correspondence See: https://www.icann.org/en/ccnso/council/correspondence * Request for input Co-Chair’s draft Review of Review * Response Council to request for input 3. Minutes & Action Items a. Minutes Meeting 228 Circulated to the Council mailing list on 6 May 2026 b. Action Items * Action Item 228-01 The Secretariat is asked to launch a call for volunteers for a new member to the Planning Prioritization Process group. (Ongoing) * Action Item 228-02 The Chair of the ccNSO is requested to formally welcome the RED.ES as a member. (Completed) * Action item 228-03 The secretariat is requested to publish the membership approval of RED.ES, the ccTLD Manager of .es. (Completed) * Action item 228-04 The secretariat is requested to publish the adoption of the ccNSO Guideline Statement and Conflict of Interest. * Action item 228-05 The secretariat is requested to inform the leadership team of the IGLC and persons appointed and enable their participation in the respective teams. (Completed) * Action Item 228-06 The Secretariat to send a calendar invite for the ICANN86 Council prep call.(Completed) * Action Item 228-07 The Triage committee to evaluate the proposal of defining and establishing a small group of councillors to act as a sounding board for ccNSO-appointed liaisons to technical groups (CSC, RZERC, IFR, future RSS Governance Council, etc.), including agreeing on its structure, scope, and level of informality, and exploring whether it should also support the identification and assessment of future appointees (To be scheduled). 4. Intermeeting decisions since meeting 228 (April 2026) a. Comments to the Review of Reviews Refined Outline 5. Triage Committee decisions since Council meeting 228 UPDATES 6. Written updates If any - since meeting 228 from the following groups can also be found on the wiki space for this meeting. Governance Groups: * ECA * CSC * RZERC * Planning Prioritization Process * RSS GWG (Dormant) Liaisons: * ccNSO Liaison to ALAC * ccNSO Liaison to GNSO Council ccNSO WG and Committees: * ccPDP4-IDN (Dormant) * DASC * GRC * IGLC * MPC * OMC * SOPC * Tech WG * TLD-OPS SC * UAC 7. Progress Board Consideration ccPDP4-IDN & Implementation ccPDP3 Informational 8. Progress CCG Review of Reviews Informational 9. Update GNSO DNS Abuse Mitigation PDP1 Informational 10. Update Chair, Vice-chairs, Councillors, Regional Organisations, Secretariat Informational a. Update Chair i. Update on Jordan's confirmation on the council after change of affiliation ii. 1-on-1 meeting with ICANN’s CEO and President b. Update Vice-chairs, Councillors, Regional Organizations, Secretariat, if any ADMINISTRATIVE MATTERS & DECISIONS 11. Adoption ccNSO Board Director Removal, NomCom Board Director Removal and Board Recall Guidelines For Decision 12. From the Triage Committee a. Update Triage Process b. ccNSO Portfolio of Activities i. Quarterly Monitor ccNSO Portfolio Informational ii. Update ccNSO Work plan: FY27- FY28 Portfolio of Activities Informational 13. Launch call for volunteers for a ccNSO appointee to the NomCom 14. Re-consideration scheduled start time Council calls For decision Considering the current timezones in which Councillors live, it is proposed that starting with meeting 231, all Council calls will all start at 13:00 UTC (6:00am for Sean and 9:00pm for Jiankang) 15. Appointments to committees or working groups, if any * Luis Diego Espinoza, vice-chair (.na) Tech WG For Decision SUBSTANTIVE MATTERS & DECISIONS 16. Introduction updated Board Nomination Guideline Informational 17. Update ICANN86 a. Prep call b. Council meeting c. Block Schedule 18. Any Other Business (AOB) 19. Next Council Meetings * 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

3 2

Agenda and Resolutions meeting 229 - Background material
by Bart Boswinkel May 20, 2026

May 20, 2026

Dear all, Please find included the Agenda and Draft Resolutions Council meeting 229 In addition – background material * For item 11 Guidelines Board Recall, and ccNSO & NomCom Director Removal (3 documents ) These documents were already circulated for your review a few weeks ago and have also been circulated to the Members. The GRC has not received any comments, and no further updates have been made. * For Item 16 – Update Guideline Board Nomination Process. At the meeting Sean as chair of the GRC will introduce the changes * Quarterly Monitor May 2026. Kind regards, Bart ---------- AGENDA & Draft Resolutions ccNSO Council meeting 229 Thursday, 21 May 2026 | 13:00 UTC Background and supporting documents 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> ADMINISTRATIVE MATTERS 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 1. Welcome 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> a. SOI updates 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> b. Meeting quorum 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 2. Relevant Correspondence 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 3. Minutes & Action Items 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> a. Minutes Meeting 228 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> b. Action Items 2<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 4. Intermeeting decisions since meeting 228 (April 2026) 3<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 5. Triage Committee decisions since Council meeting 228 3<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> UPDATES 3<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 6. Written updates 3<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 7. Progress Board Consideration ccPDP4-IDN & Implementation ccPDP3 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 8. Progress CCG Review of Reviews 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 9. Update GNSO DNS Abuse Mitigation PDP1 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 10. Update Chair, Vice-chairs, Councillors, Regional Organisations, Secretariat 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> a. Update Chair 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> b. Update Vice-chairs, Councillors, Regional Organizations, Secretariat, if any 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> ADMINISTRATIVE MATTERS & DECISIONS 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 11. Adoption ccNSO Board Director Removal, NomCom Board Director Removal and Board Recall Guidelines 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 12. From the Triage Committee 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> a. Update Triage Process 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> b. ccNSO Portfolio of Activities 4<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 13. Launch call for volunteers for a ccNSO appointee to the NomCom 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 14. Re-consideration scheduled start time Council calls 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 15. Appointments to committees or working groups, if any 5<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> SUBSTANTIVE MATTERS & DECISIONS 6<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 16. Introduction updated Board Nomination Guideline 6<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 17. Update ICANN86 6<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> a. Prep call 6<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> b. Council meeting 6<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> c. Block Schedule 6<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 18. Any Other Business (AOB) 6<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 19. Next Council Meetings 6<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 20. Adjourn 6<https://docs.google.com/document/d/1Gp5lu3cCZL7rd5_RiDAG-S7NtGec0wgGsrIXQG3…> 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 · Request for input Co-Chair’s draft Review of Review · Response Council to request for input 3. Minutes & Action Items a. Minutes Meeting 228 Circulated to the Council mailing list on 6 May 2026 b. Action Items * Action Item 228-01 The Secretariat is asked to launch a call for volunteers for a new member to the Planning Prioritization Process group. (Completed, see item 15) * Action Item 228-02 The Chair of the ccNSO is requested to formally welcome the RED.ES as a member. (Completed) * Action item 228-03 The secretariat is requested to publish the membership approval of RED.ES, the ccTLD Manager of .es. (Completed) * Action item 228-04 The secretariat is requested to publish the adoption of the ccNSO Guideline Statement and Conflict of Interest. * Action item 228-05 The secretariat is requested to inform the leadership team of the IGLC and persons appointed and enable their participation in the respective teams. (Completed) * Action Item 228-06 The Secretariat to send a calendar invite for the ICANN86 Council prep call. (Completed) * Action Item 228-07 The Triage committee to evaluate the proposal of defining and establishing a small group of councillors to act as a sounding board for ccNSO-appointed liaisons to technical groups (CSC, RZERC, IFR, future RSS Governance Council, etc.), including agreeing on its structure, scope, and level of informality, and exploring whether it should also support the identification and assessment of future appointees (To be scheduled). 4. Intermeeting decisions since meeting 228 (April 2026) a. Comments to the Co-Chair’s Review of Reviews Refined Outline 5. Triage Committee decisions since Council meeting 228 The Triage committee has reviewed 3 requests for action with following decisions: · Not to take action on request to expression for interest in becoming chair and chair-elect for the 2027 NomCom · Referred action on Approval Action and Rejection Action to the Rejection and Approval Action manager · Secretariat to alert community members to respond to survey ICANN’s Ombuds, if they received the Survey. UPDATES 6. Written updates <https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/10841066…> If any - since meeting 228 from the following groups can also be found on the wiki space for this meeting. Governance Groups: * ECA * CSC * RZERC * Planning Prioritization Process * RSS GWG (Dormant) Liaisons: * ccNSO Liaison to ALAC * ccNSO Liaison to GNSO Council ccNSO WG and Committees: * ccPDP4-IDN (Dormant) * DASC * GRC * IGLC * MPC * OMC * SOPC * Tech WG * TLD-OPS SC * UAC 7. Progress Board Consideration ccPDP4-IDN & Implementation ccPDP3 Informational 8. Progress CCG Review of Reviews Informational 9. Update GNSO DNS Abuse Mitigation PDP1 Informational 10. Update Chair, Vice-chairs, Councillors, Regional Organisations, Secretariat Informational a. Update Chair i.Update on Jordan's confirmation on the council after change of affiliation ii.1-on-1 meeting with ICANN’s CEO and President b. Update Vice-chairs, Councillors, Regional Organizations, Secretariat, if any ADMINISTRATIVE MATTERS & DECISIONS 11. Adoption ccNSO Board Director Removal, NomCom Board Director Removal and Board Recall Guidelines For Decision Draft Resolution Background The ccNSO Guideline Review Committee has prepared a draft Guideline to detail the role and responsibilities of the ccNSO as one of the five Decisional Participants with respect to the removal of ccNSO appointed Board member(s) and NomCom appointed Board member(s) and recall of the full Board. The Guidelines were circulated to Council and members of the ccNSO to review, and no changes were proposed. Decision The ccNSO adopts the Guidelines with respect to the ccNSO Board Director Removal, NomCom Board Director Removal and Board Recall as proposed by the ccNSO GRC. The secretariat is requested to post the Guidelines on the ccNSO website and publish this decision as soon as possible. This decision becomes effective 7 days after publication. 12. From the Triage Committee a. Update Triage Process b. ccNSO Portfolio of Activities i.Quarterly Monitor ccNSO Portfolio Informational ii. Update ccNSO Work plan: FY27- FY28 Portfolio of Activities Informational 13. Launch call for volunteers for a ccNSO appointee to the NomCom Draft Resolution Background The ccNSO Council was informed that the ccNSO NomCom appointee (Eyitayo Iortim) second one-year term ends in July 2026, and is therefore not eligible to be re-appointed. Decision The ccNSO Council requests the secretariat to launch a call for expression of interest before ICANN86, in accordance with section 4 and 8 of the Guideline: ccNSO Appointment Procedures<https://ccnso.icann.org/sites/default/files/field-attached/guidelines-ccnso…> and including the requirements for a ccNSO NomCom appointee, to serve on the NomCom, preferably for two 1-year terms. The Council requests the secretariat to publish this decision as soon as possible. This decision becomes effective on publication. 14. Re-consideration scheduled start time Council calls For decision Considering the current timezones in which Councillors live, it is proposed that starting with meeting 231, all Council calls will all start at 13:00 UTC (6:00am for Sean and 9:00pm for Jiankang) 15. Appointments to committees or working groups, if any · Luis Diego Espinoza, vice-chair (.na) Tech WG · Irina Danelia (.ru, vice-chair SOPC) and Charles Noir (.ca, member of Triage Committee) as member and alternate Planning Prioritization Process Group For Decision Draft resolution Decision First, as required under its Charter the Tech WG has nominated Luis Diego Espinoza (.na) as Vice-Chair of the Tech WG. Following the nomination the ccNSO Council appoints Luis Diego Espinoza (.na) as Vice-Chair of the Tech WG. Secondly, at the request of ICANN’s planning team, the ccNSO Council appoints Irina Danelia as member and Charles Noir as alternate of the ICANN Planning Prioritization Process Group The Secretariat is requested to inform the Tech WG and ICANN Planning and the candidates accordingly and publish this decision as soon as possible. This decision becomes effective upon publication. SUBSTANTIVE MATTERS & DECISIONS 16. Introduction updated Board Nomination Guideline Informational 17. Update ICANN86 a. Prep call b. Council meeting c. Block Schedule 18. Any Other Business (AOB) 19. Next Council Meetings · 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

2 1

ccNSO travel support for ICANN87
by Joke Braeken May 19, 2026

May 19, 2026

Dear All, I have contacted you regarding the ccNSO travel support for ICANN87. The meeting is currently scheduled to be held 7–22 October 2026 in Muscat, Oman. To determine the distribution of the ccNSO slots, your action is required by Friday, 29 May 2026 (23:59 UTC). Instructions and background information are included below. Thank you. Best, Joke = = = INSTRUCTIONS | Each region has three (3) Councillors, but only one (1) fully funded slot is available per region. Please coordinate with the other two Councillors from your region to agree on how this slot will be allocated. NomCom-appointed Councillors each have a slot at their disposal Submit responses to: ccnsosecretariat(a)icann.org<mailto:ccnsosecretariat@icann.org> by 29 May 2026 (23:59 UTC). Please answer the two questions below: Q1. Which Councillor(s) from your region will receive funding? Q2. What type of funding will be provided? Choose one option below: * Option 1: Full funding – airfare, accommodation, and per diem * Option 2: Partial funding – airfare only (no accommodation, no per diem) * Option 3: Partial funding – accommodation and per diem only (no airfare) Notes: If one Councillor receives full funding, submit only 1 name. If the funding is split, submit 2 names and clearly indicate which Councillor receives Option 2 and which receives Option 3. WHAT IS INCLUDED | ccNSO travel funding covers an economy class return ticket to the travel destination, the hotel costs for the time of the meeting and a per diem. (Either full or partial funding). BACKGROUND | The ccNSO has 17 full travel slots for ICANN87, of which 8 are allocated to the Council. According to the applicable guideline (section 5.1): Three (3) travel slots are reserved for the NomCom-appointed ccNSO Councillors. At least one (1) Councillor from each ICANN geographic region is eligible for travel support. Within each geographic region, the Councillors decide among themselves who will receive funding and notify the secretariat. If all three Councillors from a region decline the travel funding, the unused slot is returned to the general pool and reallocated to the broader ccTLD community. Similarly, if any NomCom-appointed Councillor declines their funding, the corresponding slot also goes back into the “Broader ccTLD community” category. The remaining 9 full travel slots are allocated directly to the “Broader ccTLD community” category. Members of the ccTLD community, including Councillors not funded through the above mechanisms, can apply for these travel slots by completing an application form available on the ccNSO website. Detailed instructions will be shared via ccNSO mailing lists and published on the website. The ccNSO Travel Fund Committee will meet shortly after closure of the application window. The committee will need to evaluate all applications received via the online form - excluding the 5+3 Council slots - and make an informed decision on the distribution of the slots. The ccNSO Secretariat will submit the ccNSO travel fund database to ICANN Travel support by the deadline stipulated by ICANN org (typically 120 days prior to the meeting). All applicants will be informed about the outcome of the deliberations, and the list of ccNSO funded travelers will be posted on the ccNSO website. Go to https://ccnso.icann.org/en/about/funded-travel The applicable ccNSO Guideline can be found here: https://ccnso.icann.org/en/about/guidelines-travel-support-19sep24-en.pdf ICANN TRAVEL SUPPORT | Consult the ICANN Community Travel Support Guidelines here: https://www.icann.org/en/system/files/files/community-travel-support-guidel… ICANN might require funded Travelers to sign an acknowledgement and waiver, built in the meeting registration for anyone that is registering for in-person participation. Instructions on how to book travelwill be provided by ICANN Travel Support to funded travelers who are confirmed and eligible. TRAVEL ARRIVAL MEASURES | All travelers have a responsibility to understand the entry and exit requirements of their travel and determine if they can meet those requirements before committing to the travel. Travelers may review specific travel requirements by visiting https://apply.joinsherpa.com/map or their local government international traveler websites. ICANN is committed to ensuring inclusive Public Meetings that provides an equal opportunity for all to engage. If funded travelers are not eligible or cannot meet the entry requirements as outlined by the government of the meeting location, ICANN aims to offer an engaging virtual participation experience. Best regards. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> ccNSO at ICANN86: https://www.icann.org/en/ccnso/meetings

2 1

Please review: written updates about ccNSO WG/C and other governance groups
by Joke Braeken May 19, 2026

May 19, 2026

2 1

You're Invited, Register for our ccNSO Cocktail and Networking Event in Seville!
by Claudia Ruiz May 18, 2026

May 18, 2026

ccNSO Cocktail and Networking Event You are invited to a special ccNSO Cocktail & Networking Event in Seville! 📅 Date: Tuesday, 9th June 2026 Further details to follow… Register here: https://forms.gle/jccwj4ha9J6R7F4t5 Please note that spaces are limited and will be allocated on a first-come, first served basis. If your registration is successful, you will receive a confirmation email a few days prior to the event with the event details. ccNSO related session schedule: https://icann-community.atlassian.net/wiki/x/EQC0OQ ✨Thank you to our amazing sponsors for their support ✨ As always, if you have any questions, please feel free to reach out We hope to see you there!

1 0