NOTES | ccNSO Council Meeting 182 | 21 April 2022, 12 UTC 1. Welcome and roll call Welcome by Chair Alejandra. Invites all to switch on camera, and to add label “Council” in zoom names Wiki: https://community.icann.org/display/ccNSOCWS/21+April+2022+-+12%3A00+UTC Meeting is quorate 2. Relevant Correspondence (https://ccnso.icann.org/en/about/statements.htm) We received a letter from Theresea Swinehart. See agenda item 12. 3. Minutes & Action Items a. Minutes Meeting 181: published (transcript of the meeting) b. Action items and To-do’s, if any All action items completed. 4. Intermeeting Decisions (since meeting 181, March 2022) · Adoption clarification impartiality statement · Adoption amendment Terms of Reference Triage committee · Adoption Terms of Reference DNS Abuse Standing Committee and launch call volunteers · Appointment Qing Cai (.cn) as ccNSO liaison to the Universal Acceptance Steering Group (UASG) · Appointment Peter Koch to the Root Server System Governance Working Group (GWG) · Launch call volunteers ccNSO appointee to 2023 NomCom Item 5-9 Written Updates Go to: https://community.icann.org/x/4QciCw 5. Update ECA, CSC, CSC RT (written updates) Circulated on council mailing list prior to today’s meeting 6. Update WGs taken (written updates) a. IGLC b. SOPC a. GRC b. OISC: no meeting since ICANN 73 c. TLD-OPS d. Technical WG e. MPC: item 18 agenda f. Triage Committee (item 15 agenda) Stephen: Tech WG charter change addition of 2 Vice Chairs with staggering terms. Will be finalised at ICANN74 7. Updates ccPDPs (written updates) a. Update ccPDP3 - Review Mechanism b. Update ccPDP4 – (de)Selection IDN ccTLD strings Stephen: sub-group for binding mechanism met and will present its results next week. Response from ICANN legal was received. Policy update at ICANN74 8. Update liaisons (written updates) a. Update ALAC Liaison b. Update GNSO Liaison none 9. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat 2 updates: (details below) * Roundtable SO/AC Chairs (hybrid meetings) * Ad Hoc group on prioritization Alejandra chairs topic for discussion next week in LA at the SO/AC roundtable Discuss topics Roundtable: * 5 year strategic plan, where are we? * Prioritization & FY24 Planning * Update on Prioritization Pilot & next steps * Collective Role of SOAC Chairs in Community Prioritization * Tour de Table: Top SOAC Priorities for 2022 & going into FY23 * Next steps organizational reviews * Improving Process for Board Consideration of Advice from ICANN’s ACs * Update & Next steps: implementation work on enhancing the effectiveness of ICANN’s Multi-Stakeholder Model * Renewing & Maintaining Community Interest in Policy Participation * Ensuring Continued Informed Participation * Reducing the Learning Curve for Newcomers * ICANN74: What to expect and Planning Ahead for Future Meetings * ICANN’s waiver for participation Chris provides update on Ad Hoc group on prioritization review spreadsheet of board approved recommendations Next group will need to prioritize them urgent and important, urgent and not important, important and not urgent, etc. ICANN staff added their own suggestion of prioritization. This group just needs to go through the process. budgets to be looked at once the prioritisation has been done. Hard to keep people on track. The fact that individuals do not like the recommendation is not relevant: they are all approved by the Board. Irina is Chris his alternate. She participated together with Chris in listening mode. Irina: just 3 to 5 meetings scheduled to do this job. That is challenging. There are 45 recommendations. would prefer to give more time for discussions to the group. it is a pilot, lessons learned. Alejandra: so more time needed? Irina: yes, my opinion. but i stand corrected if needed Chris: there is enough time, as long as we are disciplined. Alejandra: ok, will let you know if there are updates from the Roundtable next week Nick: meetings going forward. any updates on Den Haag? Will it feel like an old meeting? many people plan to attend. What to expect? Alejandra: no registration numbers shared yet. Info on health and safety protocols. RoundTable will be a trail next week. daily tests, temperature, masks, social distancing … max capacity of people allowed in a room. will check next week if there are numbers Nick: if 3000 people attend in person, how is 2 meter distance possible? How are temperatures taken? large ques? Alejandra: will see how the roundtable go next week. Chris: main room. no head table. all using their computers. overflow rooms in the centre. distancing. goals is to hold each session, and no-one is disadvantaged by not being in the room. all communication via computers. no plenary sessions. this is a policy forum. many people will choose to join meetings from their hotels, where there are no mask requirements, and people can gather. Item 10 - 18 for discussion or decision during the meeting 10. Adoption Roles and Responsibilities Councillors we have a separate doc for appointments to external WGs. See https://docs.google.com/spreadsheets/d/1dQfe1zCp0LdFFkwb6cZ1W-aXrR3Z_B92/edi... question regarding resolution? None green ticks by Councillors Against? None This resolution has been approved. 11. Appointment ccNSO representative on NomCom 2022 Council thanks Juhani Juselius (.fi) for his service on the NomCom. Juhani is term-limited. The ccNSO Secretariat shared a call for volunteers on the ccNSO members mailing list. https://ccnso.icann.org/en/announcements/announcement-29mar22-en.htm The call for volunteers closed 13 April 2022, 23:59 UTC. The ccNSO Secretariat then launched the Council selection process. As requested by NomCom support staff, the ccNSO should appoint one (1) representative. At closure of the application window, 4 candidates stepped forward for the role After receipt of the applications, the application material documents (if submitted by the candidates) were transmitted to the ccNSO Councillors, except for Chris Disspain, who was a candidate himself. The remaining Councillors selected and listed the candidates in order of preference and mailed them to the ccNSO Secretariat before the deadline on 20 April 2022 (23:59 UTC). Announcement call for volunteers: https://ccnso.icann.org/en/announcements/announcement-29mar22-en.htm Further details on the selection procedure by the ccNSO Councillors can be found here: https://ccnso.icann.org/sites/default/files/field-attached/guidelines-ccnso-... No questions or comments Move? Demi Second? Stephen Chris Disspain was the candidate with most supportive votes. resolution to appoint Chris Green ticks in the room, no red Against? None Abstain? Chris Disspain Congratulations to Chris. He says the NomCom is very important. Delighted to take up a position there. 12. Deferral ccNSO Organizational Review Theresa Swinehart, ICANN’s Senior Vice President, Global Domains & Strategy sent the ccNSO a letter asking for a deferral of the next, 3rd ccNSO Organizational Review, until such time as there is better understanding of the impact of the ATRT3 Recommendations on the next Organizational Review cycle, and taking into account the current community workload. The 3rd ccNSO organizational review is scheduled to start in November 2022. We are requested to provide our feed-back by tomorrow, 22 April 2022. Move? Stephen Second? Jenifer questions? none green ticks mean in favour no red crosses Resolution adopted. 13. Adoption Voting Report on Change of the Internal Rules of the ccNSO special thanks to the RO’s and all those that promoted the vote. The new internal rules have now been adopted Move? Demi Seconder? Sean questions regarding the resolution? none green ticks no red ticks Against? none Abstain? none Approved. Final step on this process. thanks to all involved 14. Impact upcoming change Article 10 and Annex B to include IDN ccTLDs in the ccNSO Bart: GRC had a discussion on the anticipated impact of the bylaws amendment. Bylaw change was published for public comment recently. all comments received are in favour. Major changes include: 1. change definition of who can be a member 2. the inclusion of the definition of what is a territory This was needed, to link decision-making by the member, to the territories. avoid issue against captcha. representative = primary contact. Introduction of the “Emissary”. a rep from a territory, who will vote on behalf of all members from a specific territory. specific decisions include Council elections, PDP vote, as foreseen in the bylaws. Change from 1 vote per ccTLD manager, to 1 vote per territory. But it may also have an impact regarding the voluntary arrangement for the board nomination. final role is with the council, however the members nominate and select the candidate for a board seat. Question for the future: who should have the final vote? should it be the emissary? or a representative? open question, but as a result the guideline may need to change as a results. council election guideline just follows the bylaws. Also, are changes needed to the “members veto vote” in the new internal rules? members vote on a council decision: per ccTLD manager, or per Territory? there needs to be discussion/clarification on what the community may want. How will quorum be counted? 33 % of the members? or 33% of the territories? extreme case: if NIXI would become member for .in and all IDN ccTLDs, it would be 22 members for 1 territory (India). impact on quorum and voting mechanism also change in the application form for ccNSO membership. Still geared to current definitions. Sean: Chair of the GRC. “ I’m asked to comment on the impact of upcoming changes to Article 10 and Annex B. I have brought this subject up lightly in the sub-group on COI, and it’s from that where I will express my view. I am speaking to you here, though, as a councilperson and not as chair of GRC. Under Alejandra’s pen, we sent a communication to ICANN on September 9th of last year, a follow-up to a letter from the previous council on February 7th of 2020. Subsequently, a board resolution 2021.10.28.06-10 came about regarding the feasibility assessment as a result of the work by Merdian. In reviewing the documentation on bringing IDNs into the fold, this has been a long process. I want to note the completeness of a document produced by Bart in 2013. We are approaching a decade. If there is earlier material concerning IDNs, I apologize. Why do I want to look at the IDNs at this moment in terms of Conflict of Interest? We each, as councillors, once the bylaws are in place and IDNs are at the table, have two stakeholder groups, the existing members of the ccNSO and new IDN members. We do have to acknowledge our fiduciary responsibility to our current members. This means that any changes now or in the future may appear unbalanced to those in the IDN community. At the same time, we’re charged with ensuring balance for the existing membership. This is why I brought up Bart’s document from 2013. In particular, I want to draw your attention to Bart’s ambassador idea. The ambassadorship idea has, I feel, correctly carried forward to the changes to be implemented, as it must be to ensure the core definition of the ccNSO remains the 3166 ISO table. I believe it is in our best interest to produce a written statement from the council acknowledging we are aware of such a potential for perceived conflict in a conciliatory message and move on. Moving on, we should. With the successful passing of the new rules - again, thank you to the subgroup, David and our staff - voting procedures and guidelines will need to be updated. This can be referred back to the GRC, and if so, this will move to the top of the main GRC group task list. Ideally, and perhaps aggressively, it would be nice to have this item back to the council before or during ICANN 74. With all respect to former and current board members, I would hope whatever adjustments are required are seen as administrative in nature and happen in a timely fashion. The impact of IDN’s will require this council to engage in recommendations from the Feasibility Assessment actively. In particular, items 7,8,10 and last but assuredly not least, item 11, the website. The ccNSO website needs to be up to date before or as IDNs are officially joining this community. There are more than enough resources available to ICANN for this to happen forthwith. Given that this Service Organization gives ICANN its international legitimacy, in this councillor’s opinion, let us encourage ICANN to help us welcome IDNs into our community with a modern website.” Irina: followed the process for a long time. aware of the concept of Emissary. but understood an organisation cannot be a member x number of times. good to have a list of territories for which this is applicable? Which Territory has also IDN ccTLDs? Bart: see https://www.icann.org/resources/pages/fast-track-2012-02-25-en Emissary. if it is one and the same organisation that runs the ASCII and IDN ccTLD, the emissary will be the representative of that organisation. if there are 2 distinct organisations, both can become member. issue: who will vote on behalf of the territory. hence emissary Bart: In response to Irina's second question, please see: https://www.icann.org/resources/pages/string-evaluation-completion-2014-02-1... 15. Update Triage Committee a. Outcome Council workshop 24 February 2022 no major edits to the 1-pager circulated prior to the workshop. The Strategy on a page: https://docs.google.com/document/d/18kS42BvVyOhLnoVcMB0yKkCJ9dwpgcwvXIoiCiK1... Council Workshop: What does Important mean for ccTLDs? held on 24 February 2022 at 21.00 UTC Notes: https://docs.google.com/document/d/1VoQn48ziLTxHavvXBzM-Ya3ZDmhGCBf-/edit?us... b. Work Plan FY23-25 ready before ICANN74 Annual cadence of the process. Alejandra: looks forward to new tool Triage Committee is still working with staff to port the work plan into a new interactive tool, and will be spending time at two meetings early in May to assess all the work against the new Strategy, and then present the work plan back to Council for its adoption at the May call. Jordan: I also want us to write down the pattern for this plan approval process so that in future we know exactly when to expect it, and how to gather input to it. 16. Charter Updates See overview: https://docs.google.com/spreadsheets/d/1xLgzHqLJAQ3ZNX9IC_46hJu207fGX1ugZQJo... Irina: SOPC meets on April 28. they will start the discussion then. Main topic is the approach for future work by SOPC, including the review of ICANN’s operating plans and budget. Does not expect major changes to the charter, if any, minor adjustment. Another SOPC meeting in May. 17. Interpretation during ICANN Meetings Kim: org initiative. discussed by org to make public meetings more accessible. specific languages were not discussed. initial ccnso request for spanish, french, arabic. not available for ICANN74, hopefully for ICANN75. staff is working with org and council leadership. 18. ICANN74 Meetings Peculiarities of hybrid format: Registration to the event is mandatory (23 May - 8 Jun) Registration to sessions is mandatory (23 May - 8 Jun) - # of participants Publication of schedule 23 May a. ccNSO Council i.Prep meeting (week 6-10 June) ii.Informal Council meeting (Monday 13 June 2022) iii.Council meeting b. Bilateral meetings Note ALAC reached for a meeting without any suggested topics. Comments? Any topic you would like to discuss with ALAC? Chris: defer to ICANN75, and have a lighter agenda for ICANN74. others agree Lianna Galstyan is the new liaison from ALAC to ccNSO. She participates in the call today. Javier: Belated comment on ICANN75 ALAC/ccNSO bilateral: IDNs, string confusing similarity, and DNS abuse (that’s a single-ish joint topic). Lianna: @Javier, these topics are indeed in ALAC's agenda and we can plan a bilateral meeting for ICANN75, as you all agreed. i.Joint ccNSO – GNSO meeting Joint session: ccNSO-GNSO | 14 June 700-800 UTC (block 1) Proposed Topics: · What happens after PDP recommendations are accepted by either council? Both groups are finding that post-PDP timelines lack predictability, particularly when extending well beyond the time invested in the PDP itself. Both SOs will share their approaches to remedy the issue and find potential mutually applicable solutions. · DNS Abuse Updates from both groups on our activities on this topic and our interactions with the rest of the community. · EPDP Phase 2 SSAD and ODA The GNSO would like to update the ccNSO on the latest developments of the EPDP Phase 2 – SSAD since the publication of the ODA on 25 January 2022, as the suggested direction may come of interest to certain ccTLDs in the future. · IDN While the ccPDP4 is awaiting a response from the Board following the January 2022 submission of its report, one of the liaisons between it and the GNSO EPDP on IDNs may want to report on the latest developments of the later which may affect both groups [if any]. Chris: topics 1 and 2 others if time allows? c. ccTLD relevant sessions i.ccNSO webinar for newcomers ii. ccTLD news sessions 1. ccTLD News #1 – Thursday, 19 May 2022 (13:00-14:30 UTC) The impact of the pandemic on ccTLDs Call for presenters: https://ccnso.icann.org/en/announcements/announcement-05apr22-en.htm 2. ccTLD News #2 – Tuesday, 24 May 2022 (06:00-07:30 UTC) Cybersecurity: The link between ccTLDs and national Cyber Emergency Response Teams (CERT), from a regional perspective Joke provides some planning related updates All interested in presenting, or knowing about potentially interesting contributions, please contact the secretariat iii. Tech Day – Monday 13 June 2022 iv. ccNSO Members meetings 1. Policy update: ccPDP3 and ccPDP4 Nick: updates on progress to date, and consultation with community on proposed way forward. 2. Governance session: SOI & COI (Statement & Conflict of Interest 3. ccNSO & DNS Abuse Session: local DNS Abuse policies, role of ccTLDs 4. SOPC: what are core topics to focus on in ICANN’s planning Irina: 1 or 2 committee meetings. Discussion with all ccTLDs. 5 year plan and budget is a big doc. 300 pages. Hard to process, and to submit valuable comments. perhaps we should focus on those areas most important for ccTLDs. v. WG Meetings: 1. ccPDP3 Review Mechanism WG 2. ccPDP4 IDN WG meeting 3. TLD-Ops Steering Committee 4. Tech WG 5. SOPC vi. Plenary & other cross-community session(s) 1. Plenary session 1: (Tentatively) Who set ICANN’s priorities? Five years later (proposed by ccNSO, Jordan/Chris to take the lead) planning by Jordan and Chris Chris: heard that there will be no plenary Alejandra: no final yes/no. Bart: this planery was 5 years ago at the policy forum discussions in SO/AC planning committee. discussion on thematic approach. (1 session on SubPro) also 1 plenary, and a geopolitical forum. 2. Thematic session: Subpro (Monday 13 June 2022) 3. ICANN org: Geopolitical session (Thursday 16 June 2022) 18. Next Council Meetings · Meeting 183, 19 May – 18:00 UTC · Meeting 184, 16 June - ICANN74 TBD · Meeting 185, 21 July – 12:00 UTC · Meeting 186, 18 August – 21:00 UTC · Meeting 187, 17-22 September – ICANN75 TBD · Meeting 188, 20 October – 12:00 UTC · Meeting 189, 17 November - 18:00 UTC · Meeting 190, 15 December – 12:00 UTC 19. AOB none 20. Closure Thank you all Joke Braeken joke.braeken@icann.org