Hello everyone, Please find included below the high-level notes from today’s ccNSO council meeting. Best regards, Joke Braeken 1. Notes ccNSO Council Meeting | 22 August 2019 @12:00 UTC 1. Welcome and roll call Attendance will be taken according to who is in Zoom. Apologies received: Pablo Rodriguez, Philippe Fouquart, Maarten Simon. Calls are recorded and transcribed. Recordings and transcripts will be posted on the public wiki: https://community.icann.org/x/Lwn_BQ . Welcome by the chair. Congratulations to .pr on the 30th birthday. 2. Minutes & Action Items No comments received. Most action items completed, some are still ongoing. E.g. improvements suggested to Rejection Approval Process. Will be done first part of September. 3. Intermeeting decisions (since 18 April) * Appointment ccNSO delegate on NomCom FY2020 * Submission Council Statement Draft report 2nd ccNSO Review. * Selection 3rd member IFRT (non-ccNSO member) * Re-launch CSC Selection process. Thanks to Byron for his contributions and leadership to the CSC * ccNSO Statement on Streamlining Organisational Reviews * ccNSO Statement on Fundamental Bylaw Change 4. Update “end of ccNSO membership” following transfer of management of ccTLD Based on the discussions in Marrakech. Background information provided. Detailed report was submitted via e-mail, clarifications made by Joke during the call. No questions 5. Adoption FY 2020 NomCom Selection Report Annebeth Lange Alejandra: move, Byron: second, Abstain: none 6. Update ccNSO related ICANN Bylaw Change Repository Presented to GRC. Bart provides an overview of the changes with respect to the previous version of the repository. Stephen: Presentation to community might be needed. 7. Appointment ccNSO member RZERC Root Zone Evolution Review Committee Term of the appointed member ended. The current appointee, Peter Koch (.de) reapplied. Move? Stepen, seconds? Ajay. Questions or comments? Stephen thanks Peter. Highly-qualified Against? No Abstain? No unanimous vote 8. ccNSO Selection procedure Boards seat 11 8.1 Adoption Guidelines: ccNSO Selection procedure Boards seats 11 and 12 * Language suggestions from ICANN legal * Community request: we promised that in case after Q&A people are not happy with the nominees, they can choose not to support any of the candidates (option: none of the above). This option will also be provided if there is only 1 candidate. We still have to go for a vote, even if there is only 1 candidate. Risk: not so easy to convince people to cast their vote. New language was added to the guideline. Bart: redline version. 2 additions, 1 by Bart and 1 by Amy S. (ICANN legal) There is also a provision of a deadline for the appointment of the Board member seat 11, 6 months before the AGM in Hamburg at the end of 2020. Provision added on when a candidacy is terminated. Adjusted language to deal with the “none of the above” option. Quorum: 50% + 1 Termination of the nomination process. Stephen: question regarding “none of the above”, and the threshold of 50 + 1 * If none of the above wins, is the candidate eligible to stand again for the 2nd election? Katrina: yes. We do not prevent the person from standing again. The guideline is silent on this. * What if we do not meet the 22 April deadline? Katrina: we will address this under 8.2. Move? Stephen, Seconded? Alejandra Questions or comments? None Against? None Abstain? None. Guideline is adopted. 8.2. Adoption of the Timeline and appointment of Nomination Manager Timeline. 2 options, 1 with 2 sub-options. Introduction by Katrina, with visual representation of the timelines Cost of the vetting might be high, depending on the number of candidates. According to the guideline, we vet all candidates. (option 1). Option 2: we only vet the winner. The deadline according to the bylaws is 22 April 2020. The 2 board candidates appointed by the ccNSO cannot come from the same region. The NomCom looks into the general composition of the Board: they need to ensure diversity and regional requirements etc are met. The extra 6 months ensure that NomCom can meet all those requirements (e.g. max 5 from 1 Region). What happens if we fail to meet the 22 April deadline? We will still be able to appoint a director to the Board. What if we have an unexpected vacancy? In those cases we need to take into account the overall composition of the Board. 2 Q&A options: Montreal, ICANN66 in November 2019 | Cancun in March 2020. Risks for a Q&A in Montreal: results vetting unknown Option 1.A. Q&A prior to the vote, in Montreal. Option 1.B. Q&A prior to the vote in Cancun. We might not hit the deadline Option 2: Q&A in Montreal, due diligence after the vote. Option 1 A and option 2 are the only 2 options where we can meet the deadline. Stephen: Option 1.B violates both the just adopted Election Guideline as well as the ICANN Bylaws? Why even consider it? Katrina: only fair to consider all possible options. the number of candidates we want to vet might be a prohibiting factor. Nick: none of the options are perfect. We are close to November, and candidates need to get their act together as well. In the last elections we only had 2 candidates. The key idea is to get credible and well-qualified candidates. Worried if we go forward too quickly, that valid candidates are surprised by the early need to prepare themselves for a position that will become vacant in 2020. Katrina: the ccNSO has a good pool of candidates. But do they want to stand? Stephen: shares Nick’s concerns. Start publicity effort that if candidates are considering to stand, they are pre-warned. Katrina added that the community was warned already, but indeed pr is needed. Byron: concern by ICANN legal is unfounded from a practical standpoint. We never saw more than a couple candidates. Also unfounded from a theoretical standpoint: this is simply the cost of doing business. Thinks we should ignore it, and pick the right option. Ajay: 2nd option, vetting for 2 runner-ups? Katrina confirms that 1 person will be vetted, but indeed 2 candidates could be vetted as well. The idea was to save money for ICANN. Poll: 12 respondents [cid:image001.png@01D558FF.DA051A90] 3 votes to option 2. Moving forward with option 1A. Slot needed for the Q&A session in Montreal Nominations 11 September, 2 October Deadline to accept nominations 3 weeks later 3 weeks + 1 day: Notification to community Same day: Names submitted to icann legal for background check Q&A in Montreal Elections in January 2020 Move? Stephen, seconded? Ajay Joke appointed as nomination manager. Next year: do adjustments to the guideline, when we see how things are going. 8.3. Council Elections Term end in March 2020: EU: Giovanni, AF: Souleymane, AP: Hiro, LAC: Alejandra, N-Am:Stephen Joke appointed as election manager. Move? Alejandra, Seconded? Abdalla Vote, to appoint election manager and to approve timeline with Q&A in Montreal. Against? None, Abstain? none. 9. Emoji SG Final report Several recommendations. Bart: study group needs to confirm the final report. The chair was on holiday. We do not expect changes to the final report: it will be ready for adoption during the next ccNSO Council meeting. 10. IDN ccPDP related matters 10.1 Letter to the Board re IDN ccTLD overall proposed policy Thanks for the suggested edits. Final version was added to the background material for this call. Draft resolution to adopt the letter. Move? Stephen, Seconded? Giovanni. Against? None, Abstain? None. Approved 10.2 Adoption Final Report IDN PRT 10.3 Next Steps: Actions to implement recommendations IDN PRT Action item for the Secretariat: come up with a clear path forward by the Council meeting in September. 11. PDP 3 Part 1 Retirement – Update Short update provided by Stephen 12. Council Workshop Montreal (ICANN66) a. Topics for Council Workshop * Post fears and hopes (chaired by Giovanni) * Other topics from our Kobe meeting. b. Organizing the workshop Early September we will prepare a google doc with all topics for discussion and background information, plus opportunity to subscribe to organising the workshop. The workshop will take place at ICANN66 in Montreal, on Sunday 3 November. (2 blocks: 09:00-12:00) 13. Regular Agenda Montreal (ICANN66) a. Council meetings i. Prep meeting ii. Council meeting iii. Joint meeting with GNSO Council iv. Joint meeting with ALAC Alejandra presented the high-level ccNSO block schedule. The ccNSO starts on Saturday, 2 November. She also presented the very first draft of the ccNSO Members Meeting. Joint meeting: ccNSO & GAC (13:30-14:45). Most likely onboarding on PDP-retirement, and the ccNSO members meeting will run in parallel. Day 1 ends at 18:00. Q&A sessions with Board and council candidates and the currently appointed ccNSO Board candidates to be confirmed in terms of scheduling. Stephen. 4 November: Community Approval Forum overlaps with the Welcome Ceremony (if it happens on block 1). Stephen cannot attend both the PDP-ret session and the joint meeting with the GAC at the same time. b. Tech Day & Members meeting i. Tentative agenda members meeting ii. Plenary topics c. WG meetings d. Joint meeting with the Board e. Joint meeting with GAC Joint meeting between ccNSO & GAC. Eberhard proposed to hold an onboarding session on PDP-retirement. GAC proposed to have this onboarding session during the bilateral meeting. No need for the ccNSO to attend: this is not a bilateral meeting, and we again need to defer this to Cancun. Something to discuss in Montreal: how to shape bilateral meetings, especially with GAC. We have Giovanni and Pär from the GAC-side to agree on the agenda for that meeting, but input arrives from other angles too. 14. Update ECA & CSC a. ECA Adoption fundamental bylaw change in Board Retreat in September. Community Forum needed at the Montreal meeting. Non controversial. b. CSC 100 % PTI metrics were maintained. They continues to perform at a high level, and are responsive to the input by the CSC c. CSC Selection process (for information only) 15. Update ccNSO Review 16. Updates chair, vice-chairs and Councillors, Regional Organisations, Secretariat. 17. Updates WGs. a. GRC GNSO drafting team and GRC start working on common procedure on initiation of special IANA Functions Review Team. b. IGLC (progress to date) c. SOPC For the ccNSO SOPC, we will soon circulate an email to the Committee for a conf call in preparation of the double session in Montreal where we plan to discuss the work flow of the Committee, participation and engagement, future comment rounds, coordination with the gNSO and more. d. Meeting Programme Committee e. Emoji Study Group 18. Update liaisons a. Update ALAC Liaison (written update) b. Update GNSO Liaison (written update) In written 19. Next meetings · 19 September 2019 · 17 October 2019 · 6 November 2019 | ICANN66, Montreal (2-7 November) · 19 December 2019 20. AOB 21. Closure CCWG on Auction Proceeds: we need to discuss the next steps in the September council meeting. Thank you for joining. Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org