NOTES | ccNSO Council Meeting 186 | 18 August 2022 (21:00 UTC)
1.
Welcome and roll call
Welcome by Chair Alejandra
We are quorate
Docs for today: ccNSO Council meeting, held on 18 August at 21 UTC
Chris: AOB, bylaw with respect to NomCom committee
2.
Relevant Correspondence (https://ccnso.icann.org/en/about/statements.htm)
3.
Minutes & Action Items
a.
Minutes Meeting 185
Circulated to Council on 9 August 2022
b.
Action items and To-do’s
Action Item 185-01:
The Council requests the secretariat to publish the amended charter as soon as possible (after inclusion of date of adoption by Council) and inform the chair of Tech WG accordingly. (Tech WG)
(Completed)
Action Item 185-02:
Secretariat to inform chairs and new members of working group appointments, including chair and vice-chair appointments. (GRC and Tech WG).
(Completed)
Action Item 185-03:
The Secretariat is requested to inform the former manager of .by of termination of membership to ccNSO
(Completed)
Action Item 185-04:
The chair is requested to formally welcome ARN, the ccTLD Manager for .gw, to the ccNSO. (Completed)
Action Item 185-05:
The secretariat is requested to publish an announcement on the ccNSO website, after the letter has been posted in the ccNSO correspondence section
(letter re exclusion of ccTLD policy related matters from ICANN Reconsideration and Independent Review Process)
(Completed)
Action Item 185-06:
Triage Committee to provide priority advice at the September Council meeting
(Completed, see item 6.i)
Action Item 185-07:
The ccNSO Council requests the secretariat to circulate the updated Internal Rules to the ccNSO Membership and seek feed-back, after consulting the GRC on timing and next steps. The goal is that the Council is in a position to adopt
the amended Rules by its next meeting, and circulate the proposed Rules prior to ICANN75 and call for a membership vote, which should start one week after ICANN75.
(see agenda item 18)
Action Item 185-08:
Secretariat to update and circulate link to Bylaw change repository
(Ongoing)
Action Item 185-09:
ccNSO Chair along with Secretariat, evaluate current ICANN75 block schedule and find a suitable time for MSM session
(Completed)
Action Item 185-10:
Secretariat inform meetings team and Board Op the ccNSO wishes to have a meeting with the full ICANN Board
(Completed)
Action Item 185-11:
Council to begin discussion on topics for session at ICANN75 with Board
(See item 16.b.iii)
Note all actions completed possible exception 08.
Note 185-06 (Triage) - next council meeting
item 185-08 : Bart will complete this
Questions? None
4.
Intermeeting Decisions (since meeting 185, 21 July 2022)
Alejandra: new. publication inter-meeting decisions on ccnso website. not only included in agenda, but from now onwards also on website.
Item 5-9 Updates and Q&A
5.
Update ECA, CSC, CSC RT
(written updates)
6.
Update WGs taken
(written updates)
a.
IGLC
b.
SOPC (see item 10)
c.
GRC
d.
OISC
e.
TLD-OPS
f.
DASC
g.
Technical WG
h.
MPC (see item 18)
i.
Triage Committee
j.
WS2 CCG
k.
IRP Standing Panel
7.
Updates ccPDPs
(written updates)
a.
Update ccPDP3 - Review Mechanism
b.
Update ccPDP4 - IDN
8.
Update liaisons
(written updates)
a.
Update ccNSO appointed Liaison to ALAC
b.
Update ccNSO appointed Liaison to GNSO
9.
Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat
Topic for plenary session at ICANN75 confirmed.
Jordan volunteered to help with the planning of this session.
Jordan needs more understanding of the ccNSO perspective. internet fragmentation and the role of ICANN. do you have resources or perspectives? let Jordan know, and have a chat.
Alejandra speaks to Roundtable agenda
Friday 9 September 2022, 1400 – 1530 UTC (90 minutes)
Proposed Agenda:
Item 10 - 20 for discussion or decision during the meeting
10.
Update Charters, Terms of Reference
For Information and Decision
Recurring until review of all characters and terms of reference has been completed. The SOPC has reviewed and updated its Charter, and consulted the ccNSO membership and broader ccTLD community on the final proposed draft, before
having submitted it to the ccNSO Council for adoption. Consultations took place during an ICANN74 SOPC session and via the ccNSO members mailing list in August.
Draft Resolution
Background
The SOPC has reviewed its charter following the ICANN74 session on purpose and scope of activities of the SOPC and proposes an update. As per its revised draft charter, the objective of the Committee is to provide input on the strategic
and operational planning processes and related budgetary processes of ICANN and Public Technical Identifiers (PTI) that are relevant from a ccTLD and/or ccNSO perspective and to coordinate, facilitate, and encourage the involvement of ccTLD Managers in these
processes. In fulfilling its objective, the Committee should focus on topics relevant from a ccTLD and/or ccNSO perspective, as well as those issues that are of high importance to the ICANN community. After evaluation of the ICANN74 session, the SOPC membership
adopted the amended charter. On 5 August, the final proposed version was circulated among the ccNSO membership and broader ccTLD community, for a final review and request for comments. Since no substantial comments were received by the deadline, the amended
charter was submitted for adoption by the ccNSO Council (Document: item 10 meeting 186 Charter SOPC August 2022).
Decision
The ccNSO Council adopts amended Charter of the SOPC as proposed by the Committee (document: item 10 meeting 186 Charter SOPC August 2022). The Council requests the secretariat to publish the amended charter as soons as possible (after inclusion of date
of adoption by Council), and inform the SOPC Chair and Vice Chair accordingly. This resolution becomes effective upon its publication.
Question for clarifications? none
Move? Stephen
Second? Pablo
Questions on resolution? none
only green ticks
Abstain or object? none
11.
Appointments to Working Groups and Committees
For Decision
This is an administrative resolution. When appropriate, appointments by Council will be combined into one single resolution per month.
Draft resolution
Background
Nigel Roberts (.je, .gg) volunteered to contribute to the work of the GRC. Türkan Sarikaya (.tr) wishes to be appointed as a member of the ccPDP3-Review Mechanism Working Group.
Decision
The ccNSO Council appoints Nigel Roberts as member of the ccNSO Guidelines Review Committee (GRC). The secretariat is requested to take all necessary steps to include him as a member of the GRC, including to inform the group’s
leadership team.
The ccNSO Council appoints Türkan Sarikaya as member of the ccPDP3 Review Mechanism Working Group. The secretariat is requested to take all necessary steps to include her as a member of the ccPDP3-RM WG, including to inform the
group’s leadership team.
Questions for clarification? none
Move? Pablo
Second? Souleymane
Questions on resolution? none
Abstain or object? none
adopted
12.
Update ccNSO Membership
Informational and for Decision
The ccNSO received a membership application by the ccTLD Manager of Austria (.at), nic.at GmbH
Draft Resolution
The ccNSO Council approves ccNSO membership of nic.at GmbH, the ccTLD Manager of Austria (.at), and welcomes nic.at as member 173 of the ccNSO. The chair is requested to formally welcome nic.at. This resolution
becomes effective upon publication.
Questions for clarification? none
Move? Stephen
Second? Javier
Questions on resolution? none
Abstain or object? none
adopted
congratulations and welcome to .at
13.
Update ICANN Board Seat 11 Nomination Process
Informational
The call for nominations for ICANN Board Seat 11 closed on Friday, 5 August 2022, 23.59 UTC. Patricio Poblete has been nominated, and seconded, in accordance with the applicable rules. Patricio is the only nominee. He accepted his
nomination. Council Chair sent materials to ICANN legal for due diligence verifications to start as soon as possible.
Joke: voting starts 8 November
Q&A session with Patricio prior to that
14.
NextGen@ICANN Program
For decision
Background
Draft Resolution
Decision
Seen the limited impact of the Programme for the ccNSO and its members, and in line with related Council decisions from 2020 and 2021, the ccNSO Council decides firstly, not to appoint a mentor to NextGen@ICANN, and secondly, not
to nominate any members to the NextGen@ICANN Selection Committee. The ccNSO Secretariat is requested to inform relevant ICANN staff accordingly.
Chris: seeing the limited impact. correct resolution
Questions for clarification?
Pablo: indeed little impact with the things the ccnso does. however we should seek ways to be involved in things that improve the community as a whole
Alejandra: scare resources. volunteer time to be dedicated to elements that have a true impact.
Stephen: asks Pablo how the ccnso could be contributing to this programme? Which structure?
Pablo: struggled to develop ways with NextGen. firstgen should be aware of the cctld manager of their country.
Move? Pablo
Second? Stephen
Questions on resolution? see comment by Chris
Abstain or object? none
adopted
Jordan: could we work with icann staff on explaining why we made this decision, and work on an opportunity for making it more useful for the ccNSO?
Alejandra: good idea. Action for the OISC
Tatiana: students. they are in their own bubble. might be worth a try. but looking at the effort, not sure whether it is worth the effort. nextgen was criticised even by
its participants. not comparable to icann. taking into account the modalities, not sure it can work.
Alejandra: mentoring, selection committee too much effort. but perhaps some basics are indeed to consider.
Pablo: link between them and their respective TLD operators.
Biyi: closely shares Pablo’s view. Might not be relevant to the ccNSO today. but it's always good to look for people and gain their interest in what we do.
Alejandra: eventually a to do for the OISC.
volunteered in chat to discuss in KL: Pablo, Jordan, Jenifer, Rosemary, Tatiana
15.
Request for nominations for the Planning Prioritization Process for the FY24 Operating Plan and Budget process
Informational and for Decision
Background
The Planning Prioritization Framework V2 is now published on the ICANN Finance and Planning Community wiki workspace here:
https://community.icann.org/display/projfinadhocws/Planning+Prioritization+Framework
The pilot concluded in May 2022 on Board-approved Specific Review recommendations. The community participants in the pilot that were appointed from each SO/AC prioritized the list of recommendations. The proposed Planning Prioritization
Framework Version 2 has not changed from Version 1 as published in February 2022.
ICANN’s planning team now requests each SO/AC to appoint one member and one secondary member to the FY24 Planning Prioritization Group, by 25 August. Given that the FY24 Prioritization exercise follows so soon after the conclusion
of the pilot, ICANN org believes that the most effective and efficient manner of proceeding with the FY24 Prioritization exercise is to continue to rely on the same community members who participated in the pilot. Meetings will be held in September and early
October 2022, to permit ICANN org to receive input for the development of the Draft Operating Plan and Budget which is scheduled for public comment by 14 December 2022. The scope of activities to be included in this prioritization process as a step in the
annual planning process, are Board-approved implementation work, such as PDP recommendations, Specific Review recommendations and the implementation of other non-policy and advice work.
Draft Resolution
Decision
The ccNSO appoints Chris Disspain as member, and Irina Danelia as secondary member, to the FY24 Planning Prioritization Group. The ccNSO Secretariat is requested to inform the SOPC and relevant ICANN staff about Chris and Irina’s
appointment by the 25 August deadline.
Questions for clarifications? none
Move? Jordan
Second? Tatiana
Questions on resolution?
Abstain or object? Chris abstains. Irina votes for Chris’ appointment.
approved.
16.
Change of 2022 Rules to reflect amendment of Article 10 and Annex B to include IDN ccTLDs in the ccNSO
For decision
Background
The changes of Article 10 and Annex B of the Bylaws have become effective. As a result the recently adopted Rules need to be updated. The GRC presented the proposed changes to the community at ICANN74. As next step the 2022 Internal
Rules need to be adopted by both Council and Membership. The change mechanism is described in section 4.1 of the Rules.
“First, and after consultation of the ccNSO Membership, at least 14 members of the ccNSO Council must vote in favor to adopt the proposed amendment of the Rules.
Following the adoption by the ccNSO Council, the proposed amendments to the Rules must be circulated to all Members and the Members vote shall start no sooner than twenty‐one (21) calendar days and no later than twenty-eight (28)
calendar days after the date the proposed amendments have been circulated to the Members.”
The ccNSO secretariat, after consulting the GRC, circulated the updated Internal Rules to the ccNSO Membership and sought feed-back. Deadline for this was 12 August 2022 (23:59 UTC). Council is now in a position to adopt the amended
Rules, and to call for a membership vote, starting post ICANN75.
Draft Resolution
Decision
The ccNSO Council adopts the proposed amended internal Rules for the ccNSO. The ccNSO Council adopts the timeline as proposed for the ccNSO membership vote, in line with the change mechanism of the April 2022 Internal Rules. The
ccNSO Council requests the Secretariat to publish the timeline and start the procedure accordingly. The ccNSO Council appoints ccNSO Secretariat member Joke Braeken as Voting Process Manager to manage the electronic voting process on the new set of Rules
for the ccNSO, as accepted by the ccNSO Council at this 186th meeting.
Question for clarifications? none
Move? Chris
Second: Stephen
Question on the resolution?
AF region: Ali: in favour , Biy: in favour, Souleymane: in favour
AP region: Ai-Chin: in favour, Jiankang: in favour, Jordan: in favour
EU region: Chris: in favour, Irina: in favour, Nick: in favour
NA region: Pablo: in favour, Sean: in favour, Stephen: in favour
NomCom: Javier: in favour, Marie-Noémi: apology, but she said via email she was in favour, Tatiana: in favour
LAC region: Demi: not available, Jenifer: in favour, Alejandra: in favour
approved
17.
Update regarding Board’s Consideration on ccPDP3-retirement policy
Informational
The ccNSO Council recently clarified its position regarding the exclusion of ccTLD policy related matters from ICANN's Reconsideration and Independent Review Processes. Council sent a letter, following a question from
ICANN Legal concerning the proposed ccTLD retirement policy (ccPDP3-RET), aiming to ensure that the Board's consideration process of the proposed retirement policy will be completed.
At the July meeting, Council decided to include this as a standing update on the agenda, until the proposed policy is adopted by the Board. Patricio, in his
capacity as Chair of the Board Ad Hoc Group. Board is on a 3 week break. but approved the draft resolution and rationale and submitted it to the full board for its consideration. On 23 aug there will be an info session for the board on the proposed policy
and resolution. vote during the next board meeting. come for a vote at the public meeting during ICANN75. I hope you join us to celebrate, as I have every expectation that it will be approved by the board. The letter from the council regarding the carve-out
removed the final obstacle. concerns where the RM would not be available right away. with advice of icann legal, risk was deemed to be minimal. the risk of having a cctld that has to be retired without a policy is much higher.
charter of the ad hoc group has 2 tasks :
Stephen: Thank you for the news and the report. apologies for ICANN74, not personal.
Biyi: apologies, missed part. frustrations with the process expressed by some in the past. Is there a way to have a published timeline from the board? better
manage expectations?
Patricio: good idea. part of the mechanism of how to handle future ccPDPs.
Stephen: agrees with the lack of transparency. communication with the community needs to be better.
18.
ICANN75
Informational
Note: all sessions marked with an asterisk will have simultaneous interpretation (EN, FR, ES). The schedule below is tentative, and subject to change.
a.
ccNSO Council
i.ccNSO Council Prep Meeting (Sunday, 18 September | block 2 | 02:30-04:00 UTC)
ii.ccNSO Council meeting* (Thursday, 22 September | block 4 | 07:00-08:00 UTC)
iii.no Council Workshop at ICANN75
b.
Bilateral meetings
i.Informal joint session between leadership teams of ccNSO DASC & GAC PSWG (prior to ICANN75, TBC)
ii.Joint session: ccNSO & GAC (Tuesday, 20 September | block 3 | 05:15-06:30 UTC)
Proposed topics: updates and reports on progress by DASC, ccPDP3-RM and ccPDP4-IDN
iii. Joint session: ccNSO & ICANN Board* (Wednesday, 21 September | block 1 | 01:00-02:00
UTC)
·
Proposed topic by the Board: What collaborative actions should the Community, Board and Org be undertaking to further progress achieving our strategic priorities?
Alejandra: what do you think are strategic priorities?
Jordan: what do you think they mean by that? strategic priorities from the 5Y StratPlan
Alejandra: that contains objectives but not priorities
Jordan: see Chris and Irina’s appointment. ask them to explain the priorities, so we could work out comments.
Alejandra: please all think about a possible answer.
Jordan: t would do no harm for Alejandra to give an informal heads up to Maarten that it would be nice to share the board’s view of what priorities are, in advance of the meeting - maybe in
a blog post?
small group to convene to work on an answer. (volunteered: Chris, Jordan, Stephen)
·
Proposed topic(s) by the ccNSO:
to be completed
Alejandra: what do we mean? what do we really want? if we want to involve the community, it takes time. have consultations etc. perhaps after KL discuss this ourselves. streamline
what the ccnso does, and then give feedback to community on efficiency and effectiveness
small team of volunteers: Tatiana, Sean, Pablo
c.
ccTLD relevant sessions
i.ccNSO webinar for newcomers (Tuesday, 30 August | noon UTC)
ii.ccNSO Council election webinar 1/2 (Tuesday, 6 September | 17 UTC)
ccNSO Council election webinar 2/2 (Thursday, 8 September | 6 UTC)
iii. Tech Day (Monday, 19 September | block
2,3,4,5 | 01:00-17:30 UTC)
iv.IANA and CSC update to ccTLDs* (Wednesday 21 September | block 4 | 07:00-08:00 UTC)
v.ccNSO Members Meeting sessions
·
Policy update ccPDP3* (Tuesday, 20 September | block 1 | 01:00-02:00 UTC)
·
ccTLD News Session 1/2 on geographical indications* (Tuesday, 20 September | block 2 | 02:30-04:00 UTC)
·
ccNSO & Universal Acceptance* (Wednesday, 21 September | block 3 | 05:15-06:30 UTC)
·
ccNSO Governance session* (Wednesday, 21 September | block 4 | 07:00-08:00 UTC)
·
ccTLD News Session 2/2* (Wednesday, 21 September | block 5 | 08:30-09:30 UTC)
·
ccNSO informational meeting (Tuesday, 20 September | block 5 | 08:30-09:30 UTC)
vi.ccNSO Committee and Working Group Meetings
·
DASC (Saturday, 17 September | block 4 | 07:00-08:00 UTC)
·
IGLC (Saturday, 17 September | block 5 | 08:30 - 09:30 UTC)
·
ccPDP3- Review Mechanism:
Sunday, 18 September | block 3 | 05:15-06:30 UTC
Tuesday, 20 September | block 5 | 08:30-09:30 UTC
·
ccPDP4-IDN (Sunday, 18 September | block 4 | 07:00-08:00 UTC)
·
SOPC (Sunday, 18 September | block 5 | 08:30-09:30 UTC)
·
Technical WG (Sunday, 18 September | block 1 | 01:00-02:00 UTC)
·
MPC ICANN75 wrap-up (Thursday, 22 September | block 5 | 08:30 - 09:30 UTC)
vii. Plenary & other cross-community session(s)
·
ICANN Prep Week
(6-8 September. The Prep Week schedule will be published on 22 August 2022.)
·
Plenary session:
Internet Fragmentation, the DNS & ICANN (Wednesday, 21 September | block 2 | 02:30-04:00 UTC)
·
Q&A with ICANN Executives (Monday, 19 September | block 2 | 02:30-04:00 UTC)
·
Geopolitical Forum (Thursday, 22 September | Block 3 | 05:15-06:30 UTC)
Jordan: send calendar invitations for the key sessions?
Bart: yes
Stephen: Do we need to register for each of the sessions?
Kim: no. 1 meter distance, and bigger rooms
19.
Next Council Meetings
·
Meeting 187, 22 September | block 4 | 07:00-08:00 UTC (ICANN75)
·
Meeting 188, 20
October - 12:00 UTC
·
Meeting 189, 17 November - 18:00 UTC
·
Meeting 190, 15 December - 12:00 UTC
20.
AOB
Chris: see exchange on Council list regarding the bylaws (section 8) regarding the issue of a member of the NomCom committee not being on a council or a body which the nomcom is appointing members
to. e.g ccnso board or at large. Forgot that rule existed. thought about it carefully. acknowledge that this happened in the past. no objections at the time. but my interpretation of the bylaw is that it would mean that I would not be able to re-stand for
a council position. The right way to do, is to make a decision one way or the other. nominations start 14 september. nomcom has not started yet, but will do in KL. The sensible thing to do is to withdraw from the NomCom. find an alternative appointment in
a timely manner. i would like to re-stand for council, for a new term to start in march.
Alejandra: Nominating Committee Bylaws:
https://www.icann.org/resources/pages/governance/bylaws-en/#article8
Section 8.8. INELIGIBILITY FOR SELECTION BY NOMINATING COMMITTEE
No person who serves on the Nominating Committee in any capacity shall be eligible for nomination by any means to any position on the Board or any other ICANN body having one or more membership
positions that the Nominating Committee is responsible for filling, until the conclusion of an ICANN annual meeting that coincides with, or is after, the conclusion of that person's service on the Nominating Committee.
Stephen: I brought this up. does not understand the language. Pablo served on NomCom under the same bylaw.
Chris: not suggesting that we should not seek clarification. but timing wise it would be fairer to step down from NomCom now, and not once the work started. the fact that it has happened (Pablo),
is not relevant to the interpretation of the bylaw.
Stephen: apologies for the difficult position. respect your judgement
Sean: I think Chris is taking a route that gives us the time to address the language both on the ask and changes that may be required
Tatiana: go for the second person on the list? there was more than one applicant
Bart: will check. new call for volunteers does not take long either. is the 2nd candidate still available?
Jordan: intent of the heading. drafting mistake. appointment by NomCom
Pablo: discussion in NomCom. they all agreed that the way they interpreted it was closer to what Jordan described. understands the importance of clearing the air up
Tatiana: (not only Board, but everything else NomCom is responsible for). But I agree with my lawyer's hat that it is so much open to interpretation (not only Board, but everything else NomCom
is responsible for). But I agree with my lawyer's hat that it is so much open to interpretation
Alejandra: early welcome to Olga. new NomCom appointee to ccNSO Council
Chris: identity digital (previously donuts) is sponsoring the ccnso party. limited invitations. at the mandarin oriental poolside. 18:30-22:30. BBQ.
21.
Closure
Thank you all.
Joke Braeken
joke.braeken@icann.org