NOTES | ccNSO Council Meeting 180 | 24 February 2022, 21.00 UTC 1. Welcome and roll call Documents for today’s call: https://community.icann.org/display/ccNSOCWS/24+February+2022+-+21%3A00+UTC We are quorate AOB? none 2. Relevant Correspondence (https://ccnso.icann.org/en/about/statements.htm) 3. Minutes & Action Items a. Minutes Meeting 179: circulated and published: 18 February 2022 circulated and adopted b. Action items and To-do’s, if any (To be included) 4. Intermeeting Decisions (since meeting 179, January 2022) · Appointment David McAuley WS 2 Coordination Group · Appointment members IGLC & MPC Item 5-9 Updates and Q&A 5. Update ECA, CSC, and CSC Effectiveness Review(written updates) questions or comments? None 6. Update WGs taken (written updates) a. IGLC b. SOPC a. GRC b. OISC c. TLD-OPS d. Technical WG e. MPC f. Triage Committee charter updates: topic on agenda later today questions or comments? None 7. Updates ccPDPs (written updates) a. Update ccPDP3- Retirement b. Update ccPDP3 - Review Mechanism c. Update IDN ccPDP4 Alejandra: ccPDP3 and ccPDP4 will give an update at joint meeting between ccNSO and GAC Stephen: * Retirement, is now in the board’s hands. Board formed an ad hoc group. no timeline yet. * Regarding RM: section 8 iana function contract - mediation. binding/non-binding. Continued discussion post ICANN73. 8. Update liaisons (written updates) a. Update ALAC Liaison b. Update GNSO Liaison questions or comments? None 9. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat * Joint Strategic trend exercise Council and SOPC * Roundtable SO/AC Chairs (hybrid meetings and ad hoc group on prioritization) Alejandra: Roundtable. prioritisation framework. ICANN org intends to launch a call for volunteers. Council closely worked with SOPC on this. ICANN planning expects 5 sessions starting early March. The related slide deck was shared with you in the background material for this meeting The SOPC has been involved in developing the Framework. As part of their interaction the suggestion was that: 1. an updated version of the original framework would be included in the FY 23 planning documents as background material: It was not 2. During the SOPC meeting with ICANN planning in January the suggestion was made that further developments would be done post ICANN73 Last week I reached out to the SOPC leadership but they do not see an exclusive role for themselves. So I have 4 questions: 1. Any thoughts from your end on this ICANN request? 2. Should we remind ICANN of the original schedule? 3. Should we participate? Jordan: yes, we should participate. I am not volunteering. preferably someone from SOPC. Chris: reason for not participating? Alejandra: indeed good to participate. but the plan as announced previously was not followed. We knew this was going to happen, but we did not expect it right now. Stephen: yes, keep an eye on this red-green marks? no red marks. Council agrees to participate. 4. Who should participate: a Councillor or member of SOPC? If so we have been asked to nominate a person by the end of February Nick: SOPC Chair Chris: or ask SOPC Jordan: Given SOPC is our interface with ICANN planning it is the natural group Bart: The chair was approached but he did not see an immediate role for the SOPC Chris: asking SOPC to find a volunteer as the best way forward. Alejandra: The deadline is now. timeframe is very short (this week?) Bart: chair SOPC was approached and he was not immediately enthusiastic. did not see a role for SOPC in pilot phase. few councillors are also on the SOPC. 1 person, designated by SO/AC, and an alternate. time commitment: every week in March there will be a 60 to 90 min session, and some prep work. Chris: Try to fill the role ourselves? in the next 24 hours? i will be over-committed if i volunteer. But this is very important to the community work leading forward. Alejandra: they expect 5 sessions, starting in March. Bart: see background material. testing the framework for a limited set of work items. please review the material again. if there is a self-nomination for a volunteer by tomorrow, end of day, we meet the deadline. that allows all to check whether it is feasible to do so. Chris: i will volunteer, unless others step forward? Alejandra: Irina as alternate. thanks both for volunteering in short notice. Alejandra: at the Roundtable, there was also discussion on possibility to travel to ICANN74. do you think travel to ICANN74 is possible, and if so, under what circumstances? Tatiana: i will be there Alejandra: I do not see restrictions from my country regarding vaccinations or visas, yet. willing to go. many respond willingness to go in chat. but elements out of our control. potentially meeting for SO/AC chairs in LA at the end of April. Third topic: trends exercise between Council and SOPC. Any comments? Alejandra: good exercise. discussion on current trends and feedback to icann org. good interaction. Item 10 - 18 for discussion or decision during the meeting 10. Adoption temporary Chair and Vice-Chair election procedure guideline does not foresee arrangement if meeting virtually. ad hoc procedure from last year proposed to be used again. Before starting that procedure, Council is asked to adopt it today. Main milestones are: Chair selection: START of Nomination on Monday, 28 February 2022 at 00:01 UTC END: Friday, 4 March 2022 at 23:59 UTC. Acceptance of nominations 7 March Vice-chairs: same dates On 8 March the secretariat will provide the list of candidates. Depending on the number of candidates there will be either a call for selection and formal appointment during the Council call on 10 March OR if there 2 or more candidates for one position there will be an email vote starting on 9 March until 10 March and formal selection during the Council meeting Pablo: move Chris: second Questions/comments? None All in favour 11. Launch Roles and Responsibilities discussion For discussion at prep council meeting ICANN73, as well as during ICANN73 Council meeting. Various roles: chair and vice chairs. But also: Triage, OISC, liaison for GNSO, PDP oversight commitee, etc. Full list will be circulated. We will share a google doc. You can sign up either tomorrow or monday. If there are questions, we will address them during the next Council prep meeting. please keep an eye out. You will have the possibility to volunteer for a role Bart: https://ccnso.icann.org/sites/default/files/field-attached/roles-responsibil... | Overview Roles 2021-2022 Relevant ccNSO Guidline: https://ccnso.icann.org/sites/default/files/field-attached/roles-responsibil... 12. ccNSO & Universal Acceptance deferred from previous meeting. is an important topic. UASG requested the ccNSO Council to appoint a liaison UA experience from Irina, Ai-Chin, Jiankang? Irina: many resources needed from registry. there are 61 IDN ccTLDs. India runs 22 of them. So roughly 30-40 IDN ccTLD managers. they are directly impacted and interested in this effort. Is that enough for the whole ccNSO to be involved? UA in a broader sense: common issue for all ccTLDs. frontend and backend should support and accept IDN email addresses. long-term. limited group of ccTLD managers, and they are already involved. They probably need more support. UASG is looking for a contact person from ccNSO, to better communicate. Alejandra: agrees. current ASCII ccTLDs also manage IDNs. broader Ai-Chin: UA should be initiated by the local community. cccTKD manager has arole. active promoting role to team up with registrars, email service providers. ccnso can do 2 things: * promotion role. focus on sharing info, experience, knowledge and best practice * create a UA readiness index, to allow ccTLDs to measure their stage. Perhaps not for all ccTLDs, but a UA readiness index could be an idea Alejandra: we could do something similar as what we did for DNS Abuse. Started at ICANN72, to explore the role of the ccNSO. good idea? Ai-Chin: we can try. Irina: we can do 2 things. approach those ccTLD managers, or ask via the list. preliminary survey Alejandra: not just IDN ccTLD managers Jiankang: agrees with all what has been said. 2 actions for the ccNSO, since IDN is a hot topic for the ccNSO. in future, more IDN ccTLDs. UA is important. ai-chin shared some suggestions. very good idea. liaison. perhaps a person with UASG. if they have something to coordinate, we can help. Alejandra: thank you. should we aim to appoint a liaison now? or not? Ali: local languages in Africa. French and English are not the biggest languages. capacity building and user sensibilisation needed. Alejandra: call for volunteers? seek a liaison? wait? Ai-Chin: we can appoint later. does not matter if the liaison is a councillor or not. Needs to better coordinate with UASG. and good connection with ccNSO, in time. Alejandra: let’s launch a call for volunteers ok? no red marks We also need to inform the ccPDP4 WG about this. 13. Change the Rules of the ccNSO: Council acceptance and next steps a. Council acceptance of proposed Rules Any questions on the changes? Or the process to date? See letter by Sean Copeland and David McAuley Alejandra: one of the final steps of an extensive process. one of the topics we knew had to deal with. We took our time. and now reached a milestone. We showed we can tackle complex topics. Also an achievement in times when we do not meet in person. Great accomplishment. Move? Pablo Second? Irina Comments or questions? None b. Next Steps Under assumption the Council will support the updated Internal Rules, the following decisions are required: · Approval of timeline for members vote · Appointment of the voting process manager. approve (a) , object (o), abstain (no) AF region: Ali: a, Biyi: /, Souleymane: a AP region: Ai-Chin: a, Jiankang: a, Jordan: a EU region: Chris: a, Irina: a, Nick: a NA region: Pablo: a, Sean: /, Stephen: / NomCom: Javier: a, Marie-Noémi: a, Tatiana: a LAC region: Demi: a, Jenifer: a and Alejandra: a Bart: stephen and Sean are on the call. might have audio issues. Perhaps they wish to approve by green/red tick? Alejandra asks them again? no response. comes back later to this Irina: how many in favours to make it happen? Alejandra: majority. in new rules we ask for at least 14 councillors. Sean sent his apology, had to attend in a call. Nick: stephen is travelling, timezone challenges Alejandra: we accepted the new proposed rules. Now members need to adopt them too. Email vote, called by Council, Chair or members themselves. Proposal that Council does so. See timeline in background material. Appoint Joke as Voting Process Manager. Questions/comments? none Move? Irina Second: Javier Comments/questions? none All in favour Alejandra: are Sean/Stephen back? no 14. Review of WG Charters and Terms Of Reference a. Adoption Updated charter Guideline Review Committee Move: Jordan Second: Nick Comments or questions? none All in favour b. Introduction Terms of Reference Triage committee email vote to adopt by Thursday 3 March noon UTC. Jordan: better represent the planning and prioritisation of the committee. online decision, after this meeting, to adopt the proposed ToR Alejandra: questions/comments? please use mailing list. online decision next week c. Progress review of other Charters TLD-OPS: no need for review Tech WG: is working on draft IGLC: also online decisions MPC: after ICANN73 other groups will reply hopefully soon. 15. ccNSO and DNS Abuse: what should the ccNSO do? Next steps. see roadmap in your background docs. Based on discussions at ICANN72. proposed ToR for DASC. Nick: leading suggestion is that there ought to be a dedicated committee by ccNSO working on this. largely because show-casing ccNSO’sinterest. best practice sharing forum. not policy formation. demostrating that all SO?ACs, incl ccNSO are involved. Show-case best practices by ccTLDs. Ad hoc group drafted the proposed roadmap. there will be opportunities to provide community feedback. approach where there ar eno surprises. See what we did so far, and how we used the input, and converted it into a proposal. main elements: * Enhanced information and best practice sharing, to benefit ccTLDs * Showcase ccTLD efforts and reinforce the message about the nature of ccTLDs and the role of the ccNSO * Explore DNS Abuse related metrics and other potential elements of the ccNSO & DNS Abuse ecosystem and related approaches. Not part of TLD-OPS. but they use a mailing list, and the ad hoc discussed that model. rapid response mailing list. is that useful when it comes to DNS Abuse? Nick is not in favour. to be determined by the new committee. Ask if there are any comments, any concerns? Any feedback can be also shared in the mailing list. If not, the proposed Terms will be presented to the community and if they agree, on the march council agenda for adoption. FYI, this topic is part of the agenda of the meeting with the GAC, along with updates of ccPDPs. 16. ICANN73 Meetings a. ccNSO Council i.Prep meeting: Roles and responsibilities Councillors ii.Council meeting: Chair and Vice-Chair elections, Conclude Roles and Responsibilities, Adopt Roadmap ccNSO & DNS Abuse, adopt terms of Reference iii.Nomcom: 5 min at the start of the council meeting (anouncement search for new leaders) b. Bilateral meetings .No joint ccNSO – GNSO meeting i.ccNSO - GAC joint meeting (Tuesday 8 March 2022, Block 1) 1. PDP updates (ccPDP RM and IDN ccPDP) 2. DNS Abuse ii.Q&A session with ccNSO related Board members. Alejandra will circulate icann board questions with council mailing list. Irina to moderate from ccNSO side c. ccTLD relevant sessions i.ccNSO webinar for newcomers: 23 February 2022 (13:30 UTC) ii.ccTLD news sessions 1. ccTLD News #1 - ICANN73 ccTLD News | Wed, 2 March 2022 (13 UTC) topics: Meet the members 2. ccTLD News #2 – Thu, 3 March 2022 (09:00 UTC). Topic: Capacity building efforts by ccTLDs iii. Tech Day – Monday 7 March 2022 iv.ccNSO Members meetings 1. Governance session: 2. ccNSO & DNS Abuse Session v.Plenary & other cross-community session(s) 1. Plenary session 1: Evolving the DNS Abuse Conversation: Maliciously Registered versus Compromised Domains 2. Plenary session 2: Moving Forward with the Global Public Interest Framework 3. ICANN org: Overview legislative initiatives with potential impact on DNS 17. Next Council Meetings · Meeting 181, March 10 | 14:30 UTC – ICANN73 , includes tentatively decision on ccNSO & DNS Abuse Roadmap, Chair and Vice-Chair election and assigning roles and responsibilities to Councillors · Meeting 182, April 21 – 12:00 UTC · Meeting 183, May 19 – 18:00 UTC · Meeting 184, June 13-16 – ICANN74 TBD · Meeting 185 July 21 – 12:00 UTC · Meeting 186, August 18 – 21:00 UTC · Meeting 187, September 17-22 – ICANN75 TBD · Meeting 188, October 20 – 12:00 UTC · Meeting 189, November 17 - 18:00 UTC · Meeting 190, December 15 – 12:00 UTC 18. AOB 19. Closure Council Workshop: What does Important mean for ccTLDs ? Start time: 22.15 UTC All interested are invited to join the workshop. Alejandra gives floor to Jordan. talking about a strategy document. we need to have a clear view of what the high-level strategy is, to enable triage committee to do its work. 3 pillars. mapping closely to purpose. foundations to what we do. is not a detailed strategy. not controversial either. this is about being clear what our direction is. does it help us to achieve what we want? address a few questions, and do a stress-test. first cut. not the final chance to discuss this. quick impressions. 3 breakout rooms, plus 1 room for observers. 3 questions. 1. Are the areas identified the most important ones, over a 3-year period? 2. Is any area missing that has to be included - and if yes, then which existing area in the draft is least important? 3. Any other feedback? 4. How would you rate the work required on any of these topics for the ccNSO/ccTLD community? (of strategic importance, less important, not relevant, detrimental) a. DNS Abuse b. Universal Acceptance c. RDS-WHOIS review 1 reporter per room. all captured in jamboard. further discussion later. this is the first step. Timing: 20 min in breakout room. 4 min report back time. no time for plenary discussion today. Reporting back Nick (main room) * Q1. reference to whether this is beneficial for end-users of the ccTLD? (ALAC - end users). none of the goals promote the experience for the end user * Q2. we spent most time on the box in the middle. Are all 3 goals equally important? middle one is the main priority, against which objectives should be set. is policy creation that important? the few policies we create are important, but policy creation in general? * Q3. DNS Abuse example: policy creation is not important here * Q4. 100% agreed those were correct. especially against the middle goal. Jordan * Q1: yes. right areas * Q2. missing? third of the goals was discussed. there might be issues where there is no ccTLD interest, but still important to work on, to uphold the system. * Q3. word “modern” in second foundation. collaborative could be better * Q4. this framework of goals would allow that. DNS Abuse fits in 2nd goal. UA fits in 3rd. we did not prioritise them. * discussion on overal purpose of the ccNSO still fine? still ok. no need to reasses. Marie-Noemi * goals capture the strategic direction. yes * missing? change of formation is maybe not enough. is capacity building covered and where? relations with Regional Organisations and others such as ISOC could be covered to * Q3. dialogue between members, is that captured? it is important. innovation for new topics? should it be included? * Q4. (notes missing) Irina: * Q1. yes, these are most important areas. aligned with previous discussions * Q2. ccNSO voice is not heard loud enough. we need to promote the work by the ccNSO more. depends on context. * Q3. clear and concise one-pager. allows us to stay on track * Q4. DNS Abuse considered to be important, not sure about UA. Jordan: this was helpful. we are broadly right, improvements to be made. This can feed into work plan. Thank you all. Joke Braeken joke.braeken@icann.org