NOTES | ccNSO Council ICANN76
ccNSO Council Meeting *
Thursday, 16 March 2023 | 18:15-19:30 UTC (13:15-14:30 local)
Join meeting and consult session recordings | Room: Auditorio (ccNSO)
—
1.
Welcome and roll call
AF region: Ali, Biyi, Souleymane
AP region: Ai-Chin, Jiankang, Jordan
EU region: Chris (Apology), Irina, Nick
NA region: Pablo, Sean, Stephen
NomCom: Javier, Olga, Tatiana
LAC region: Demi, Jenifer and Alejandra
Quorate? yes
Topics on agenda today:
2.
Relevant Correspondence
(https://ccnso.icann.org/en/about/statements.htm)
letter to the GAC is required under the policy development process
According to the Bylaws the Board will also have to ask the GAC for opinion or advice, after they have received the ccNSO policy.
3.
Minutes & Action Items
2.
Action items and/or To-Do’s:
Action Item 192-01:
ccNSO appointed liaison to the GNSO: informational webinar followed by call for volunteers.
Deferred to Post ICANN76
Action Item 192-02:
Triage committee is requested to reach out to various committees and working groups to improve planning and scheduling. The committees and working groups are requested to take note of suggestions
from the workshops Ongoing
4.
Intermeeting Decisions (since meeting 192, 16 February 2023
·
Appointment of additional members to IGLC:
o
Beth Njau (.ke, KENIC)
o
David McAuley (.cc, Verisign)
Item 5-10 Updates and Q&A
Note that CSC RT has completed its work. Council can expect Final Report shortly,
on agenda for discussion and adoption for the April meeting
5.
Update ECA, CSC, CSC RT
6.
Update WGs taken (written updates or taken from the meeting)
1.
IGLC
(meeting during ICANN 76)
2.
GRC
(meeting during ICANN 76)
3.
SOPC
(meeting during ICANN 76)
4.
OISC (no meeting since ICANN 74, travel funding subgroup met)
5.
TLD-OPS
(meeting during ICANN 76)
Met on sunday. Looking for volunteers.
Bart: call for volunteers needed?
Ali: 2 potential candidates. Chair will follow-up
Bart: by April meeting, come up with 2 candidates. And then appoint them?
Secretariat will reach out to Jacques and Regis for the preferred method for finding candidates
6.
DASC
(meeting during ICANN 76)
7.
Technical WG
(meeting during ICANN 76)
8.
MPC (meeting during ICANN 76)
9.
Triage Committee
10.
IRP Panel selection
11.
CCG WS 2 Implementation
12.
Prioritization Framework group (recently announced new round of discussions)
7.
Updates Update IDN ccPDP4
(taken from the meeting)
8.
Update liaisons (written updates)
1.
Update ALAC Liaison
2.
Update GNSO Liaison (see item 13) Note This reference to item 13 is incorrect
Bart: regarding ccNSO appointed liaison to GNSO. Call for volunteers: will happen after the icann meeting
9.
Update ccNSO Website redesign
Deferred to next meeting
10.
Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat
Invitation to participate in Trend exercise, together with SOPC. Date has to be set, expected to be early April 2023. invitation also sent to SOPC.
Administrative matters for discussion and/or decision during the meeting
(items 11 – 15)
11.
Chair and Vice-Chair Election
Alejandra explains procedure.
Nominate? Sean nominates Alejandra
Second? Stepen seconds her nomination
Accept nomination? Yes
Other candidates ? no
In favour? Hands in zoom
Against? none
Abstain? None
Alejandra to continue in her role as Chair of the ccNSO Council
Resolution
Move? Tanja
Second? Stephen
Comments regarding resolution?
None
All in favour
Jordan gives the floor back to Jordan
Nominate? Ai-chin nominates Jordan, Stephen nominates Biyi
Second? Javier seconds Jordan, Ali seconds Biyi’s nomination
Accept nomination? Jordan: Yes, Biyi: Yes
Mover for both resolutions? Sean
Second? Tatiana
Comments regarding resolution?
In favour? All in favour
Against? none
Abstain? none
12.
Roles and responsibilities of Councillors
For information and decision following the 12 March 2023 Council Workshop
We started developing succession planning, time ago. During ICANN76 Council prep meeting, we agreed to review all existing roles of Councillors and ccNSO appointees to other
communities
Aim: understand the roles, understand if they are needed currently and in future. Also agreed to look at the capabilities required per role and then start identifying potential
future candidates for roles critical to the ccNSO.
During the workshop we started the review of the current roles of Councillors, and concluded this needed additional work. does not make sense to assign roles and responsibilities
for the upcoming year, but continue the current assignments at least until ICANN77.
Alejandra, Irina Danelia, Sean Copeland, Biyi Oladipo, and Chris Disspain to continue the review of the current roles and responsibilities in key areas for the ccNSO and present
their findings during a Council session during ICANN77.
Move? Jenifer
Second? Ali
Questions or comments? none
In favour?
Against? none
Abstain? None
13.
Updates & Adoption ccNSO Internal Procedures
(taken from the meeting)
no role yet for Council
1.
Update Guideline: ccNSO SoI and CoI
2.
Update Implementation policy
observations from the discussions on Tuesday and with the Board members?
expect any immediate steps from the Council?
14.
Update Charters, Terms of Reference
Recurring until review of all Charters and Terms of Reference has been completed.
No updates pending
15.
Appointments to Working Groups and Committees
Secretariat to launch a webinar to launch the call for expression of interest. Previously, ccNSO was required to appoint at least a representative from a ccTLD who is not a member of the ccNSO.
This requirement has been removed.
Adding Tatiana to GRC
Olga requested to be appointed to DASC. online decision took place, but no subscription to mailing list to date (Bart: admin matter)
Move? Pablo
Second? Olga
Questions or comments? none
In favour?
Against? none
Abstain? none
Items
for discussion and/or decision during the meeting (items 16-19)
16.
Council Deliberations and decision on recommended policy for a review mechanism (ccPDP3 Review Mechanism)
Process started in 2010:
Delegation and redelegation working group. (DRD)
In the DRD report several gaps and issues were identified in the IANA policies and practices with respect to ccTLDs and a need to address them. It is the reason why the ccNSO
was created 20 years ago.
Issues:
=> addressed in the Framework of Interpretation, as adopted in February 2015.
In 2014 the discussions around the IANA Stewardship Transition started, and became the main focal point of the ccNSO and others. As a result of the Transition, specifically
Workstream 1 of the accountability group, the Independent review procedure was restructured, however the ccTLD community made the choice to exclude all disputes and claims with respect to the delegation and redelegation of ccTLDs form this process, with the
commitment to develop an alternative review mechanism acceptable for the ccTLD community.
Only after the Transition was successfully completed, the ccNSO could re-focus its attention on the main policies with respect to ccTLDs.
In 2017 the Council launched ccPDP3, which resulted first in the retirement policy. This policy was adopted by the ccNSO in 2021 and by the Board in September 2022. We are now
at the point to finalise the policy to introduce a review mechanism for specific disputes relating to ccTLDs. If this policy gets adopted by the ccNSO and the Board we will have come full-circle and all the issues identified by the DRD WG will have been addressed.
Stephen: refers to specification by John Postel. Review Board to be in place. Thanks to WG members and staff.
See section 10 and 11 of Annex B of the ICANN Bylaws.
ccNSO Council is expected to decide whether it will make a Council Recommendation supporting the proposed policy to introduce a review mechanism pertaining to IFO decisions
on the delegation, transfer, revocation and retirement of ccTLDs.
AF region: Ali, Biyi, Souleymane
AP region: Ai-Chin, Jiankang, Jordan
EU region: Chris (Apology), Irina, Nick
NA region: Pablo, Sean, Stephen
NomCom: Javier, Olga, Tatiana
LAC region: Demi, Jenifer and Alejandra
Move? Irina
Second? Nick
Alejandra reads resolution
Questions or comments?
Bart: why am I not included yet? First step. Not done yet. I am still the issue manager. Also, i do not include myself
The WG will not be closed just yet. If there is a request by the board, it is wise to keep the group.
In favour
Against
Abstain
AF region: Ali: Y, Biyi: Y, Souleymane: Y
AP region: Ai-Chin: Y, Jiankang: absent, Jordan: Y
EU region: Chris: Y, Irina: Y, Nick: Y
NA region: Pablo: Y, Sean: Y, Stephen: Y
NomCom: Javier: Y, Olga: Y, Tatiana: Y
LAC region: Demi: Y, Jenifer: Y and Alejandra: Y
Draft Resolution
Background
In December 2015, the ccNSO Council discussed the need to launch a formal ccNSO Policy Development Processes to address the lack of policy with respect to retirement of ccTLDs and to introduce a Review Mechanism on
issues pertaining to the delegation, transfer, revocation, and retirement of ccTLDs. This discussion was grounded in the need to ensure the predictability and legitimacy of decisions with respect to the delegation, transfer, revocation, and retirement of
ccTLDs.
In March 2017, and in accordance with Annex B section 3 and 4 of the ICANN Bylaws, the ccNSO Council decided - among others – to initiate the third (3rd)
ccNSO Policy Development Process with the initial focus on developing a policy for Retirement of ccTLDs (Part 1), and only after the substantive work on that topic would have been concluded, focus on the development of policy recommendations for a Review Mechanism
pertaining to decisions on delegation, transfer, revocation and retirement of ccTLDs (Part 2).
In April 2017 the Retirement Working Group (WG) started its work. The ccPDP3 Review Mechanism WG began its work in March 2020, after the Retirement WG completed its Initial Report.
As it became apparent that the envisioned advantages of combining the two topics into one (1) ccNSO Policy Development Process have become obsolete, both the Retirement and Review Working Groups, supported by the community
at large, proposed to separate Part 1 (Retirement) and Part 2 (Review Mechanism). On 04 June 2021 the ccNSO Council decided to split up ccPDP3 accordingly and the decision became effective on 11 June 2021.
As stated the RM working group began its work in March 2020, and met 63 times to date (as of March 2023). This work included the participation of PTI staff at all and ICANN Legal staff at a number of these meetings.
The RM working group presented updates to the community on its work at all ICANN meetings since ICANN 71, including seeking feed-back on the proposals from the ccTLD community at the ICANN 71, 74 and 75 sessions.
Presentations to the community, including to the intersessional update in May 2021 and at ICANN75 to the GAC, can be found on the wiki-space of the group.
The RM held a formal public comment on its proposed policy from 29 November 2022 to 26 January 2023. To introduce the Initial Report to the broader community a webinar was held, which was attended by members of the
ccTLD community and members of the GAC. Based on the submissions from the public comment the WG did not identify any issues, questions or proposals that would require a need to modify the proposed policy.
According to its charter the RM WG has the following goal:
“The goal of the working group (WG) is to report on and recommend a policy for a review mechanism with respect to decisions pertaining to the delegation, transfer, revocation and retirement of the delegated Top-Level
Domains associated with the country codes assigned to countries and territories listed in the ISO 3166-1 and within the framework of the ccNSO Policy Development Process.”
The CCPDP3WG-RM charter also listed the following questions:
·
Which decisions and/or actions should be subject to a review mechanism?
·
Whose decisions and/or actions should be subject to a review mechanism?
·
Should a Review Mechanism be open and applicable to all ccTLDs?
·
What will be the result / scope of the review decision?
·
What powers will be bestowed upon the review panel?
·
Who will have standing at a review?
·
What are the grounds (for a review)?
In addition, in July 2022, the ccNSO Council requested the Working Group specifically recommend and/or advise on the need for clarification of the scope of ICANN Bylaws Sections 4.2 (d) (i) and 4.3 (c ) (ii).
On 03 March 2023 the Issue Manager submitted the recommended Review Mechanism Policy to the ccNSO Council for their consideration and decision-making The Proposed Policy is contained in the Final Paper of the Review
Mechanism Working Group sections 2-6 and section 9. As required under Annex B of the Bylaws the Chair of the ccNSO requested the GAC to provide an opinion or advise.
Decision
The ccNSO Council adopts the Recommended Policy as contained in the Final Report of the ccPDP3 Review Mechanism Working Group section 2-6 and section 9 and as submitted to the Chair of the ccNSO Council on 03 March
2023. The adopted recommendations shall be conveyed to the Members of the ccNSO as the Council Recommendation to vote upon.
The ccNSO Council Recommendation addresses the issues pertaining to the introduction of a Review Mechanism as identified in February 2017 as adopted by the ccNSO Council in March 2017.
The Issue Manager is requested to compile the Members Report taking this resolution into account.
In accordance with the adopted timeline the Members vote on the Council Recommendation will start on Tuesday 18 April 2023, 00.01 UTC and end 09 May 2023 at 23.59 UTC. The ccNSO Council appoints Joke Braeken as
voting process manager, and requests her to take all steps necessary to organize the members vote and report on the result of the ccNSO members vote to Council at its May 2023 meeting.
The ccNSO Council wholeheartedly thanks the members and other participants of the Review Mechanism Working Group for their hard work and prolonged effort to and propose the review mechanism and conclude the ccPDP3
policy endeavor. In particular the Council thanks the chair and vice-chair of the working group Stephen Deerhake (.as) and Eberhard Lisse (.na) and Bernard Turcotte, Kimberly Carlson and Joke Braeken for their unwavering support and hard work. The secretariat
is requested to inform the WG membership and broader community.
17.
Adoption Roadmap ccNSO & UA and next steps
various stakeholders requested the ccNSO Council to initiate the discussion on the role of the ccNSO with respect to Universal Acceptance.discussion on the potential role of the ccNSO was discussed
with the community in Kuala Lumpur. 2 workshops. Yesterday proposals presented to community.
Observations:
Biyi: people approached Biyi to be part of a committee.
Alejandra: other questions or comments regarding this topics
Bart: suggestion is to take a decision online. Ad hoc group will first be asked to determine the ToR by the committee. By May, the call for volunteers can follow.
Council agrees to take an online decision
18.
Start 360-review of Councillors
January 2023: Council adopted its internal 360 review procedure.
·
Ali Hadji Mmadi
·
JianKang Yao
·
Iriana Danelia
·
Jennifer Lopez
·
Sean Copeland
·
Javier Rua – Jovet, NomCom appointed
Bart as feedback process manager. Review completed by ICANN77
Request to correct Irina’s and Jenifer’sname in the resolution
Move? Jordan
Second? Irina
Questions or comments? none
In favour
Against: none
Abstain: Sean
19.
ICANN76
WSIS+20 review. Jordan requests to make sure it is on the agenda at national level. Get involved in IGLC. Also GE team at ICANN will soon share report.
20.
AOB
none
21.
Next Council Meetings
o
Meeting 194, 20 April – 18:00 UTC
o
Meeting 195, 18 May – 12:00 UTC
o
Meeting 196, June - ICANN 77
TBD
o
Meeting 197, 20 July – 21:00 UTC
o
Meeting 198, 17 August – 12:00 UTC
o
Meeting 199, 21 September – 18:00 UTC
o
Meeting 200, October – ICANN 78
TBD
o
Meeting 201, 16 November – 12:00 UTC
o
Meeting 202, 21 December – 21:00 UTC
22.
Thank you and Welcome
Thank you for the warm welcome in Mexico, and thanks for the organisation of the ccnso cocktail
Thank you to Souleymane, welcome to Molehe
Thanks to WG/C, secretariat, interpreters, all participants
23.
Closure
Thank you all
= = =
ICANN76 LINKS TO BOOKMARK NOW
• ccNSO Schedule
https://community.icann.org/x/8IMFDQ
• ccNSO Session Highlights
https://community.icann.org/x/kYYFDQ
• Tech Day