NOTES | ccNSO Council meeting #200 16 November 2023 (noon UTC)
1.
Welcome and roll call
welcome by Alejandra
https://community.icann.org/pages/viewpage.action?pageId=228788175
a.
Is the meeting quorate?
Yes
b.
Introducing Statement of Interest for Councillors
Guideline:
https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-21sep23-en.pdf
Form:
https://forms.gle/WQuz6S72tY5kuKvk6
Any updates we need to be aware of? None
Alejandra: SOI template available now. COI for Councillors. Invite to please complete the SOI form. council to set the example. SOI introduction: other ccNSO WG/C
were informed too.
ADMIN MATTERS
2.
Relevant Correspondence
(https://ccnso.icann.org/en/about/statements.htm)
a.
Transition ABR process in regular Budget process (see item 19)
b.
Invitation to meet with Ombudsman search Committee
(see item 20)
c.
Invite to appoint members Excellence Award Selection Panel
(see item 14 a)
3.
Minutes & Action Items
a.
Minutes Meeting 199:
Taken from transcript of the meeting.
transcript not yet available
b.
Action items
see list included in agenda. several completed, some ongoing.
See item 199,8: conversation with RySG on exchange of liaison. Have not met yet with RySG leadership. Perhaps we should invite people that are already active in
this area. e.g. Chris, Nick, David Mcauley
Alejandra asks for confirmation.
Green ticks in zoom
Also still ongoing: Reach out to GAC chair, to see who will be the one liaising with us regarding agenda setting. Pär Brumark is no longer vice chair. New leadership
team at GAC. update to the liaisons?
Letter sent to ECA. ccNSO as decisional participant
b.
Decision leadership program
2 individuals selected: see e-mail list. participation confirmed and prep is on the way.
5.
Intermeeting decisions Triage Committee
The Triage Committee considered requests for input (completed).
The Triage recommendation tracker on the ccNSO website will be updated within the next 24 hours. See
https://ccnso.icann.org/en/about/council/decisions/2023.htm
Quarterly monitor:
(updated version circulated to Council)
UPDATES
6.
Update IDN ccPDP4 (written update)
7.
Update ECA & CSC
(written update)
8.
Update WGs
(written updates or taken from the meeting)
a.
IGLC
b.
GRC
c.
SOPC
d.
OISC
(no meetings pending Review)
e.
TLD-OPS
f.
DASC
g.
Technical WG
h.
MPC
i.
UAC
j.
IRP Panel selection
k.
CCG WS 2 Implementation
l.
Prioritization Framework group
9.
Update liaisons (written updates)
a.
Update ALAC Liaison
b.
Update GNSO Liaison
c.
Update UASG Liaison
10.
Update OISC Review
Nick: meeting at ICANN78. 3 options:
Note: overlap with activities of other groups
Note: Volunteer capacity is limited
Pablo: thanks for an excellent meeting in Hamburg, and for listening with care to each of us. job well done
Nick: thank you, but not yet finished.
11.
Update ccNSO Website redesign
Stephen: ICANN78 came in between. No meeting took place there.
Developing personas. Look at what they are trying to find on the website. it proves to be interesting and useful. results look promising. Staff
has a good toolbox.
Next week Thanksgiving: only working on Monday-Tuesday.
Persona approach input?
Alejandra: good summary.
12.
Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat
a.
Invitation to meet with Ombudsman Search Committee (listening)
Alejandra: Committee from ICANN Board. Similar to CEO search
draft requirements Ombudsman shared. They seek from us a summary of what the community is looking for in this role. Any input? speak up now, or respond to the
email i will share afterwards. ccNSO Chair and Vice Chairs participate on behalf of the ccNSO
Nick: amazing this exists. empty office? useful? statistics?
Alejandra: know it is being used
Stephen: has been used. serves a useful purpose in the org for mediation. worthwhile effort.
Tatiana: yes, extensively used. Many issues that never go public. resolved via ombudsman. less going on in terms of offensive communication. this is a safe and
friendly environment. especially compared to other spaces. ombudsman is part of ICANN structure. necessary for accountability purposes.
Biyi: ombudsman deals with things before they blow up. helps to resolve a lot of issues. we used it once. Issue with someone from Nigeria and India, with public
statement that should not have been made.
Alejandra: was approached once by the Ombudsman regarding a potential issue
Jordan: The Office of the Ombudsman received 172 complaints from 1 July 2021 to 30 June 2022.
Bart: see annual report.
https://www.icann.org/resources/pages/reports-96-2012-02-25-en
Nick: useful background information. we should support the continuation. if it works well, no changes needed to ToR
b.
SO/AC Leadership Roundtable Washington DC
Workshop in January. 2,5 days in person for the Council leadership team.
Proposed Topics:
Additional topic: WSIS+20 coordination. Topic to be raised by us.
See also topic later on in the agenda. (item 19)
Alejandra suggests to deal with item 19 first.
ADMIN MATTERS & DECISIONS
13.
Update 360 Feedback Councillors
Alejandra: Last time we spoke about the frequency of the feedback sessions. Review the guidelines. Questions in the questionnaire? See new proposal displayed in
zoom.
Major changes:
Do you agree with the proposed changes? Comments welcome by the end of the week
14.
Appointments to WG and Committees
a.
Appointment panellist Excellence Award selection committee
Olga and Pablo reconfirmed. second term. thanks to both
green ticks
Abstain? Pablo and Olga
Object? None
b.
Appointment ccNSO NomCom appointed Councilor to Travel Funding Committee
Javier Rua his term on Council ended at ICANN78. Other NomCom councillor needed to replace him on travel fund committee
Biyi: i was going to nominate Wafa
Joke: short summary of what to do (timeline and evaluation of applications. decision on how to distribute slots)
Biyi: Travel fund committee as part of OISC
Wafa: I accept my nomination
Move? Tatiana
Second? Olga
Abstain? Wafa
Object? none
decision approved.
15.
Contacting members CCWG-AP recommendations and other issues pertaining to the Grants Program
See background. Exchange of letters between xavier Calvez and Sebastien Ducos. ccNSO was one of the chartering organisations, and adopted the CCWG AP final report.
ICANN org asked leadership team whether there were objections to ICANN contacting the former members regarding implementation. There was a recommendation from CCWG-AP (rec 7) that requires a fundamental bylaw amendment. ICANN thought that it was not needed
to go down this path: no bylaw change needed.
ICANN Board Chair sent an email to the former members of the CCWG-AP to inform them of the Board’s intention to direct ICANN org to change the
implementation path of the CCWG-AP’s Recommendation 7, which was focused on limiting the use of ICANN’s accountability mechanisms to challenge individual application decisions made by the independent assessment panel. the ICANN Board intends to now direct
ICANN org to achieve this recommendation through the applicant terms and conditions that grant applicants will agree to when submitting their grant application. The ICANN org team looks forward to providing further public updates on the progress of the ICANN
Grant Program across various communication avenues, including via former CCWG-AP members and SO/AC leaders. Recognizing that the former members of the CCWG-AP now act in their individual capacity, asks feedback whether SO/ACs are comfortable in having them
engage in this conversation or whether it should be held differently.
Irina: reasonable
Alejandra: resolution at ICANN78
Bart: board decision in Hamburg. They directed staff to follow the advice of staff to not go for a fundamental bylaws change. the Grant Program
will start at end of Q1 2024. fundamental bylaws change would take too long. Fundamental bylaws change raised some concerns. Hence the alternative approach. GNSO is concerned from diverting from the mechanism to implement the recommendation. contractual solution
to avoid applicants use the reconsideration or IRP. topic no longer “hot” topic.
Alejandra: board resolution. also bylaws change in parallel.
Bart: broader discussion as part of the resolution. to be included in the ccNSO icann bylaw repository. The intention to consult the community
on broader implications of fundamental bylaws changes is something to monitor. Especially in light of the conversation in hamburg on bylaws changes.
16.
Update Council Election and Board Nomination Process.
a.
Update Board Nomination process
b.
Update Council Election
17.
Confirm no role of the Council or ccNSO to discuss individual cases if invited to comment on specific ccTLD cases in press or otherwise
Alejandra: I was approached about .su
Others were approached regarding other TLDs, also topic during public forum at ICANN78
Council agreed not to discuss individual cases, nor as Council nor as a ccNSO Councillor in public. This is a reminder to all. we as Council will be discussing
gaps in the IANA policies the coming months internally and with IANA staff.
Pablo: discuss in appropriate spaces and with appropriate people. I support what you shared
Alejandra: commenting on a specific ccTLD situation is challenging. sovereignty for ccTLDs, and we may not be aware of all circumstances
Stephen: ICANN to reach out to us for our view on a topic?
Alejandra: ICANN might inform Council (leadership) what will happen, but does not consult. They are aware of Council’s role. e.g. recent .lb case
green ticks, no objections
18.
Portfolio of Activities monitor
(Triage Committee)
Jordan: we circulated the updated Activity Monitor. originally a quarterly update, but following ICANN78 a quicker updated was deemed valuable
Quarterly monitor:
Updated version circulated to Council, and will be online soon.
Questions? use mailing list
19.
Role , if any, of IGLC, ccNSO Council and / or ccNSO with respect to WSIS +20
Alejandra:
We want to avoid it to become as a fight between multistakeholderism versus multilateralism
ccNSO as voice of the ccTLDs
Should Council have a role? or shall we leave this to IGLC?
Jordan: we can encourage ccTLDs to talk about this topic with their governments. ministry of foreign affairs or economic affairs. Thus you will learn about what
your gvt thinks about the topic
Dedicated point of coordination / information would be good, regarding WSIS+20 and GDC. could perhaps be a dedicated meeting by IGLC. ccTLDs interested to be informed
and inform others. From the Hamburg meeting, it showed that it was obvious to those already involved. But for those not yet involved, it is very much an insider-topic. IGLC developed a Q&A before ICANN78. AUDA Comms department offered help to refine the message,
to share info in a clear and concise way.
Stephen: We need to start talking to our gvt. Could IGLC as a “clearing house”? repository of what ccTLDs are doing with their governments? have a global overview.
Jordan: let’s ask the IGLC Chair and Vice Chair
Tatiana: 100% a role for the ccNSO. might be a big role. if Annaliese and IGLC are willing and available. In the broader community there are growing concerns about
WSIS+20. clearinghouse sounds like a good idea. point of collecting ideas, setting the strategy. broader community conversation, and liaising with Veni Markovski and Elena Plexida. share info, be informed about potential strategies.
Annaliese: ccTLDs can indeed play a role in engaging with their governments. We did a mapping exercise in Hamburg. WSIS+20 was an issue across all of the regions.
We have not decided what to do regarding the mapping, in terms of prioritising. IGLC can indeed reflect on potential approaches. mapping. clearing house. people are keen to hear more about it. personally happy to have IGLC usefully contribute here
Nick: thanks to Annaliese and AUDA. important topic. meeting in London with the ICANN CEO to talk with our gvt and national stakeholders about WSIS. same path
to take. what do we advocate? continuation? continuation with adjustments? duplication of efforts with ROs, with efforts at national level. What is the objective of the community?
Anil: ccTLD to liaise with governments. IGLC to collaborate with a small team of the GAC. advise how to collect info, and advocate the ICANN stance to their governments.
Alejandra: good ideas. motivating ccTLDs to reach out to their GAC members and governments. but it is up to ccTLDs, we cannot force them
Jordan: countries have diverse and sometimes opposed views. regarding future IGF, regarding multistakeholderism versus multilateralism. We need to contain those
discussions in a dedicated space. institutional and national level might not support multistakeholderism. be conscious and respectful about those viewpoints in our work in that area.
CEO goal 6 is applicable from 1 July 2023 to July 2024. little time left, and potential CEO transition. we should expect to be hearing more from ICANN regarding
their WSIS messaging. If not clear by roundtable in January, we should ask.
Alejandra: i was approached. ccnso as key player. global reach, diversity. it is important to have voices heard from everyone. louder voices are anglo-saxon voices
currently.
Jiankang: ccNSO is family for all ccTLDs. relation with local government. All ccTLDs should play their role regarding WSIS. inclusiveness. Universal Acceptance
is also part of the WSIS meetings. role for Council to be an advocate of the multilingual internet.
Jordan: Some really strong points about how ICANN work and things like IDNs and UA can really help more people get access to the gains. Celebrating and emphasising
those successes can be a core thing we can do probably with broad consensus
Ai-Chin: What are our expectations for this issue, or what direction does ccNSO intend to take? This will allow us to offer concrete thoughts to our members
Alejandra:
Council agrees (green ticks).
Thanks to IGLC leadership team
20.
Transition ABR process in regular Budget process
Alejandra: The proposal is about the process, how to submit a Budget request. Currently there is a separate process, ICANN proposes for efficiency and transparency reasons to include
the ABR procedure in the Annual Budget process. Based on the online discussion, my suggestion is to inform ICANN we support the simplification, however with the caveat that ICANN provides a template like they do now to distinguish between Budget requests
and comments on the Budget/Operating Plan.
Green ticks
21.
AOB
Stephen: i requested an AOB, but will use mailing list instead in the interest of time
Alejandra: reminder about DASC mailing list launch. please spread the word with your ccTLD peers that deal with DNS Abuse
22.
Next Council Meetings
a.
Meeting 201, 21 December – 21:00 UTC
b.
Meeting 202, 18 January 2024 -12.00 UTC
c.
Meeting 203, 15 February 2024 - 18.00 UTC
d.
prep for ICANN79, 22 February 2024 - 18.00 UTC
23.
Adjourn
thank you all.
Joke Braeken