Hello everyone, Please find the high-level notes and action items from today’s council meeting included below. Thank you. Best regards, Joke 1. Welcome and roll call Several apologies received. Call is quorate. 2. Minutes & Action Items Minutes were circulated via email. No comments received, minutes are approved All action items are approved 3. Intermeeting decisions (since 18 April) · Approval Annual Work Plan · Appointment members IDN policy review team · Adoption Council Statement IRP · Adoption decision to conclude end of ccNSO membership of former manager .tr · Appointment Alyssa Moore (.ca) new member GRC 4. Update & Next Steps IFRT appointment process We reached out to Trang, to understand ICANN’s position. Email was sent to all appointing organisations, those that received the initial proposal and exchanged info, including the initial proposal from Trang to move fwd with the 3 cc-representatives, if no objection is received. Recap: * We asked for a bylaw change. Council decided that we would like to move fwd with our regional proposal. We stated that there have been no formal objections in written by other appointing organisations. IFRT should start asap with current proposed membership, unless objections come in by the end of may . Some express support received, no objections received. * Stephen: why 31 may? (2 weeks after the communication was sent) What is the GNSO’s view as a whole? (All appointing organisations, no overall GNSO point of view.) We had unofficial information from one of the SGs, but this was never been confirmed. Katrina will send a reminder tomorrow. Email was also forwarded to Goeran and our Board members. Goeran forwarded it to several others, incl Cherine, Theresa, JJ. 5. Discussion end of membership following transfer of management of ccTLD Difficulties already were discussed in Kobe. Bylaws clearly say who is eligible to be a ccNSO member, namely ccTLD Manager. But, there are changes possible, in who is the ccTLD manager. We do not know when a transfer happened. Some ccNSO members are technically not members anymore. End their membership becomes necessary. 2 ways: 1. Automatically, since the bylaw requirement is not met. No need to change the bylaws in that case. The moment you cease to be ccTLD Manager, you cannot be a member any longer. 2. With bylaw change Secretariat reached out to PTI and received info on transfers that happened in the past. Also included in the Board resolutions. First there is a Board resolution, and then it takes around a week, when the IANA DB is changed. Technically, we look at the IANA DB. However, the moment when the Board decides, the old manager is not the ccTLD manager anymore. Important: there is a one-week gap. Stephen: thinks a bylaw change is needed. Have a backstop in the bylaw. Standard bylaw, would go up for rejection action. Demi: My option: - no changes on Bylaws and - we wait for IANA database changes to reflect them on ccNSO membership
 Katrina: you cannot do a switch. The new ccTLD manager might not want to be a ccNSO member. We need an explicit application by the new ccTLD manager Nick: was ICANN legal consulted? Bylaws are not as clear as they could be. Californian law could be different. Action item #1: Staff to consult ICANN legal for advice regarding membership status after a transfer of the ccTLD manager and bylaw interpretation. Issue Katrina wishes to bring to the attention of the ccNSO Council: We were contacted by the primary contact in the .tr membership application. He was contacted via whatsapp. Phone number in the application form. Number was not in the IANA DB. Person was asking whether it was normal he was contacted that way. 2 PDFs with a business proposal were sent to him. Regarding EAI. Any comments from councillors on the call? None. This is not normal: the application was not published yet, and used for business purposes by a councillor. We do not have a written code of behaviour. But, we have never had any issues like that. Secretariat received the commercial proposals via PDF. DataXGenTechnology was the sender of that business proposal. This company that sent the business proposal, is owned by one of our councillors. This undermines the trust in the council, we should deal with this in a transparent and open manner. Stephen: this breach from the phone number came from a councillor? Katrina: yes. From this moment onwards, phone/email will not be shared with council anymore. We will not publish this type of information in future any longer. To avoid this type of behaviour in future. This is not acceptable. We might need standards of behaviour 6. Adoption Guideline: ccNSO Selection procedure Boards seats 11 and 12 We need the guideline for the future elections. Most likely by September, but no timeline available yet. Stephen: votes no to this guideline. Believes he should have pushed his viewpoint harder within GRC. Strongly believes vetting should be done prior to the announcement to the community, so that issues can be dealt with privately. Katrina: against the process. Raising the issue now is not within the process. Text from guideline was misread. Byron: is there an urgency to get this done today? Could we defer to the next meeting? Katrina: we can defer. We need to run the nomination and election process in Sept/October. We need the guideline by July, process to be started in August. GNSO and ccNSO are the only ones that don’t do background checks on their appointed board members. We do not have time to send it to the community one more time. Nick: preferable for all councillors to be comfortable. If we have time, we should see if we can address Stephen’s concerns. Katrina: we move/second and then discuss. That is the process. Alejandra moved, Byron seconded. Postponed to ICANN65. Action item #2: Stephen to submit his comments regarding this guideline to council mailing list by next Thursday 7. Approval membership application .tr Move? Demi. Seconded? Hiro Approve? All in favour 8. Approval Amended Charter Meeting Programme Committee Move? Alejandra, Seconded? Byron. Questions for MPC chair? Alejandra clarified that regarding the updated charter, the term start was further detailed, based on discussions during the ICANN64 MPC face-to-face meeting. Object? None. Abstain? None. All in favour. 9. Approval Amended Charter Triage Committee Amended charter triage committee, to reflect outcomes of the Kobe workshop Move? Pablo, Seconded? Hiro 10. Appointment chair IDN PDP Review team Move? Demi, Seconded? Pablo, Against? None Abstain? None 11. ccPDP3, Part 1: Retirement – Update Progress is being made. Group plans to meet face to face in Marrakech 12. Agenda Marrakech a. Council meetings i. Prep meeting ii. Council meeting iii. Joint meeting with GNSO Council b. Tech Day & ccNSO Members meeting c. Meeting with GAC d. WG meetings Not all WG/Committees will meet this time. We are meeting with GNSO and GAC, but not with anybody else. Board is meeting is not meeting with any groups during the policy forum. Meeting with ALAC postponed to ICANN66. Alejandra provides clarifications on the proposed ccNSO block schedule. 2 HIT sessions, 2 CC sessions. No final confirmation of the schedule yet. Monday: DoH session, future of multi stakeholder session. Thu: GDPR, universal acceptance. Proposed ccNSO Members Meeting. Day 1: Tue, Day 2: Wed. policy session in block 3, to accommodate joint meeting with the GAC. quite some volunteers for the ccTLD News Session. 1 remote presentation. 14. Update ECA & CSC a. ECA Rejection action petition on budget and strategic plan. Upcoming rejection action petition period with SSAC bylaw change. Stephen was invited to present to ALAC at their upcoming meeting in Marrakech regarding empowered community. Will ask for council’s approval b. CSC Had its monthly meeting on 16 May. Few processes well under way. Some work on those. Update on effectiveness review. Subject to a number of reviews. In general CSC agreed fully with the effectiveness review recommendations. Confusion regarding individual complaints: will be clarified. How to deal with attendance on CSC. Need to be strict about that. Initial terms of some members and liaisons come to an end. Skill matrix: CSC needs to be populated by the right profiles. Also some updates on next pieces of work, updating specific matrix. Work on IDN table. Changes to SLA’s in terms of technical amendments. CSC requested some travel funding for its members. Probably will not be granted for this year. Byron will be lobbying the powers that be in Marrakech. Stephen: how can we help you lobby for the travel support? Byron’s term is up in October. New members finally approved by GNSO and ccNSO councils in September. c. CSC Selection process (for information only) 15. Update ccNSO Review Review WP received the report with 49 recommended considerations. That is too much, to be rationally implemented. Concerns were shared with Merid.org. Clear recommendations needed. Merid.org will come up with a shorter list. Stephen: supports what Katrina said. 16. Updates chair, vice-chairs and Councillors, Regional Organisations, secretariat. Pablo: NomCom’s activities. 7 final candidates that will be interviewed in Marrakech. Also the final candidates for ccNSO were selected. 17. Updates WG. a. GRC Currently looking into Special IFR, joint call with draft team from the GNSO. Need to coordinate. Last resort: if everything else fails. CSC, escalates to PTI, then to CEO, then to Board, and then the special IFR comes. b. IGLC (progress to date) First meeting took place. Thinking about working methods etc c. SOPC No recent activities d. Meeting Programme Committee See update by Alejandra e. Emoji Study Group We need to contact the ccTLDs that are listed in the draft report Then the draft report will go out for public comment. Finalise in Marrakech 18. Update liaisons a. Update ALAC Liaison (written update) b. Update GNSO Liaison (written update) 19. Next meetings · June – ICANN65 Marrakech (Wed, 26 June | 17:00-18:30 local | room Opale) Councillors are kindly invited to be on time: there will be a council group picture · July/August – 22 August · September 19 · October 17th · November -Montreal (2-7 November) · December 19th 20. AOB Katrina: recommendations from Triage Committee. Council needs to prepare 2 statements. 1st one on ICANN multistakeholder model. Due: 4 june. Google doc will be circulated. Please work together, and help shaping this council statement. Second one on organisational reviews. Bart and Katrina will draft something. 21. Closure Thank you all. Bye 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