NOTES
ccNSO Council meeting 229
Thursday, 21 May 2026 | 13:00 UTC
https://icann-community.atlassian.net/wiki/x/AYDZK
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
Consult the
ccNSO SOI Guideline
Complete the SOI
template
Check the ccNSO
Statements of Interest
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)
Claudia: apologies from Chris Disspain
You are quorate
·
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.
Circulated to the Council mailing list on 6 May 2026
Any questions?
If none, Minutes are confirmed!
All due action items are completed, any questions?
The Secretariat is asked to launch a call for volunteers for a new member to the Planning Prioritization Process group. (Completed, see item 15)
The Chair of the ccNSO is requested to formally welcome the RED.ES as a member.
(Completed)
The secretariat is requested to publish the membership approval of RED.ES, the ccTLD Manager of .es.
(Completed)
The secretariat is requested to publish the adoption of the ccNSO Guideline Statement and Conflict of Interest.
The secretariat is requested to inform the leadership team of the IGLC and persons appointed and enable their participation in the respective teams.
(Completed)
The Secretariat to send a calendar invite for the ICANN86 Council prep call.
(Completed)
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).
a.
Approval comments on the Co-Chair’s Review of Reviews Refined Outline
We have taken one decision
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.
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
If any - since meeting 228 from the following groups can also be found on the wiki space for this meeting.
Governance Groups:
Liaisons:
ccNSO WG and Committees:
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.
Informational
Although also included in written updates, Alejandra provides information on the planning the next weeks (Seville and beyond,
public comment)
Nick was elected Vice Chair.
ccNSO representatives appointed to this effort:
Informational
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
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
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.
Bart: more to follow in Seville
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.
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
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.
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.
·
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”
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
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
Alejandra: Thursday 13.00 UTC: to discuss
Biyi: public holiday in Nigeria
Alejandra: will be recorded.
Also a holiday for Wafa and Sami. major Muslim holiday.
Topics:
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
none
·
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