[ccnso-council] Notes | ccNSO Council meeting 210 | Thursday, 17 October 2024 at 21:00 UTC

Oct. 17, 2024

      Notes

ccNSO Council meeting 210
Thursday, 17 October 2024 at 21:00 UTC

________________________________

Background and supporting documents

  *   Council workspace for this meeting:
https://community.icann.org/pages/viewpage.action?pageId=320405813

  *   ccNSO correspondence: statements and responses:
https://ccnso.icann.org/en/about/statements.htm

Agenda

  1.  Welcome and roll call

Welcome by chair Alejandra
anybody any AOB? none

a.            Establish whether meeting is Quorate

Claudia confirms we are quorate

  1.  Updates Statements of Interest

Any updates? none

Fill out the ccNSO Statement of Interest form:
https://forms.gle/79Jw4wSnNhn5W4Z46

Check your SOI here:  https://community.icann.org/x/doAFEg

Consult the ccNSO SOI Guideline:
https://ccnso.icann.org/sites/default/files/field-attached/ccnso-internal-pr...

ADMINISTRATIVE MATTERS
2.            Relevant Correspondence
3.            Minutes & Action Items
a.            Minutes Meeting 209: Circulated 14 October 2024

Any comments? none

  1.  Action items:

Any comments? none
suggestion : 5, 5, 6, 7, 8 and 9 skipped, in interest of time
Any concerns? none

4.            Intermeeting Decisions (since meeting 209, September 2024)

209-A: Adoption Terms of Reference DASC Effectiveness Review

5.            Intermeeting Decisions Triage Committee

UPDATES

6.            Update ECA, IFRT & CSC (written updates)
Informational

7.            Update Working Groups (written updates)
Informational

