NOTES | ccNSO Council Meeting 178 | 16 December 2021, 18.00 UTC
1.
Welcome and roll call
Welcome by Chair Alejandra Reynoso
Background material: https://community.icann.org/display/ccNSOCWS/16+December+2021+-+18%3A00+UTC
are we quorate? yes
2.
Relevant Correspondence (https://ccnso.icann.org/en/about/statements.htm)
3.
Minutes & Action Items
a.
Minutes Meeting 177: circulated and published
b.
Action items and To-do’s, if any
Action Item 177-01: Proposal to defer until later.
Action item 177-02 : Ongoing
Action item 177-03: Completed see item 17
To-do: Update Tech WG Ongoing for discussion under item 17.
4.
Intermeeting Decisions (since meeting 177 October 2021)
this includes also the Triage committee decisions. no comments
Item 5-9 Written updates unless special developments Council needs to be aware of and Q&A
see https://docs.google.com/document/d/1Y07DWDI-3nDrt7ctxm589PfQU31my1iv70FdtYJtUBY/edit?usp=sharing
5.
Update ECA & CSC
(written updates)
6.
Update WGs taken
(written updates)
a.
IGLC
b.
SOPC
a.
GRC
b.
OISC
c.
TLD-OPS
d.
Technical WG
e.
MPC
7.
Updates ccPDPs
(written updates)
a.
Update ccPDP3 - Review Mechanism
b.
Update IDN ccPDP4
ICANN Board has opened a public comment (22 Nov - 12 Jan) and has asked the GAC for its advice on the proposed policy. (22 November 2021 - 12 January 2022.) as per the provisions in the bylaws. See
https://www.icann.org/en/public-comment
8.
Update liaisons
a.
Update ALAC Liaison (written update)
b.
Update GNSO Liaison (written update)
9.
Update Chair, Vice-Chairs, Councilors, RO’s and Secretariat
none
Alejandra:
Item 10 - 16 for discussion during the meeting
10.
Selection Members panel ICANN Excellence Award 2022
we were approached to appoint 2 members. currently Margarita and Stephen
Ideally 2 consecutive terms, before stepping down. not a hard requirement.
Call for volunteers closes 22 Dec. Appointments to be made by 24 Jan.
Alejandra suggests that when we select the candidates we have an eye for long-standing community members that are familiar with the community.
Stephen: glad to hear there are volunteers, withdraws, since he served already for 3 years at leats
Alejandra: Thank you for your service on the panel.
11.
Update on changes to ccNSO ICANN Learn
Svitlana: We revised the course. We thought about the audience: newcomers from the ccTLD community, and also other representatives that are from outside the ccTLD community. We tried to emphasise what was important,
we made it more lively, and introduced a quiz section. The main purpose was to make the course easier to understand. We tried to translate the course into “human language”. I read the revised course with pleasure. Invites all to have a look.
Joke: A small team of ccTLD volunteers performed an extensive revision of the current ccNSO Onboarding Course (ICANN Learn identifier 150.1), addressing both content, accessibility, and other aspects. Following
review and input by relevant ICANN staff, the small team will finalise its recommendation to the ccNSO OISC and Council, for final review and adoption.
The aim is having the course eventually translated in the various languages ICANN provides translations in.
Alejandra? when ready?
Joke: hopefully by end January.
Svitlana suggests a regular review of the content.
12.
Closure special Council Elections European region
Giovanni will step down on 31 dec. For the remainder of his term, an election process was kicked off.
Joke: one candidate: Chris Disspain. one observation, added to the report. regarding Chris his affiliation with a cctld manager. Chris mentioned he is not affiliated with a ccTLD. bylaws and guideline refer to
individuals not representing their employers
stephen: any issues with his candidacy?
Alejandra: none
Pablo: moves
Javier: second
in favour? green ticks
abstain? none
approved.
13.
Closure Council Elections 2022
Alejandra: To do. Nick’s affiliation in agenda needs to be corrected
Councillors invited to reach out to potential individuals who might be interested in the work of the ccnso and council
Pablo: move
Irina: second
in favour: green ticks
abstain? none
objections? none
passed.
Congratulations to all!
14.
Appointment Chris Disspain to the Strategic and Operational Planning Committee (SOPC)
move? Irina
Second? Stephen
Pablo: happy with that decision. Chris has a lot to offer to this group and to the ccnso. we can benefit from his knowledge
in favour? green ticks
Abstain? none
Against? none
passed.
Alejandra: good to see new members join the SOPC. This committee is being respected throughout the community. Giovanni needs to leave and we need a new chair.
Alejandra: What is required to be the SOPC chair?
Giovanni: SOPC meeting on Monday. The next steps will be discussed at that meeting. FY23 budget is open for comments. Chair needs to be spend some hours each month to the info that comes in. the role requires
patience, to make sure there is coordination between the members, to provide timely input. Giovanni encourages a SOPC chair to step forward. it is prestigious, positively looked at by icann org and other SO/ACs , but it is a job that requires time.
Stephen: big shoes to fill! What is your shoe size? :)
Pablo: thank you, you are an example.
Alejandra: the committee’s work is also done by its members. Councillors on the SOPC are encouraged to move the work of the committee forward. make sure it continues to keep up those high standards.
15.
Update re-design process ccNSO Website
A small team of councilors started working on the new website. various personas were created. Who is your target audience? not only ccTLD managers, but also other profiles (other SO/ACs, icann staff, non members
from cctld community etc). preliminary ranking of main sections on the website, to be prioritised. hopefully a proposal by the next council meeting
Nick: timing by icann web team?
Alejandra: not a quick process. icann org is doing an audit of the ccnso website, and the taxonomy should be ready by June. In the meanwhile we will review the content analysis. they will explore new features.
Perhaps content for members only. ccnso small team to look into content to be archived or deleted.
Stephen: since not much is happening until June, and I expect it even later
This small group should continue to insist on fixing broken links
Alejandra: yes. let’s do parallel work and keep the conversation going
16.
Progress process to change the Rules of the ccNSO: next steps and what can Council expect?
Alejandra: GRC soon expects the final draft. Will then be sent to Council. Council to review. Once we agree, it should be presented to the members for a vote. voting to start probably by the end of February. Needs
to stay open for 14 days. a supermajority needs to be in favour. we need at least 50% of the members to vote. if the quorum is not met, we have a second round without a quorum.
David McAuley: (chair of the GRC sub-group on rules). one clarification. when the vote is for a board member, the quorum does not apply. the members continue to have the ultimate responsibility for selecting a
board member
Alejandra: thank you for guiding us through this process David. You are a very good chair
17. Review of Charters WG and Committees: next steps
Tech WG: Stephen is council liaison to the Tech WG
The current charter is outdated, and mostly not applicable
A proposed new draft was sent to the Chair. no comment yet. Stephen will remind him, and will then send the proposed draft to the entire Tech WG.
will keep the council informed.
Alejandra: until mid January? for feedback by Tech WG
Stephen: has been dragging a long time. do not expect strong objections by the Tech WG members.
Alejandra: let’s have it ready by the next Council meeting
Alejandra: let’s ask all WG/C to review their charters and see whether updates are needed.
Stephen: concern. We should stagger the review processes.
Sean: GRC has a new chair. ideally: 2 per year up for review.
Alejandra: some are overdue, some need to be done and are on track
Bart: There is a difference between review and update. Does the purpose still match the activities of rh WG? Some WGs are already in the process. e.g. Triage Committee, GRC too.
First do a review regarding the purpose.
Nick: bake into the ccnso process that a review is due. scheduled in the diary, notification 6 months prior to the deadline.
Alejandra: yes, should be part of the ongoing activities. I will send an email to chairs, asking them to review their charters.
17.
ccNSO and DNS Abuse: what should the ccNSO do?
Tatiana: small group working on what the ccNSO should do with respect to DNS Abuse. results based on the ICANN72 session and the November workshop for Council and community. suggestions were categorised: effort
and benefit (matrix - high to low values)
4 categories:
Nick: perhaps we should properly distinguish between the things we already do and those which are new.
Alejandra: the small team also still considers creating a WG. For our next update, we will present you how these efforts influence each other, and how the dynamics work. We should organise a webinar for the community
at the end of January, start of Febuary
18.
ICANN73 Meetings
a.
ccNSO Council
i.Prep meeting
make sure you participate. We will review the annual roles and responsibilities overview for Councillors, and will confirm during the council meeting later that week. We will also need to elect the Council chair
and Vice chairs at the meeting itself
ii. Council meeting (last day - Thursday)
b.
Bilateral Council meetings
i.ccNSO – GNSO. Suggested topics? e.g. CSC Review. Anything else. Please send to mailing list
ii.ccNSO Joint session with ICANN Board of Directors or ccNSO related Board members? What is the preference? Pablo: only ccnso related
board members. Stephen: agree. Nick: danger. we talk to people that agree with us, and are from our community. the meeting with the full board is a good opportunity to stress for instance the difference between ccTLDs and gTLDS. unique opportunity to have
these touch points.
Alejandra: not the only chance we have to meet with the Board.
Irina: depends on the topics whether we need to meet with the full board.
Stephen: agrees with Nick.
Alejandra: no full board meeting at policy forum. let’s meet with them at the AGM.
Biyi: first decide on the topics.
Suggested topics?
iii. ccNSO - GAC
Giovanni steps down as liaison. easy task, to manage. discuss topics for the upcoming meeting. please self-nominate online.
c.
ccTLD relevant sessions
i.ccNSO webinar for newcomers: Date and time
TBC
ii.ccTLD news sessions
1.
ccTLD News #1 - General session
2.
ccTLD News #2 – Topical session
See Heads up! ICANN73 ccTLD News Sessions: Applications for speaker slots open soon
https://ccnso.icann.org/en/announcements/announcement-16dec21-en.htm
iii. Tech Day
iv.ccNSO Members’ meetings
1.
Governance session (TBC)
a.
Rules
b.
Conflict of interest
2.
ccNSO & DNS Abuse Session
v.Plenary session(s)
1.
Proposed: Moving Forward with the Global Public Interest Framework (TBC)
2.
Overview legislative initiatives with potential impact on DNS (TBC)
3.
Plenary Session 3: TBD
19.
Next Meetings
a.
Meeting 179, Jan 27 - 12:00 UTC: Discussion Roadmap ccNSO & DNS Abuse + discussion new Rules.
b.
Meeting 180, Feb 24 - 21:00 UTC: Strategy workshop, agree on ccNSO & DNS Abuse roadmap.
c.
Meeting 181, Mar 05-10 - ICANN73
TBD: Roles & Responsibilities and chair & vice-chair election
d.
Meeting 182, Apr 21 - 12:00 UTC: Adopt work plan
e.
Meeting 183, May 19 - 18:00 UTC
f.
Meeting 184, Jun 13-16 - ICANN74
TBD: Launch Board Seat 11 nomination process
g.
Meeting 185, Jul 21 - 12:00 UTC
h.
Meeting 186, Aug 18 - 21:00 UTC
i.
Meeting 187, Sep 17-22 - ICANN75
TBD:
j.
Meeting 188, Oct 20 - 12:00 UTC
k.
Meeting 189, Nov 17 - 18:00 UTC
l.
Meeting 190, Dec 15 - 12:00 UTC
20.
AOB
21.
Thank you
22.
Closure
thank you all. Happy holidays! Bye
Joke Braeken
ccNSO Policy Advisor
joke.braeken@icann.org