NOTES | ccNSO Council Meeting 194, 20 April 2023, 18:00 - 19:30 UTC
Table of contents
Meeting with Sally Costerton
1
Intro by Alejandra. Roll call: after conversation with Sally.
Heads up about decisions we need to make today.
CEO and President ICANN (18.00-18.30 UTC)
open Q&A and casual conversation.
Sally: We have been involved in the last 4 weeks with UA day. This has gone better than expected. ccTLDs have been instrumental. global campaign mobilised is not easy, and has taken a long time.
80 community groups applying for an event. We approved 55. It is a dry topic. Common sense. but people do not know. Example of a Chinese lady not being able to write in english.
Countries : Nigeria, Philippines, India, China, Indonesia. community driven. Multi-stakeholder.
Next round: strategies focusing on countries being locked out of domain access.
With the Board in Cancun, a different spirit. Willingness to try. deliverability of the board resolutions.
Alejandra: ccTLDs can be helpful. ccTLDs have been working on this a long time. The ccNSO consists of ccnso members and Council. We work in a framework where we try to make available a platform
for knowledge sharing. We also have a PDP task, but that is narrow. Sharing experiences is the core. Motivitating and inspiring. Invite to Biyi to speak how ccTLDs can strengthen the multistakeholder model
Biyi: appreciates the items Sally mentioned. ccTLDs within the icann ecosystem. In strengthening the MSM, ccTLDs are strategic partners. They are closely linked to their local communities. ICANN
should rely on that. Reference to UA and the role of ccTLDs. We developed a roadmap to strengthen the UA discussions around ccTLDs. grassroot. Build from there. Another thing of interest is the Coalition of Digital Africa. conversations we had. In setting
up the program, initially, the structure was away from the people running it. discussions were had with governments etc, but not with ccTLDs. Rather, working with ccTLDs would have strengthened the model. It works better if we cooperate.
Sally: agree. thanks for the feedback on ccTLD engagement. We just hired someone for secretariat in Nairobi. project team should proactively engage with the ccNSO. Being inside the coalition,
and helping inform.
Very much agrees with the critical role of ccTLDs in their countries. passionate advocate of the regional engagement teams. anchor partners in any country or region.
Stephen: will you apply for the CEO role?
Sally: i do not know. have not seen the job description. supports the listening sessions by the Board.
Jiankang: thank you for introducing the UA work. Has ICANN plans to do outreach to EAI and IDN work? email providers in the world do not all support EAI. more outreach is needed.
Sally: example microsoft. legacy systems are the most difficult ones. Talk to infrastructure providers for scripts to be accepted. what we did in India, was having major dialogues with trade
associations. that worked very well. I met the CEO of NASCOM. priority for me to have those kinds of discussions early. appreciates the feedback on how work progresses.
Sally: stressing the regional partnership. love feedback - such as the one by Biyi - how can we do more with the ccTLDs to leverage local/national knowledge base. Example AUDA. Rosemary and
team put lots of effort in engagement. ccTLDs and TLD operators, as we go into the next round - even if applications were successful, not all applications go through. sometimes because of lack of knowledge how to run a registry. ccTLD business model is its
own thing. Varies from country to country. ccTLDs might want to be backend providers. would love to keep that idea on the agenda for the next months. how would the ccTLDs be interested in being part of the next round. the TLDs need to work, and ccTLDs have
experience.
Alejandra: in terms of ccTLD outreach, ccNSO is the right place. they know the actors in their own ecosystem. Whether ccTLDs want to have a say in how to approve the AGB, we have not discussed/consulted
yet.
Sally: As we develop the outreach and engagement plans, let’s discuss. talk to ccTLDs about the plans. keep as a live issue. Thank you for the time.
Alejandra: final words by Stephen?
Stephen: icann’s legitimacy stems from the participation of ccTLDs. do not forget that.
Sally: agree. refers to Rod. early warning system
Javier: diversity of governance models of ccTLDs. The legitimacy is transversal. up down and sideways.
Sally: that is the superpower. working together in events and engagement opportunities.
Meeting is quorate
2.
Minutes & Action Items
no action items pending
a.
Minutes Meeting 193: from the transcript
b.
Action items and/or To-Do’s
3.
Intermeeting Decisions (since meeting 193, 16 March 2023)
no comments or questions
4.
Update Charters, Terms of Reference
Jordan: refers to spreadsheet with the overview of the incoming requests for decision. triage to make decisions in more streamlined manner. Triage can now makes a decision, but if there is broad
attention required or consultation, Council will be involved. merely to make “simple” decisions easier.
For decision: updated charter Triage Committee
Questions or comments on topic? none
Move? Sean
Second? Pablo
Questions or comments on resolution?
Abstain? none
Against? none
All in favour
5.
New: Intermeeting decisions Triage Committee
New agenda item, standing item moving forward
Note item
10-2023: Given the importance of Subpro and impact on ICANN community, the Council is requested to confirm the Triage committee decision. See email on Council mailing
list.
Any questions or concerns?
Green ticks only.
Javier: I abstained. I was part of WT5.
General overview Triage Committee decisions:
https://ccnso.icann.org/en/about/council/decisions/2023.htm
Do you like this format for the intermediate triage decisions?
Pablo: can we ask clarifications?
Alejandra: yes. Triage keeps a record.
Pablo: nice if we could get context
Alejandra: link would be helpful
6.
Application of ccNSO membership by National Telecom Regulatory Authority, the (IDN) ccTLD Manager for .Egypt (xn--wgbh1c / مصر)
For Decision
NTRA, IDN ccTLD manager Egypt, applied for ccNSO membership. important milestone in the 20 years of ccNSO history: first IDN ccTLD manager
ASCII ccTLD manager and IDN ccTLD manager for Territory of Egypt will need to appoint an emissary. (no impact on current ccPDP3-RM vote)
Questions or comments on the topic?
Chris: suggestion. assuming we vote in favour. it is the 1st one. you should write tot he Board to tell them this happened. A letter to the board is a public letter. bylaw change has led to the 1st application.
let them know
Alejandra: agree
Stephen: agree with Chris. Assuming that this does not have effect on quorum requirement for ongoing vote?
Alejandra: indeed. no impact on quorum or voting.
Javier: agrees with Chris. transnational legitimacy of the ccTLDs.
Pablo: who to vote?
Alejandra: if there are 2 members from the same territory, they need to appoint an emissary
Joke: The ICANN Bylaws (section 10.4 (e)), specify that in the event
there are two ccTLD managers from the same Territory as ccNSO members, the two ccTLD managers are to appoint one of the Representatives from among the respective ccNSO members to serve as the Emissary to vote on behalf of the ccNSO members from that Territory.
The Bylaws further specify that “during any period in which an Emissary is not appointed, the ccTLD manager that has been the member of the ccNSO for the longest period is deemed to be the Emissary for that Territory” and “The ccTLD managers within each
Territory may define the process to determine how their respective Emissary's vote is determined.”
Move? Chris
Second? Sean
Questions or comments on resolution?
Abstain? none
Against? none
All in favour
Congratulations to the first IDN ccTLD manager joining the ccNSO
Javier: is NTRA the entity with Manal as Director?
Alejandra: yes.
7.
Adoption Final Report 2nd Customer Standing Committee Effectiveness Review
Sean: Same template as first review, plus one additional question. CSC functions effectively. Nonetheless, recommendations to address some issues, to ensure CSC remains effective in the long
term. Recommendations:
Both ccNSO and GNSO Council need to support the recommendations to become effective. GNSO Council also meets today.
Questions or comments on topic? none
Move? Demi
Second? Ali
Questions or comments on resolution? none
Abstain? Sean
Against? none
otherwise green ticks. resolution passed
8.
Update Councillors 360-review
Start the 360 review process. See emails from Bart next week. Closure: 18 May
No self-evaluations. Results anonymous and confidential. will be compiled by Bart and Alejandra. will only be shared with the Councillors. if NoCom appointed councillors agree, results could be shared with NomCom
9.
Updates ccPDPs
(written update)
a.
Update ccPDP3 - Review Mechanism -
Membership voting
Joke:
The decision-process by the ccNSO membership formally kicked off. ccNSO Members, via their emissaries, can now vote on Council’s recommendation to adopt the proposed policy on a review mechanism for ccTLDs.
Following a heads up to the community, the ballots were distributed to the ccNSO membership on 17 April and voting started as of 00:01 UTC on Tuesday, 18 April. Voting closes 9 May (23:59 UTC). See
https://ccnso.icann.org/en/announcements/announcement-2-17apr23-en.htm
At least 50% of the membership needs to vote (87 members), and 66% of the votes cast need to be in favour, for the first round of voting to be valid. To date: 41 votes cast.
Voting happens electronically, and is anonymous. This is a warm invite to please vote, and invite your peers to do so too. For any questions regarding voting or eligibility, please contact me.
Stephen: please vote
Alejandra: reach out to friends and colleagues! voting is easy, and we need the votes and hopefully a positive outcome.
b. Update IDN ccPDP4 (written update)
10.
Update ECA & CSC
11.
Update WGs
(written updates)
a.
IGLC
b.
GRC
c.
SOPC
d.
OISC (no meeting since ICANN 74, travel funding subgroup met)
e.
TLD-OPS
f.
DASC
g.
Technical WG
h.
MPC
i.
Triage Committee
j.
IRP Panel selection
k.
CCG WS 2 Implementation
l.
Prioritization Framework group (no meeting since last update)
12.
Update liaisons (written updates)
a.
Update ALAC Liaison
b.
Update GNSO Liaison
(see call volunteers and invite webinar:
https://ccnso.icann.org/en/announcements/announcement-19apr23-en.htm )
c.
Update UASG Liaison
13.
Update ccNSO Website redesign
14.
Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat
15.
Updates & Adoption ccNSO Internal Procedures
a.
Update Guideline: ccNSO SoI and CoI
b.
Update Implementation policy
16.
Appointments to Working Groups and Committees
17.
ICANN77
Virtual Council prep call
Virtual Council workshop: roles and responsibilities
No joint sessions
Council meeting on Thursday, 15 June
Kim: roundtable SO/AC chairs on Sunday, later in the day
18.
AOB
2 items:
1/ NomCom - Appointment of Board Members
We will need a drafting team for a Council Statement and will request for volunteers after the call.
2/ ccNSO appointed delegate to NomCom: term end. request by ICANN org to appoint a delegate. Council will be asked to take an on-line decision re timeline etc.
19.
Next Council Meetings
a.
Meeting 195, 18 May – 12:00 UTC
b.
Meeting 196, June - ICANN 77 TBD
c.
Meeting 197, 20 July – 21:00 UTC
d.
Meeting 198, 17 August – 12:00 UTC
e.
Meeting 199, 21 September – 18:00 UTC
f.
Meeting 200, October – ICANN 78 TBD
g.
Meeting 201, 16 November – 12:00 UTC
h.
Meeting 202, 21 December – 21:00 UTC
20.
Closure of formal meeting
Thank you all.
No recording, no notes. Observers (non-Council members) are welcome to stay.
This informal discussion is to prepare for a meeting between the Executive Search Committee of the ICANN Board and the ccNSO leadership team, scheduled for Friday 28 April, noon UTC. Topic: discuss
the requirements for the new ICANN CEO & President. Councillors can attend on 28 April, but only as observers.
Joke Braeken
= = =
ICANN77 links to bookmark now
https://community.icann.org/x/IQM5Dg
https://community.icann.org/x/RgI5Dg