ccNSO Council meeting 215
Thursday 13 February 2025
ICANN82
https://icann-community.atlassian.net/wiki/x/-4slBg
Welcome by Alejandra Reynoso
Council members are asked to add “Council” to their names in Zoom
We are quorate
Remote: Ali, Wafa, Jiankang
Any SOI updates? None
Any AOB?
Alejandra: e-mail from ICANN org. We will discuss in AOB
No relevant correspondence
a.
Minutes Meeting 214: not yet circulated
You may expect the minutes soon.
Action items as taken from the notes
b.
Action Items (preliminary, as taken from the meeting notes. Pending distribution and approval meeting minutes)
·
Action item 214-01 (ongoing)
GRC to prepare a draft response to the request for comments on the Proposed Updates to the Operating Standards for Specific Reviews.
·
Action item 214-02 (ongoing)
Secretariat and Peter Koch to draft input for Council’s discussion and consideration, regarding input for the work by the RSS GWG.
Skipping to item 5
a.
Adoption Board Seat 12 Nomination Report and formal nomination by Council of Byron Holland to Board Seat 12
None
CSC: Need for alternate to replace Nicklas Pousette for remainder of term (until 1 October 2015)
Suggested action item: Chair and secretariat to propose alternate for formal appointment by the Council
Alejandra: need to find replacement for an alternate on the CSC
Current members (Federico and Pablo), to seek an alternate for the remaining term of Nicklas, until start of October.
Role: CSC shadow, alternate. In case one of the members is not avalaible
a.
ccPDP3-Review Mechanism
- Dormant
b.
ccPDP4-IDN
- Dormant
c.
DASC
d.
FIN2 WG
e.
GRC
f.
IGLC
g.
MPC
h.
OMC
i.
PGA WG
j.
SOPC
k.
Tech WG
l.
TLD-OPS SC
m.
Triage Committee
n.
UAC
o.
CIP-CCG
p.
Planning Prioritization Process group
q.
RZERC
r.
RSS GWG
s.
ICANN How We Meet Group
Written updates - if any - are published on the wiki space for this meeting.
a.
Update ccNSO Liaison to ALAC
b.
Update ccNSO Liaison to GNSO Council
c.
Update ccNSO Liaison
to UASG
No meeting since Council meeting 214
Update taken from the meeting
ccPDP3: see update from Becky during Q&A. board consideration by or at icann83
ccPDP4: proceeding well
No questions or comments
a.
pre-ICANN82 SO/AC Round Tabl
The “How we meet” process and Reviews were the major topics.
As you may note these two topics are on the agenda, and we will discuss in more detail later on the agenda.
Additional Meeting: Biyi, Jordan and I met with ICANN org staff this week on the retirement policy. I’ll address this in more detail under the AOB.
We also met with other SO/AC on the next steps Pilot Holistic Review, we will discuss this further under item 17.
Leadership and OMC met with newcomers. We intend to turn this into a recurring (informal) event. It was a great opportunity for us to learn from them how we can improve the onboarding
process and build a mentoring program.
Meeting with RySG to find common topics of interest, and gather feedback from respective communities. Suggestion to hold a session at ICANN83
Peter:
Alejandra: action item for us to draft a statement
Biyi: more engagement with fellows and newcomers needed. Not just OMC, but all of us.
Pablo: yesterday meeting in LAC space. Hope for more engagement with/by ccTLDs from caribbean region
b.
Update Councillors from various sessions they attended during ICANN82
11.
Update Council 360 Review
Suggestion to extend deadline
Alejandra: only 6 provided feedback. Minimum 10 needed
Draft Resolution
Background
According to the ccNSO Council 360 feedback process (https://ccnso.icann.org/sites/default/files/field-attached/ccnso-council-360-degree-feedback-process-21dec23-en.pdf),
the review process should be open two-weeks, and at least 10 Councillors should have responded during this period. During the first 2025 process, which ran from Tuesday 11 February 2025 to 3 March 2025, only 6 Councillors responded, and hence the quorum was
not met.
Decision
The ccNSO Council extends the 360 review process until 21 March 2023.
The results will be shared with the Councillors. The results will be shared with the individual Councillors starting 25 March 2025.
Alejandra: Assuming they have not done so, and although Nick and Demi will step down at the end of this meeting, I suggest that both of them do provide their feedback as if they
are still Council.
Move: Olga
Second: Stephen
Any questions regarding the resolution?
Biyi: please send reminder with links to the survey
Bart: will do
Peter abstains
Other councillors approve, resolution is adopted
Alejandra: Before moving into the formal part of this section I want to thank all of you for an amazing year. A lot of what we have achieved since March 2024 is captured in our
annual achievement report. However that report does not do justice to your contributions and what we collectively have achieved and our collegiality. I think this is reflected in how we handled the assignment of roles and responsibilities for the upcoming
year. We will formally adopt the assignments under item c of this agenda item.
Bart explains the process.
First chair election. Nick will ask for a nomination/secondments. Candidates whether they accept. A secret vote only if more than 2 candidate
Chairs and vice chairs need to reside in different icann regions, to ensure geo diversity.
According to the Guideline: ccNSO Council Roles and Responsibilities (https://ccnso.icann.org/sites/default/files/field-attached/roles-responsibilities-council-26feb18-en.pdf)
the ccNSO Council elects is chair and vice-chairs annually, at the first ICANN meeting of the calendar year. The chair will be elected first and the vice-chairs selected afterwards. The section of the meeting where the Chair gets elected shall be chaired by
Vice-Chair who is not standing for chair. According to the Guideline the chair and vice-chairs need to be from different ICANN regions.
Chair election
After nomination and secondment, a candidate has to accept her/his nomination. If only one candidate stands, the Councillors will appoint the candidate by a public vote. If two or more candidates have
accepted the nomination, the Councillors will elect the Chair by a secret vote.
Vice-Chair elections
To be nominated as vice-chairs the following procedural requirements are relevant: The candidates should not be from the same ICANN regions nor from the Chair’s ICANN Geographic region, Has been nominated
and seconded, and has accepted her/his nomination.
If there are as many valid candidates as there are open Vice-chair seats and each candidate is from a different ICANN Geographic Region, the Vice-chairs will be appointed by a public vote.
a.
Election of the ccNSO Council Chair
The ccNSO Council is expected to elect its chair from its members at this meeting.
Draft Resolution
Decision
In accordance with the procedure to select its chair and vice-chairs, as included in the
Guideline ccNSO Roles and Responsibilities adopted on 26 February 2018, [insert name] was duly nominated and seconded as
candidate Chair of the ccNSO, and accepted her /his nomination and the ccNSO Council elects [insert name] to serve as its Chair starting at the end of the ICANN82 until the end of ICANN85.
The secretariat is requested to inform the ICANN secretary accordingly and post an announcement on the ccNSO Website. This resolution becomes effective upon publication.
Nick: thanks for explanation
Asking for nominations for the chair
Pablo: i nominate Alejandra Reynoso
Seconded by Demi
Any other nominations? None
Do you accept?
Alejandra: yes
Nick: thank you and congratulations
Alejandra: LAC region
b.
Election of the ccNSO Council vice-chairs
The ccNSO Council is expected to elect its vice- chairs from its members at this meeting.
Draft Resolution
Decision
In accordance with the procedure to select its chair and vice-chairs, as included in the
Guideline ccNSO Roles and Responsibilities adopted on 26 February 2018, [insert names] were duly nominated and seconded,
and accepted their nominations. It is noted that the Chair, and Vice-Chairs are all residing in different ICANN regions. The ccNSO Council elects [insert names ] to serve as its Vice-Chairs starting at the end of the ICANN82 meeting until the end of the ICANN85
meeting.
The secretariat is requested to inform the ICANN secretary accordingly and post an announcement on the ccNSO Website. This resolution becomes effective upon publication.
Nominations for Vice chair
Molehe: i nominate Biyi
Second: pablo
Biyi: i accept
Other nominations? There are 2 vice chair roles
Sean: i nominate Jordan
Chris: second
Jordan: i accept
Further nominations? None
Thank you all
Alejandra: thank you. Honour to do this
Regarding the process: all clear?
Bart: we will add the names to the resolution.
Jordan: quick reflection. 3 of us have a good dynamic. Pleasure to work with. Enjoy Alejandra’s leadership style
Biyi: alejandra knows how to make you work ;-)
c.
Adoption of Assignment of roles and responsibilities of Council members
By adopting the overview of roles and responsibilities of Councillors, individual Councillors are appointed to the various committees and liaison roles. The overview was provided on 12 March 2025.
Draft Resolution
Decision
The ccNSO Council adopts the March 2025 overview of roles and responsibilities and their assignment to Councillors, including those of the Council Chair and Vice-Chair as decided under a. and b.
above. The secretariat is requested to publish this resolution and the overview on the ccNSO website as soon as possible. This resolution becomes effective upon publication.
Alejandra: We have assigned roles and responsibilities last Sunday. The overview was circulated. By adopting the overview of roles and responsibilities of Councillors, individual
Councillors are appointed to the various committees and liaison roles. The overview was provided on 12 March 2025.
Move? Jenifer
Second? Chris
Any questions regarding the resolution? None
Green ticks
Adopted.
Alejandra: working with Jordan and Biyi is smooth. Happy to continue one extra year.
Draft Resolution
Background
After the successful conclusion (January 2025) of the review of the DNS Abuse Standing Committee (DASC), the Council requested the chair of the Council and chair of the GRC to document the method that
was used to review the effectiveness and efficiency of the DASC. The intention was that the method will be used to review the purpose, effectiveness and efficiency of other ccNSO Committees and long standing working groups, which are subject to a regular review.
According to their charters/ terms of reference, the following committees will need to be reviewed over time:
·
Meeting Program Committee (MPC), once every 3 years, starting November 2022
·
Internet Governance Liaison Committee (IGLC), once every 2 years, starting March 2023
·
Universal Acceptance Committee (UAC), every 2 years, starting July 2023
·
Strategic and Operational Planning Standing Committee (SOPC), once every 3 years, starting August 2022
·
Guideline Review Committee (GRC), once every 2 years, starting February 2022
·
TLD-Opc Steering Committee, once every 2 years, starting July 2017
·
Technical Working Group, once every 3 years, starting July 2022
Decision
The ccNSO Council adopts the Template/ Blueprint for review. The ccNSO Chair and secretariat are requested to develop a schedule and timeline for review of the various groups, after consulting the
various committees and taking into account the workload to conduct a review and need for a review. The schedule and timeline are expected by meeting 216. This would allow the Council to launch a review well before the Prague meeting (ICANN83). The secretariat
is requested to publish this resolution as soon as possible. This resolution becomes effective 7 days after publication. The chair is requested to inform the various working groups as soon as possible after the resolution becomes effective.
Alejandra: After the successful conclusion of the review of the DNS Abuse Standing Committee (DASC) in January this year, the Council requested the chair of the Council and chair
of the GRC to document the method that was used to review the effectiveness and efficiency of the DASC. The intention was that the method will be used to review the purpose, effectiveness and efficiency of other ccNSO Committees and long standing working groups.
The document was shared with you a few days ago.
I also want to alert you to the overview of the reviews, in particular to the aggregate effect. When looking at a review from an individual committee perspective, it makes sense
to do a review once every 2 or 3 years. However if you combine all the reviews, we are constantly reviewing the effectiveness and efficiency of committees. With this in mind we suggest that before embarking on reviews, we prioritize the reviews, and devise
a plan to do a maximum 2 reviews per year.
Move? Stephen
Second? Ali
Any questions regarding resolution? None
Green marks in zoom, adopted
Draft Resolution
Background
In February, Nicklas Pousette, the Councillor-elect, from the European Region announced that he will not start his term on the ccNSO Council starting at the end of ICANN83 (13 March 2025). To fill this
anticipated vacancy as soon as possible, the Council will launch an extraordinary European Region selection process, and therefore has to adopt a timeline and appoint the Selection process manager.
The proposed timeline was circulated separately. The main dates are:
·
Nomination period: 26 March - 22 April
·
Election, if needed: 30 April - 21 May 2025
·
Announcement 23 May 2025
In addition the Council needs to appoint the Election Process Manager
Decision
The ccNSO Council adopts the proposed timeline for the extraordinary ccNSO Council European election. The ccNSO Council appoints Joke Braeken, ccNSO secretariat, as Election Process Manager. The
secretariat is requested to publish this resolution as soon as possible. The decision becomes effective upon publication.
Alejandra: Nicklas Pousette, councillor Elect EU region. His term was supposed to start at conclusion of ICANN82. He resigned Other councillors from the EU region
wanted to have the seat filled asap. Not wait for the review of the council selection guideline
Move? Peter
Seconded? Wafa
No questions
Green ticks in zoom. adopted.
Draft Resolution
Decision
The following persons are appointed:
·
Alishah Shariff to the IGLC
·
Ann Ibrahim (InternetNZ) to the UAC
The secretariat is requested to inform the appointees and chairs of the committees accordingly. The secretariat is also requested to publish this resolution as soon as feasible. This resolution becomes
effective upon publication.
Joke: typo in Anne’s name
Move? Olga
Second? Jenifer
All in favour
For discussion
Jordan: concerns regarding icann’s presentation. It was straightforward by the community. That it was suggestions for cost-savings. ccTLD managers to offer their thoughts, through
the public comments. Ccnso session, aggregate comments from the ccTLD community
Alejandra: molehe and Jodi to review outcomes of the session
We will prepare a statement
For discussion
Any action required by the Council?
Chris: board weas thinking to review this. Co-chairs of PHR had conversations with Board and community members. Meeting with SO/AC chairs. And Cherlyn LOE. chair ATRT3.
Way to deal with PHR, provide that the community can accept the premises on which the review is going to be build. SO/AC chairs and Board effectiveness community.
As long as you accept what we will do, we will build it. Subject to all accepting it, and subject to the board accepting to continue. Tripti mentioned a few times: go back to drawing
board. Stop what we are doing. Why do we do this. ATRT4. Unanimity, waste of time. At-large mostly thinks it is not a waste of time.
Alejandra: occurred to me. Write to board first?
Chris: what we say to them will have some effect to what they decide. We need to write to them first.
Alejandra: we will wait for the letter to arrive and will reply
Alejandra: regarding ATRT4. Should we do sth? It was deferred to april, discussed in the reviews. Cascading effect it has.
Chris: no harm to draft a note to the board.
We need to write them: do you intent to move forward with ATRT4?
Alejandra: and all other reviews?
Chris: board might have sent it already by the time we decide
Jordan: entire review system is broken. Intended as sth useful. Need to look as icann system as a whole. Holistic review. All other reviews are not in scope. Pause all reviews?
Incl PHR? Stop all bylaw reviews? Appoint a design team to design a good review process?
Chris: yes. Sort of what Tripti said.
When Fadhi and Larry agreed what the review should be about. NTIA to plug topics out.
If we wanted to write to board and say that, it would be helpful. Right path forward.
Chris, Jordan, Sean, Peter volunteered to drafting team
Peter: not all bylaw reviews are equal. Be careful. Do not throw away the baby with the bathwater
Chris: by next council meeting
Bart: mid April
Alejandra: Retirement policy: we have just received a note from ICANN. I have shared this to the council, and I suggest that we do not respond directly, but
by our next council meeting in April at the latest.
From my perspective this request ends all other conversations we had and we only focus on the response.
I also urge everyone not to respond to any questions regarding .su case in your capacity as Councillor, and note that the retirement working group was formally
closed at our 22 September 2022 meeting.
May I ask Jordan, Biyi, Chris and Peter, together with the secretariat to prepare a response, to be circulated to the list. They agree
Questions, comments? None
AOB? none