NOTES | ccNSO Council Meeting 189 | 17 November 2022 (18.00-20.00 UTC)
1.
Welcome and roll call
Wiki: https://community.icann.org/x/fdAGCw
Note: Council meeting formally finishes at 19.00 UTC. Second part is workshop (guests, members ccPDP3 and ccPDP 4 have been invited and all people on the call are welcome to participate)
Council meeting is quorate
AOB? Alejandra has one: email by Brett Carr. He will change jobs
2.
Relevant Correspondence
(https://ccnso.icann.org/en/about/statements.htm)
a.
Response Samantha Eisner in response to letter ccNSO on interpretation section 8.8 ICANN Bylaws (see item 4 a).
b.
Comments ccNSO Council on Pilot Holistic review (see item 4.b)
3.
Minutes & Action Items
a.
Minutes Meeting 188: circulated 8 November 2022
b.
Action items and/or To-Do’s:
4.
Intermeeting Decisions (since meeting 188, 20 October 2022)
a.
Adoption nomination criteria NomCom appointee ccNSO Council
b.
Council support ccNSO Council comments Pilot Holistic Review
c.
Request GRC to develop ccNSO Guideline on how to relate to implementation ccNSO Policy
d.
Appointment members SOPC, DASC, Tech WG, MPC and IGLC
e.
Selection of Sean Copeland (Councillor and Chair GRC) and Everton Rodrigues (Chair of MPC), ICANN leadership program.
Item 5-9 Updates and Q&A
item 5-9: delay in the written updates. they will come soon. Please use the mailing lists, should you have any comments
5.
Update ECA, CSC, CSC RT
(written updates, if anything to update)
See AOB regarding the ccNSO appointee to the CSC
6.
Update WGs taken
(written updates, unless no meeting)
Please use the mailing lists, should you have any comments
Is there anything that needs to be mentioned regarding the PDPs?
Stephen: ccPDP3 ready for public comments. one appendix needs to be filled in.
Retirement process was approved by the Board. Kim Davies confirmed to Stephen that IANA is looking into matters.
Bart: expects the week after Thanksgiving that the report will be published for public comments
Irina: SOPC has submitted comments regarding IANA and pti draft operating budgets. we are fine with the proposals, but are concerned regarding implementation of PDPs. and the personnel costs
Ans I forgot to mention that SOPC invited Tech WG members to participate in drafting comments and thanks them for their valuable input
Bart: ccPDP4 has been making considerable progress since ICANN75. the full WG adopted the recommendations with respect to variant management. nearly completed the basic discussion around the
use of the Review Mechanism. in principle, they will refer to the RM for IFO decisions, when an IDN ccTLD string needs to be de-selected. there will be a special RM for confusing similarity. this is already included in the fast track process currently. special
RM under that policy. the CS group will meet next week on a 2nd reading of the basic text. on 29 Nov, there will be a joint meeting with the GNSO EPDP group, to coordinate around confusing similarity. you are welcome to join. The coordination with GNSO is
going fairly well, both with respect to Variant Management and Confusing Similarity.
a.
IGLC
b.
GRC
c.
SOPC
d.
OISC
(no meeting since ICANN74, travel funding subgroup met)
e.
TLD-OPS
f.
DASC
g.
Technical WG
(no meeting since ICANN75)
h.
MPC
i.
Triage Committee
(no meeting since ICANN75)
j.
IRP Panel selection
k.
CCG WS 2 Implementation
l.
Prioritization Framework group
7.
Updates ccPDPs
(written updates)
a.
Update ccPDP3 - Review Mechanism
(no meeting since 20 October 2022, awaiting public comment)
b.
Update IDN ccPDP4
(written update)
8.
Update liaisons
(written updates)
a.
Update ALAC Liaison
b.
Update GNSO Liaison
9.
Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat
Alejandra: Kim, please tell us about the planning meeting for ICANN76
Kim: let’s wait until item 19
Administrative matters for discussion and/or decision during the meeting
(items 10 – 16)
10.
Adoption 2023 Election report ccNSO Council
For decision
Joke: no issues or concerns. no elections, as only one candidate per region
Mover? Pablo
Seconder? Demi
Questions with respect to the resolution? none
Vote: all in favour
to do: secretariat to set up onboarding session with new councillors in january
11.
Adoption ccNSO Comments Initial report 2nd CSC Effectiveness Review.
For decision
Mover? Olga
Seconder? Irina
Questions with respect to the resolution? Irina requested a correction of her surname
Vote: all in favour
12.
Update and follow-up development of ccNSO & UA Roadmap
Ai-Chin provides an update: The small team met on 2 November. The team consists of Councilors only, namely Jenifer, Ai-chin, Jiankang, Biyi and Pablo. The team approved the report of the discussions
from the ICANN75 session on the role of the ccNSO and UA. This report was previously shared with the full Council as well. The team agreed on the next steps, which consist of a workshop during the December Council meeting, to determine the possible impact
and implementation effort of the various suggestions from ICANN75. The purpose is to determine the value of the suggestions for the community, as well as the sustainability of implementation of the suggestions. Based on the workshop results, the small team
will prepare a draft roadmap for Council’s consideration. If Council agrees, the roadmap will be presented to the community at ICANN76. Unless there are community objections or concerns, the draft Roadmap will be presented for adoption by Council at its
ICANN76 meeting.
Alejandra: thanks for the heads up that the December council meeting will also include a workshop
13.
Updates ccNSO Internal Procedures
a.
Update Procedures for ccNSO Appointees
b.
Guideline: ccNSO Nomination Process ICANN Board Seats 11 and 12
c.
Guideline: ccNSO Council Election
d.
Update Guideline: ccNSO SoI and CoI
Sean: SOI/COI is moving forward. happy with progress. Monday GRC will address the guidelines on Board nominations and the council elections. the deadline for comments has passed.
Patricio: was going to send a short comment, but the window closed yesterday. Apologies that I missed the deadline. in the call for candidates, it says that the call for candidates must include
the closing date. the opening date is not mentioned in the guidelines. nominations submitted before the opening date were previously discarded.
Bart: the GRC will start the discussion on implementation of policies. The ccNSO is responsible for the policy development. Once the board has approved the policy, it will go into implementation.
set expectations: together with icann org, define a role and points of interaction. That work will kick off at the upcoming GRC meeting
Sean: we have invited guest speakers. first tentative steps. learning process for us. input is beneficial.
Bart: open for discussion by GRC whether we will work with sub-groups. If the GRC decides to have sub-groups, please volunteer. First meeting is on Monday. you are welcome to join. please let
staff know.
14.
Update Charters, Terms of Reference
a.
Amended charter MPC for Council consideration
Joke gives highlights
Mover? notes missing
Seconder? notes missing
Questions with respect to the resolution?none
Vote: All in Favour
b.
Terms of reference for review Effectiveness ccNSO Outreach and Involvement Standing Committee (OISC)
For decision
draft template for the review was circulated. Similar approach to CSC Effectiveness Review
Irina: what is the reason to make this review? and why now?
Alejandra: this SC has been dormant. question arose whether we should keep the committee or not. review was proposed, to inform that decision.
Bart: in the past there was the travel funding committee and other external committees which were incorporated in the OISC. if you close the OISC, what will you do with those tasks that will
continue. Ensure that at least some of the activities continue. important to all on this call.
Mover? Pablo
Seconder? Ali
Questions with respect to the resolution? None
Vote: all in favour
15.
Appointments to Working Groups and Committees
Background: Peter Koch (.de) was appointed in 2019 for a second term of 3 years. His term ends this calendar year. The call for expression of interest closed on 9 November 2022
and Peter was the only candidate.
Stephen: unique skill set. make sure that once his term is up, there is a successor
Chris: we should ask Peter what the basic skill set required for that role is.
Alejandra: let’s add this to our to do. Contact Peter.
Bart: likes the approach. this approach might be useful for all external committees. let’s discuss this perhaps at the Cancun workshop, when we will discuss roles and responsibilities.
let’s come up with a succession plan.
Alejandra: call for volunteers includes written skillsets. anything in addition to that?
Chris: there is a difference. what is the minimum skillset that peter feels he can work with, to bring someone up to speed the next 2 years, to bring the person fully up to
speed, and prepare him/her to take over
Pablo: had the opportunity in KL to attend some meetings that dealt with administrative matters. root zone operators. guidelines presented by icann. What funding from icann?
you do not require to be a techie.
Mover? notes missing
Seconder? notes missing
Questions with respect to the resolution? none
Vote: all in favour
16.
Progress Board Seat 11 Nominations
Informational
Joke: provides update
Alejandra: once council adopts the report, inform ECA about the candidate
Nick: why still election if only one candidate? is voting anonymous
Alejandra: none of the above option was added to the guideline upon request of the membership
Joke: voting is secret.
Items
for discussion and/or decision during the meeting (items 17-20)
17.
Update ccNSO Website redesign
Nick: delay of almost a year. other priorities by icann org. content management. how to become less dependent on icann web team? what maintenance is required? members-only section,
for TLD OPS for instance?
Jiankang: we do not need anything new. the ccnso website should be accessible from most browser versions. cctld family from all over the world
Nick: current website carried over in its entirety
18.
Peer review (NomCom) Council members
Alejandra: should council review the performance of its peers?
Chris: recommendation of the review to the NomCom, that appointees should be reviewed, and that the results should be sent to NomCom
Alejandra: should we open this to all councillors?
Chris: closed process. council has no role in the selection.
Alejandra: reflect how to do this. there will be a meeting between ccnso chair and vice chairs with NomCom, to discuss skillsets for future appointees. Questions regarding how to conduct the
review for them can be addressed at that point in time.
Chris: NomCom has high turnover. if the recommendation is going to proceed, and board etc gives input to NomCom. up to us to decide how to do this. this is a delicate matter. there needs to
be agreement. regular group of councillors to work this out, without breaching delicate balance
Bart: let’s have a small group to discuss how to conduct this properly. propose plan at December meeting
19.
ICANN76
For discussion
a.
ccNSO 20th Anniversary
b.
Joint meetings:
i.ccNSO-GNSO Council Meetings
ii.ccNSO Council-ALAC
iii.ccNSO-GAC
iv.ccNSO-Board (full Board or ccTLD related Board members)
Alejandra suggest to not meet with full board at community forum, only with cctld-related board members. policy forum: never meeting with Board. Then have a joint session with
the full board at AGM
20.
AOB
Alejandra: will discuss on mailing list regarding Brett Carr’s position
Stephen: i am in BRU at DNS Symposium. presentation regarding RSAC and where they are at. encourages that at the next meeting we be informed
Eberhard: can be invited any time at Tech Day
21.
Next Council Meetings
·
Meeting 190, December 15 – 12:00 UTC, 2 hours to include workshop ccNSO & UA
·
Meeting 191, 19 January 2023 - 21:00 UTC
·
Meeting 192, 16 February 2023 - 12:00 UTC
·
Meeting 193, 16 March 2023 - ICANN76 TBD
In addition staff proposes the usual Council preparatory meeting and in addition a workshop on roles and responsibilities of the Councillors during ICANN76 for Sunday 12 March 2023
22.
Closure
Part 2 – 17 November 2022, 19.00 UTC.
Open Council Workshop
Effectiveness and efficiency of ccNSO (policy development) processes.
Use the development of the retirement process as a case study to identify areas of improvement of the process.
Jordan: structured reflection on what worked well, and what we should do differently.
agenda:
Notes will be taken in the jamboard.
Jordan: delay in 2015-2017 timeframe?
Bart: we had 2 drafting teams. one working on issues regarding retirement, other one on RM. discussion whether it should be 1 or 2 PDPs, and the order of handling things. the drafting teams
started in january, until april. discussions at icann meetings, need to consult community

Group 1: Report by Nick

Group 2: Report by Bart

Report by Pablo

Report by Allan
Jordan summarises the main findings. analysis needed of the comments, and a report for the next council meeting
thanks, bye all
Joke Braeken
joke.braeken@icann.org