NOTES | ICANN78 Council Meeting 199 1. Welcome and roll call Wiki: https://community.icann.org/pages/viewpage.action?pageId=228788172 Meeting is quorate Administrative matters 2. Relevant Correspondence (https://ccnso.icann.org/en/about/statements.htm) a. Information ICANN staff to Chair of the ccNSO on various review related initiatives (see agenda items 20, 21 a and 21 b) We have received various requests for comments. See the related items on the agenda. 3. Minutes & Action Items 1. Minutes Meeting 198: circulated to Council 17 October 2023 The minutes have been circulated on 17 October. We have received no comments 2. Action items 198-01: As a Decisional Participant, the ccNSO Council to determine if a Community Forum should be requested. (Completed, see agenda item 16) 198-02: Secretariat to inform various ICANN org departments, which may be involved in implementation of a ccNSO developed policy, of this guideline (ccNSO Policy Implementation Assistance Program (CCPA)) (Completed) 198-03: Secretariat to publish resolution 198-02 (informing various ICANN org departments on the ccNSO Policy Implementation Assistance Program) as soon as possible. (Completed) 198-04: Secretariat to publish the quarterly monitor Portfolio of Activities on the ccNSO website (completed) 198-05: Secretariat to seek final sign-off on SOI/COI to be implemented after ICANN78 (Completed see agenda item 17) 198-06: Chair of the ccNSO to circulate questions to the Board by 11 October (Completed) 198-07: Secretariat to produce doc for Council assignments at ICANN78 to provide update at the Council meeting (Completed) 198-08: Liaison to GAC to follow up regarding virtual joint meeting (Ongoing) 198-09: Further discuss how ccNSO can better interact with gTLD registries, during the “roles and responsibilities” talks (completed, see agenda item 19) Alejandra: All actions are completed with exception of Action Item 198-08 is the only action time that is still open. This awaits further discussion between the GAC and the ccNSO teams. 4. Intermeeting Decisions (since meeting 197, July 2023) a. Decision to provide comment on second version Terms of Reference Holistic Review b. Appointment of Fikriye Gelgüç (.tr) & Burak Eren (.tr) as members of DASC. Alejandra: note that the drafters of the first comments will be asked to prep a comment over the next two weeks to meet the deadline. 5. Intermeeting decisions Triage Committee No additional decisions. Quarterly monitor has been published at: https://ccnso.icann.org/sites/default/files/field-attached/ccnso-icann-activ... Updates 6. Update IDN ccPDP4 (written update) 7. Update ECA & CSC (written update - see also item 16 re ECA) 8. Update WGs (written updates or taken from the meeting) 1. IGLC 2. GRC 3. SOPC 4. OISC (no meetings pending Review, see item 10) 5. TLD-OPS 6. DASC 7. Technical WG 8. MPC 9. UAC [Universal Acceptance Committee] 10. IRP Panel selection 11. CCG WS 2 Implementation 12. Prioritization Framework group 9. Update liaisons (written updates) 1. Update ALAC Liaison 2. Update GNSO Liaison 3. Update UASG Liaison 10. Update OISC Review Nick: meeting on Sunday. The committee was created just before covid-times. Mandate: outreach. Bad luck, in terms of timing. the momentum of the committee did not get going. Did not meet since 18 months. We start lots of initiatives, if they fall short of the objectives, we should stop them. 2 alternative recommendations: work of activity and the ToR were reviewed. important and valuable parts of overall mission of the ccNSO. Either continue or re-constitute. We will bring the recommendations forward in due process. a lot of work of the ccNSO already involves capacity building and outreach. Overlap with the work of other committees. e.g. IGLC, DASC. Crowded space for outreach? Review Team to keep in mind. Pablo: thanks for the work done. opportunity to re-focus the objectives of the committee. Alejandra: looking forward regarding review results. timeline? Nick: need to check. latest, we expect our conclusion in start calendar year 2024 11. Update ccNSO Website redesign Stephen: next meeting soon Alejandra: up to us now to keep things moving forward. 12. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat Alejandra: * There was an SO/AC Chairs Roundtable, where Tripti, Sally and all the chairs shared our priorities for this meeting. * Laura Margolis has been appointed as ALAC liaison to the ccNSO. Jordan: appointed to the MAG, multistakeholder Advisory Group to IGF on behalf of Technical Community. Pablo: Next ICANN meeting is in Puerto Rico. We expect you there Administrative Matters & Decisions 13. Approval ccNSO membership IDN TLD ".ישראל" (xn--4dbrk0ce, .Israel in Hebrew) as member of the ccNSO. Move? Chris Second? Stephen question re resolution? None Astain or object? None Resolution approved. 14. Appointments to WG and Committees For decision a. Appointment Chair and Vice-Chair Universal Acceptance Committee, at nomination of the UAC: Abdalmonem Galila, chair and Regina Fuchsova, vice-chair b. Appointment Busayo Balogun (.ng) member of DASC c. Appointment of members IGLC: Javier Rua, Demi Getschko d. Appointment members SOPC: Olga Cavalli, Abdalmonem Galila, Eleanor Bradley Move? Nick Second? Ali Question regarding resolution? Chris: some have the ccTLD included in the resolution, some don’t. Please be consistent Javier: I am not associated directly with .pr and I am no longer a Councilor at the end of the AGM Pablo: Javier has the full support of the .pr registry to continue as a member of the IGLC Alejandra: yes, will add the ccTLDs in the final version Javier: abstain from decision Resolution is approved 15. Update Council Election and Board Nomination Process. For information · Update Board Nomination process · Update Council Election 16. Alert Approval Action Decision - Changes to IFR related Bylaws Articles 18 & 19 are FundamentL Bylaw changes Alejandra: see Approval Community Forum later today. The ccNSO Council is expected to take a decision whether to support, object or abstain from the proposed Bylaw changes. Under the rules for a Fundamental Bylaw change, at least 3 Decisional Participants need to support the change, whilst only one may object to the change. 17. Progress Implementation SoI/CoI Kim: internal process completed. (inaudible) pending council approval. We developed scripting for WG/C chairs. Ready to go as of 1 November For discussion and Decision, if needed (effective after 7 days of publication of the resolutions) 18. Outcomes from ccNSO sessions at ICANN78 (next steps) a. Update ad-hoc Council group: ccTLD caretaker and other policy matters Next steps, taking into account the results from the workshop and IANA update session. Jordan: We had a closed council workshop on sunday. 3 elements: * consolidation policies * identifying gaps in current policies * how to address unidentified issues Confirmation small team (notes missing regarding potential new additions) b. Registrant Capacity building (if needed) Biyi: what is the ICANN registrant capacity team doing and how does it relate to ccTLDs? ccTLDs have their own policies, and how they relate to registrants is different. What part of what ICANN is doing needs to be adopted/adapted. Good conversation to have. good engagement during the session. Proposal to have those that contributed to the session continue the conversation and take it forward. Alejandra: anybody that thinks we should not continue with this work? none. ok c. Corporate Social Responsibility (if needed) Molehe: session held on 24 October. Sharing experiences across the regions. Good presentations. Notable moments by those ccTLDs presenting. We need to continue monitoring. the approach aligned with the work done by IGLC. Proposal is to add this as a standing item to agenda of ccnso at icann meetings, as a standing item in terms of engagement. Javier: Very good session. Presentation by .be regarding sustainability. Aligned with other conversations elsewhere in the community, even at ICANNorg level. New CEO goal (goal 8): ICANN’s view of its environmental impact. avangarde conversations in ccNSO on CSR. Alejandra: let’s see if the community wishes to continue to discuss. 19. Review & adoption ccNSO external and review of Council Roles & Responsibilities appointees a. ccNSO External Appointments for adoption Alejandra: As part of reviewing the roles and responsibilities of ccNSO appointees to other groups, and as part of the succession planning process agreed upon in Cancun, a small team of Councillors has reviewed the roles of the ccNSO appointees to external groups (as Liaison or otherwise). The Council has been regularly updated. The latest changes are adding the description to RZERC and RSS CWG. Goal is to approve the overview during the ICANN78 Council meeting. Move? notes missing Second? notes missing no questions Abstain or object? none Resolution adopted b. Review and update, if necessary, Council roles & responsibilities. Background - It was agreed during meeting 198 to further discuss the need for exchange of liaisons with the GNSO registry Stakeholder Group. Depending on the way Council intends to organise this (either as a role at the level of Council, or through non-Councillors) the role(s) will be listed in the overview of roles and responsibilities of Councillors or as an external appointment. In addition check whether the current roles and responsibilities of Councillors needs to be adjusted. Alejandra: * liaisons per topic? e.g. abuse * general liaison? we agreed during the workshop that this was a good idea. any volunteers? Chris: i started having a chat with the leadership. good to have a chat with their and our leadership teams to discuss how to do that Alejandra: ok 20. Requested input and guidance ccNSO on WS 2 Accountability recommendation 2.3 David: I have been working on the WS2 coordination group. Community-wide framework on raising certain issues. Good faith, related to board member removal. The group asked to raise this with our communities. We pushed this off to January or later this year. standardised framework to raise issues to the ECA Best way to address this: council looks at the questions. GRC to discuss. Alejandra: GRC to look into this. if you agree, i will inform ICANN org David: spoke with staff support. They understood we would not be responding immediately, but will take it up in due course. 21. Review and feed-back on ICANN proposal to retire recommendations from reviews and proposal to establish a cross community group. At the latest SO/AC chair roundtable, the chairs of the SOs/ACs were requested to provide feedback from their respective communities on a proposed procedure to retire Board adopted recommendations from Reviews, which after certain passing of time have not been implemented. The second proposal is the creation of CCG to develop a continuous improvement framework as suggested by ATRT3. Alejandra: concern that this forum is being used to gather input from the community. it complicated the process. a. ICANN proposal to retire review recommendations b. ICANN proposal to establish a cross community group continuous improvement Sean: Open Space Technology as a good methodology. Maybe even PDPs would benefit from an open space session at the beginning. Irina: the proposals require detailed investigation. proposal “a” looks reasonable. proposal “b”: i do not agree with all 4 tasks mentioned. Alejandra: David, what is your view? Seen your experience in CCWG? David: this group is the first cross-community coordination group. it has been deliberate, and somewhat slow. Good, but also thanks to excellent staff support. there are various interests represented by all SO/ACs. takes time. Reasonable approach. but our challenge these days is prioritisation. Move? Tatiana Second? Jenifer Abstain: Sean (as it is a GRC matter) resolution adopted. 22. RSS GWG | Request for comments for “Governance Principles for the Root Server System” The ccNSO appointed members of the Root Server System Working Group (Luis Diego Espinoza and Peter Koch) have requested feedback and guidance of Council which they could relate to the Working group on the Governance Principles for the Root Server System” Peter: I am one of the 2 appointees to the RSS WG. Group to design the future structure of the RSS. Group came up with principles. Those are the guard rails for the working group in future. RSS WG seeks input from the respective SO/ACs. Luis to add additional comments in writing, if he wishes to do so. This is an informal consultation. Not a public comment. I seek Councils’ guidance on how to move forward. Happy to also set up a follow-up meeting, potentially with community members my recommendation would be to go ahead. However, it is important to review the proposals before you decide Jiankang: this is very important work. suggests for the appointees to have a bi-monthly report about the activities to council and/or community. Peter: request for more regular updates. the meetings are open to all. interim documents are accessible. understanding that an update is different from that. long debates and discussions which resulted in the principles. preference to first think about the principles before we move to further updates Chris: deadline for comments? Peter: not a formal consultation. need to check the deadline. Alejandra: any concerns? anything that requires closer attention? Peter: this is about accountability and future decision-making. no specific concerns regarding any one of those principles Irina: question to Peter. important work to progress further. how about presenting it to the overal ccTLD community? does it make sense in the future? Peter: good question. RSS GWG will engage in future too. progress is slow. avoid having a session every time will cause the process to move very slow. We need to sync timings for such sessions. but we need your feedback sooner. Alejandra: request to Peter and Luis to confirm deadline for feedback. 23. ICANN Leadership Program (LP) 2024 The ccNSO Council is requested and has the opportunity to nominate two candidates for ICANN’s leadership program. The program will be held on 29 February – 1 March 2024 in San Juan, Puerto Rico, just before the ICANN79 Public Meeting. The deadline for nomination is Wednesday, 15 November 2023. To date the ccNSO Council selected two persons (in general one Councillor and one non-councillor who serves in a leadership position with a working group or committee Biyi: selection of 1 councillor and 1 member in leadership position makes a difference. Community facilitators. bringing perspective of the ccTLDs. we should continue that way. Alejandra: deadline is 15 November. biyi, jordan and Alejandra to come up with a proposal, which will be presented to full council. ensures we meet the deadline Stephen: Board Action mentioned in Public Form. we need to keep an eye out for this 24. AOB 25. Thank You’s & Welcome 26. Next Council Meetings a. Meeting 200, 16 November – 12:00 UTC b. Meeting 201, 21 December – 21:00 UTC 27. Adjourn Joke Braeken joke.braeken@icann.org<mailto:joke.braeken@icann.org> ICANN78: Links to bookmark now ccNSO Schedule https://community.icann.org/x/doDxDg ccNSO Session Highlights https://community.icann.org/x/K4LxDg