a.            ccPDP3-Review Mechanism - Dormant
b.            ccPDP4-IDN - Dormant
c.            DASC
d.            GRC
e.            IGLC
f.             MPC
g.            OMC - First meeting prior to ICANN81
h.            PGA WG
i.              SOPC – Had no meeting since meeting 209
j.              Tech WG - Had no meeting since Council meeting 209
k.            TLD-OPS SC - Had no meeting since Council meeting 209
l.              UAC
m.           Triage Committee - See items 16 and 19 b.
n.            CCG WS2 Implementation - Had no meeting since Council meeting 208
o.            IRP Panel Selection - Had no meeting since Council concluded its work, panel was appointed (see: https://www.icann.org/en/announcements/details/icann-announces-standing-pane...). Will no longer be included
p.            Planning Prioritization Process group - Had no meeting since Council meeting 208
q.            RZERC
r.             RSS GWG
s.            CIP-CCG

8.            Update Liaisons (written updates)
Informational
a.            Update ccNSO Liaison to ALAC
b.            Update ccNSO Liaison to GNSO Council
c.            Update ccNSO Liaison to UASG

9.            Update ccNSO Website redesign
Informational: No meeting since Council meeting 209.

10.          Update Chair, Vice-chairs, Councillors, Regional Organisations and Secretariat

Alejandra:

  *   1:1 with Sally. main topic was “how we meet”. We sent a letter a while ago. light review of the meeting strategy. lighter WG. no cross-community WG. not take too long. presented to SO/AC chairs in Istanbul
should not just include the meeting strategy, but also a broader scope of the meetings that take place in between icann meetings. ideas is to check on how the money is spent. how to be more cost-effective
Chris: lighter?
Alejandra: not as bureaucratic and long in duration versus a cross-community WG.
Chris: concerns me. that is still a review. lighter review. means fewer people. meaningless if it is still able to make recommendations and changes.
Alejandra: suggestions to the community, open for public comment.
Chris: cross-community review of the meeting strategy without a cross-community group. concerned about attempts to restructure the way the org works, without the using mechanisms that already exist. either it cannot make recommendations to change, and it is a waste of time, or it should be a proper cross community group
Alejandra: only a heads up today. more details in IST when the proposal will be presented

  *   I also have a head up to LACTLD about ccNSO activities in Kigali.
  *   GNSO already sent its IANA CCG rep.

Jordan:

  *   gave update to APTLD the week before that
  *   WSIS+20 group met. GDC: should people endorse it? What might the process mean? concrete overview of the process, and see where icann and its participants can make useful interventions
Chris: The first meeting was about the scope. a group to prod icann to move in the right direction. be a support to those people in the org that want to be proactive.

11.          Update Board Seat 12 Nomination Process by the Nomination Process Manager

Nick: i am a candidate. do i need to recuse myself?
Alejandra: not needed. regular update.
The nomination period for ICANN Board Seat 12 closed on 27 September 2024 at 23:59 UTC. Two candidates, Byron Holland and Nick Wenban-Smith, were nominated, seconded, and accepted their nominations before the deadline, as per the applicable rules. Due diligence for both candidates has begun.
One additional nominee declined to accept their nomination.
In line with the relevant guidelines and the timeline agreed upon by the ccNSO Council, an election will be held. The election will begin on 4 February 2025 (00:01 UTC), following the completion of due diligence and an opportunity for ccNSO members to interact with the candidates. The ccNSO members will propose and elect candidates for ICANN Board Seats 11 and 12, allocated to the ccNSO. The winner of the election—defined as the candidate receiving the most votes—will then be nominated to the ICANN Board by a majority vote of the ccNSO Council.
A Question & Answer session is planned between 22 and 28 January 2025, providing the ccNSO members and the broader ccTLD community an opportunity to engage with the candidates. In preparation for this session, the candidates have been invited to submit written statements, which can be found on the ccnso website.

12.          Update Council Election Process by the Election Process Manager

The 3-year term for five members of the ccNSO Council will end in March 2025. nominations close 22 October.
to date: no nominations for LAC region, neither for the EU region.
As per the ccNSO Guideline, only the Representative from a ccNSO member will be able to nominate and second candidates to serve as a ccNSO Councillor. Further instructions are included below. in line with previous election round: asked the Representatives if they agreed with the nomination/secondment made by the non-representative.

A Question and Answer session with the candidate(s) will be held on Wednesday, 12 November 2024 (13:15-14:30 local in Istanbul, 10:15-11:30 UTC), during ICANN81. In preparation of the Q&A session, the written candidate statements will be posted on the ccNSO website. The Q&A session gives the ccNSO members and broader ccTLD community an opportunity to interact with the candidates.

If at the close of nominations there are no more valid candidates in a particular geographic region than there are seats on the ccNSO Council available for that geographic region, then the nominated candidates shall be selected to serve on the ccNSO Council. Otherwise, an election shall be held for that geographic region, to select the ccNSO Councillors from among the valid candidates. The first election round (if any), will start Wednesday, 27 November 2024 (00:01 UTC) and will close Wednesday, 18 December 2024 (23:59 UTC), as per the timeline adopted by the Council.

ADMINISTRATIVE MATTERS & DECISIONS

13.          Appointment members to committees and working groups, if any

On our agenda we have the usual item of appointment of members. And again it is good to note we have volunteers stepping up to the plate.

However, I want to make two observations before we go to the draft resolution in front of us.
Firstly, we agreed that a team to review the DASC was necessary, and we adopted the terms of reference for such a review. When the terms were introduced, you were asked to consider volunteering, and after adoption were formally asked to volunteer. Despite a reminder, none of the eligible councillors stepped forward.

From my perspective, this is a little disappointing, not only for us as a Ccouncil, but also for the DASC itself. So I hope some of us who are not members of the DASC itself will step forward.

Related, under item 15 we'll be discussing the search for a volunteer to become ccNSO appointed liaison to ALAC  and under 19 b we will be preparing for the council work session in Istanbul. The discussion under 15 and the upcoming work session will focus on resourcing and prioritisation, and I invite you to take this experience into account to appreciate the importance and urgency of the work session.

Olga: i am member? need to reapply?
Alejandra: not needed
Olga: can nomcom appointed councillors apply for liaison role?
Alejandra: councillors are not eligible
we received the request by pablo to join IGLC. was sent after agenda was circulated. will be an online decision.

any questions regarding resolution? none
green marks

we appreciate your time and effort. thanks for volunteering

14.          Skills and expectation NomCom appointee to the ccNSO Council

We have received a request  from the NomCom operations team to review the current NomCom appointed ccNSO Councillor’s job description. The latest review was two years ago.
After going over it, I don’t see a reason to adjust it.
Questions Comments?

No changes to the current version

Action item: secretariat to please confirm to nomcom that no changes are needed.

15.          ccNSO Liaison to the ALAC: next steps

As you will have noted, no volunteer has stepped forward even after extension of the deadline. As already said this is an illustration of some of the issues we are facing with respect to “resourcing”: finding volunteers with adequate skills and experience and willing and able to put in time.
With this in mind we will need to decide what to do with this specific role.
Comments?

Options:

  *   Re-launch call for volunteers: starting ICANN81, include announcement during opening of ccNSO meetings
  *   Launch new call by ICANN82 (Seattle)
  *   No Action: reconsider decision September 2025.

Nick: 2 points.
general point about ICANN 81 workshop on planning and resourcing. lack of volunteers for DASC effectiveness review. and no volunteers for this role.
need to look more carefully at what we are doing. What is in it for the liaison? what is in it for them? What is in it for us?
Joke: https://ccnso.icann.org/en/announcements/announcement-2-12sep24-en.htm
Pablo: relaunch in Istanbul.
Jordan: agree
find someone who is prepared to do it
council agrees
Chris: i agree, but also, Nick is right. we should have a discussion. is there a value in doing this. if all that happens, is that a person goes to an ALAC meeting, and writes a report, which no-one reads….
Alejandra: ok. let’s discuss during the workshop.
Nick: i also voted to relaunch the call. i do read the alac report. not of high relevance to the cc-community.
Joke: As specified in the ccNSO Guideline Liaison and Observers (https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/g...) the ccNSO appointed liaison to the ALAC shall report to the ccNSO Council not less than monthly on the activities of the respective organization. The ccNSO appointed Liaison to the ALAC shall represent ccNSO values in these efforts, shall pursue specific direction from the ccNSO Council as and when given, and shall seek ccNSO Council advice as and when needed.
Jordan: if the idea is to build connections between the Councils, it would make more sense for liaisons to be Council members, instead of not-Council-members
Alejandra: often overlap between Council meetings.
Pablo: concern to be blindsighted. good to have someone to keep the flag high.
Alejandra: agree. relaunch in istanbul, discussion on whether role is needed or not. but agree with your comments Pablo

16.          Quarterly Monitor Progress ccNSO Activities

Nick: Triage committee reviews the ccnso activities on a quarterly basis. We did that last week.
no major changes to flag. some minor changes.

17.          Introduction and discussion text general invite ccTLD managers to become ccNSO members

Council was requested to send a letter to an individual ccTLD, inviting them to join the ccNSO as a member.  Council noted that such letter, if any, needs to be addressed to the current ccTLD Manager as listed in the Root Zone delegation record. The Secretariat was requested to draft a boilerplate text, and send it to Council for review.
The secretariat prepared a draft, and is now looking for your feed-back. If you could do so by next week 25 October, we can have it ready by the Council meeting in Istanbul.

18.          Introducing the Pilot Holistic Review

The pilot Holistic Review held its inaugural meeting on 30 September. Irina, Chris and Demi were selected and appointed.
Chris: Some people think the holistic review is different than ATRT3. get everybody on the same page. upcoming work: define what a holistic review is about. stay tuned.

SUBSTANTIVE MATTERS & DECISIONS

19.          ccNSO Schedule ICANN 81

Read more about the ccNSO at ICANN81: https://community.icann.org/x/IgDyF

a.            Council preparatory meeting
Irina and Andreas are invited. prep for the joint sessions.

  1.  Council workshop: Tentative What will be adequate resourcing the next five years and how can we achieve this.

Resourcing is a critical factor.
Nick: lots of ongoing activities. part of the CI initiative. we need to better match resources with the future workload. session is a brainstorming on doing some of that work, and get ideas from whole council. how does “good” look like? how to be more efficient and productive.
distribute the materials, so you can think about the session objective, and can prepare ahead of the meeting. We will circulate an overview.
“eating your own dog food” : make the session enjoyable for people.

Bart: You can expect a 4-pager.
background information with links. please click on the links.
start the discussion in Istanbul, then follow-up with an action plan.
virtual follow-up post ICANN 81.
discussion of 3 questions with flip-charts.
Remote participation will be challenging.
as soon as Triage and Alejandra finalised the overview, we will circulate it

Bart: one question. should we invite the leadership teams of the various committees and WGS. do you agree we invite them?
Alejandra: yes, personal opinion
council agrees too
Nick: useful work by the WG/C. let’s invite them

  1.  Council meeting

regular meeting in Istanbul on Thursday

  1.  Joint meeting: ccNSO and ICANN Board

i.Topics for discussion

Tentative from ccNSO (TBC’ed):

  *   Knowing that Board members are active in various committees, working groups and caucuses, and knowing that Board members step down regularly ( end-of term, for other reasons), is progress and continuity ensured of the (smaller) groups, specifically those groups that deal with community work (policy development, advisories, other work).

[ccnso-council] Notes | ccNSO Council meeting 210 | Thursday, 17 October 2024 at 21:00 UTC

Joke Braeken