May 2019 - Ccnso-council - lists.icann.org

Re: [ccnso-council] Action item regarding my issue with the proposed Board Seat 11 and 12 Guideline
by Ajay DATA June 12, 2019

June 12, 2019

Hello Stephen, The way forward you suggested - "I suggest a more suitable proposal needs to have prospective candidates submit nominations, with appropriate seconds, acceptances, and a signed release for the background check to an appropriate entity within ICANN.ORG without public disclosure of the candidacy at the time."The above approach is already in practice by Nomcom and I have experienced the same. However I believe ICANN.ORG outsources the same. The entire thing was private and at-least I have not seen any information in public domain. Only after the candidate clears the background check, his name was announced. Before that no one knew in public domain that I applied for any position. Thanks. Ajay Data From: "Stephen Deerhake @ ASNIC" MailId : [91550901]To: ccnso-council Subject: [ccnso-council] Action item regarding my issue with the proposed Board Seat 11 and 12 GuidelineDate: 30 May 2019 02:37:21 PM Greetings, Please find attached (PDF A4 format) a detailed explanation of my issues with the proposed Guideline for the Election of Board Seats 11 and 12, as we discussed on our recent tele-conference. I am happy to discuss this further of course. Best Regards, /Stephen _______________________________________________Ccnso-council mailing listCcnso-council@icann.orghttps://mm.icann.org/mailman/listinfo/ccnso-council_______________________________________________By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.Do not Remove:[HID]20190530143721295[-HID]

8 8

apply for ccNSO Travel funding for ICANN66
by Joke Braeken May 30, 2019

May 30, 2019

Dear All, Today, Thursday 30 May 2019 from noon UTC onwards, it will be possible to apply for ccNSO travel funding for the next ICANN public meeting. ccNSO travel funding is available for a limited set of travellers for ICANN66, taking place between 2 and 7 November 2018 in Montréal, Canada. When can I apply? The application window opens today, Thursday, 30 May 2019 noon UTC, and closes Thursday, 13 June 2019 (23:59 UTC) (http://ccnso.icann.org/about/travel-funding<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org_about_t…>). No early/late submissions will be accepted. Who can apply? Funding to attend and participate in ICANN66 is made available to a small set of travellers, who meet the following requirement: They actively participate in the work of the ccNSO, and make a special contribution to its projects and meetings. Important: Applications which do not clearly state an active contribution, are not eligible and will not be taken into consideration. Examples of contributions to the work of the ccNSO: * an active engagement in a ccNSO working group, * a presentation at the ccNSO member meeting, * or other engagements that strengthen the activities of the ccNSO. What is included? One (1) ccNSO Travel Support slot may be awarded: either * On a fully supported basis (full funding), consisting of an economy class ticket to the travel destination, hotel costs for the approved duration of the trip and a per diem; or * On a partially supported basis (partial funding): * Option (a): economy class ticket to the travel destination. No hotel, no per diem; or * Option (b): hotel accommodation for the approved duration of the trip & per diem. No flight. Applicants are asked to specify their preference for support on a full or partial basis. If the latter, they are requested to state a preference for option (a) or option (b). If several applicants request partial funding (options (a) and (b)), more applicants can be funded. How can I apply? Full details on how to submit your application, including the applicable guideline, is available at: https://ccnso.icann.org/en/about/travel-funding What are the next steps? Once the application window closed, the ccNSO Travel Fund Committee members will evaluate all applications. The outcome of the ccNSO Travel Fund Committee deliberations will be published on the ccNSO website, latest mid-July 2019. All applicants will receive a personal notification as well. Thank you. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)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

1 0

Re: [ccnso-council] invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC)
by Joke Braeken May 30, 2019

May 30, 2019

Dear councillors, This is reminder regarding the email below. Your action is required by Friday, 31 May 2019 (noon UTC). Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)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 From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Friday, 24 May 2019 at 11:43 To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC) Dear Council members, On behalf of Joke: I am following up on Triage recommendation 25-2019 (Evolving ICANN’s Multistakeholder Model), which was recently approved by the ccNSO Council. Your action is required by Friday, 31 May 2019 (noon UTC). The recommendation specified that a Council statement is needed, as defined in https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-stat… <https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-stat…> Close date for public comments is 4 Jun 2019 23:59 UTC Short summary: Building on the conversation at ICANN64, a public comment invites the community to further define issues that challenge the effectiveness of ICANN's multistakeholder model. Read more here: https://www.icann.org/news/announcement-2019-04-25-en = = = = = |||| Your action is required ||| Kindly review the instructions included below, and provide input to the google document with the draft council statement.https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0Xr… Deadline for this: Friday, 31 May 2019 (noon UTC), allowing for sufficient time to produce a final version of the Council statement. = = = = = Instructions Commenters should refer to the draft "Issues List" that reflects input received from the ICANN community about how to improve the effectiveness of ICANN's multistakeholder model. We welcome all comments, and encourage you to focus on the following: 1. For each issue, or your issues of interest, provide a specific example about how the issue hampers the effectiveness of ICANN's multistakeholder model. Be sure to provide a specific and clear articulation of the issue so that it is clearly and fully defined. Please provide fact-based examples only. If offering a "new" issue to be considered, provide a clear articulation of the issue along with fact-based examples and a rationale about how the issue is hampering the effectiveness of ICANN's multistakeholder model. If you believe that an issue or issues do not belong on the Issues List, provide a rationale as to why the issue or issues should be removed. 1. Commenters are also invited to offer prioritization of the issues on the Issues List. When offering prioritization, carefully consider the following: * Issues that, if they are constructively addressed and solutions can be found, would have the greatest impact in making ICANN's multistakeholder model more effective and efficient. * Whether there are interdependencies between any of the issues that you are prioritizing. That is to say, for issue "A" to be addressed a solution for issue "B" must be addressed as well to achieve improvements in the effective functioning of ICANN's multistakeholder model. * Which issues could favorably impact the effectiveness of ICANN's multistakeholder model at a potentially lower cost? * Which issues could favorable impact the effectiveness of ICANN's multistakeholder model without introduction of unnecessary layers of process or bureaucracy? * Which issues could be combined or consolidated because their nature is so similar? When considering consolidating issues, carefully consider whether there are any interdependencies that argue against consolidation.

1 0

Action item regarding my issue with the proposed Board Seat 11 and 12 Guideline
by Stephen Deerhake ＠ ASNIC May 30, 2019

May 30, 2019

Greetings, Please find attached (PDF; A4 format) a detailed explanation of my issues with the proposed Guideline for the Election of Board Seats 11 and 12, as we discussed on our recent tele-conference. I am happy to discuss this further of course. Best Regards, /Stephen

1 0

FW: [Gnso-newgtld-wg-wt5] Work Track 5 Supplemental Initial Report - Published for Public Comment
by Katrina Sataki May 27, 2019

May 27, 2019

FYI From: Annebeth Lange <annebeth.lange(a)norid.no> Date: Saturday, 25 May 2019 at 12:38 To: "ccnso-wt5-participants(a)lists.norid.no" <ccnso-wt5-participants(a)lists.norid.no> Cc: Katrina Sataki <katrina(a)nic.lv> Subject: Re: [Gnso-newgtld-wg-wt5] Work Track 5 Supplemental Initial Report - Published for Public Comment Dear all, As you may know, the Work Track 5 has now completed going through the Supplemental Initial Report to check out that the staff and co-leads have represented the input commenters the correct way. We now have a better view of where the disagreement lays. On Wednesday 29th at 20 UTC the work will continue with the next step. We will then start with the discussion of the WT5 Summary Document, which later will be fed into the Subsequent Procedures Summary Document, where all the 5 work tracks will be gathered for discussion in the full group. The plan for Wednesday is to discuss Country & Territory Names in all alternatives (Recommendation 2 – 9). We know by now that the main disagreement lays with 3-char letters from ISO 3166. As representatives for ccTLDs it has not been essential that you have attended the meetings for some time where we have gone through other aspects for geographical names. But I will urge you to be an active participant on Wednesday 29th, as there will be focus on issues important for us. The agenda for the meeting will be sent out very soon. I hope to meet many of you at the teleconference Wednesday 29th. Have a wonderful weekend, Annebeth B.Lange, co-chair for ccNSO in Work Track 5

1 0

invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC)
by Bart Boswinkel May 24, 2019

May 24, 2019

Dear Council members, On behalf of Joke: I am following up on Triage recommendation 25-2019 (Evolving ICANN’s Multistakeholder Model), which was recently approved by the ccNSO Council. Your action is required by Friday, 31 May 2019 (noon UTC). The recommendation specified that a Council statement is needed, as defined in https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-stat… Close date for public comments is 4 Jun 2019 23:59 UTC Short summary: Building on the conversation at ICANN64, a public comment invites the community to further define issues that challenge the effectiveness of ICANN's multistakeholder model. Read more here: https://www.icann.org/news/announcement-2019-04-25-en = = = = = |||| Your action is required ||| Kindly review the instructions included below, and provide input to the google document with the draft council statement.https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0Xr… Deadline for this: Friday, 31 May 2019 (noon UTC), allowing for sufficient time to produce a final version of the Council statement. = = = = = Instructions Commenters should refer to the draft "Issues List" that reflects input received from the ICANN community about how to improve the effectiveness of ICANN's multistakeholder model. We welcome all comments, and encourage you to focus on the following: For each issue, or your issues of interest, provide a specific example about how the issue hampers the effectiveness of ICANN's multistakeholder model. Be sure to provide a specific and clear articulation of the issue so that it is clearly and fully defined. Please provide fact-based examples only. If offering a "new" issue to be considered, provide a clear articulation of the issue along with fact-based examples and a rationale about how the issue is hampering the effectiveness of ICANN's multistakeholder model. If you believe that an issue or issues do not belong on the Issues List, provide a rationale as to why the issue or issues should be removed. Commenters are also invited to offer prioritization of the issues on the Issues List. When offering prioritization, carefully consider the following: Issues that, if they are constructively addressed and solutions can be found, would have the greatest impact in making ICANN's multistakeholder model more effective and efficient. Whether there are interdependencies between any of the issues that you are prioritizing. That is to say, for issue "A" to be addressed a solution for issue "B" must be addressed as well to achieve improvements in the effective functioning of ICANN's multistakeholder model. Which issues could favorably impact the effectiveness of ICANN's multistakeholder model at a potentially lower cost? Which issues could favorable impact the effectiveness of ICANN's multistakeholder model without introduction of unnecessary layers of process or bureaucracy? Which issues could be combined or consolidated because their nature is so similar? When considering consolidating issues, carefully consider whether there are any interdependencies that argue against consolidation.

1 0

High-level notes and action items: ccNSO Council Meeting. 23 May 2019 (18 UTC)
by Joke Braeken May 23, 2019

May 23, 2019

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(a)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

1 0

MPC update - draft agenda ICANN 65
by Alejandra Reynoso May 23, 2019

May 23, 2019

Dear All Please find in attachment the documents shared today in our call. Note that the Welcome Coffee was confirmed for 8:00 - 8:30 *;)* Best regards, Alejandra -- [image: Photograph] *Alejandra Reynoso*Investigación & Desarrollo | Dominios .gt *P:* +502 23688565 *E:* alejandra.reynoso(a)cctld.gt 18 Ave. 11 <https://maps.google.com/?q=18+Ave.+11&entry=gmail&source=g>-42 Zona 15, V.H. III. Guatemala, Guatemala www.gt

2 1

Reminder | invitation to participate in the ccNSO Monthly Newsletter Satisfaction Survey
by Joke Braeken May 23, 2019

May 23, 2019

Hello everyone, This is a reminder that the ccNSO Secretariat is writing to request your participation in the Monthly ccNSO newsletter satisfaction survey. The purpose of the survey is to verify how well the ccNSO monthly newsletter meets your needs and expectations, and to identify aspects that need improvement. To participate, please click on the following link: https://www.surveymonkey.de/r/N8K3FGV This survey closes Friday, 30 May 2019 (23:59 UTC). Background You will be able to find the ccNSO Newsletter Archive and instructions on how to subscribe here: https://community.icann.org/display/ccnsowkspc/ccNSO+Newsletter If you have any questions, please contact joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Thank you in advance for providing this important feedback. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=Dw…> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso…> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DwMGa…>

1 1

Agenda and draft resolutions Council call 23 May 2019
by Bart Boswinkel May 23, 2019

May 23, 2019

Dear all, Please find included the agenda and draft resolutions for Council meeting 51, 23 May 2019, Kind regards, Bart Draft Agenda ccNSO Council Meeting 23 May 2019 Welcome and roll call Minutes & Action Items Minutes Minutes have been circulated by email 14 may 2019. Action items Action Item 150-01 Moving forward, book the Council face to face meetings in a separate room/u-shaped table set up. Completed Action Item 150-02: ccNSO Council Chair to ask ICANN Org and appointing organisations if there were any objections to moving forward with current appointees IFRT. Completed Action Item 150-03: ccNSO Council Chair to inform Annebeth Lange of support from Council on her reappointment to WT5. Completed Action Item 150-04: Council to adopt ToR for IDN overall policy preliminary review group, via email vote. Completed Action Item 150-05: Once ToR is adopted, issue call for volunteers, IDN preliminary review group. Completed Action Item 150-06: Secretariat to publish (travel funding) guideline as soon as possible Completed Action Item 150-07: Bart Boswinkel to send work plan to Council for email adoption decision Completed 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 Moorre (.ca) new member GRC Update & Next Steps IFRT appointment process For update and discussion Included for you reference the email from the Chair to other appointing organisations: Dear all, Following my email from 4 April, it has been very quiet on the list. Meanwhile, on 12 April, the ccNSO Council has requested the ICANN Board of Directors to amend the ICANN Bylaws (https://ccnso.icann.org/en/about/sataki-to-chalaby-12apr19-en.pdf ). However, as indicated in my previous email, we do not expect that the amended Bylaws will apply retrospectively. At our latest ccNSO Council meeting (23 April), the ccNSO Council further discussed different options to make sure that we move forward with the IFR. As stated in my email, the preferred option, which was re-confirmed, is our original proposal (included in the letter from Trang from 07 January) that - in light of the requested Bylaws change - the IFRT should start its work with three ccTLD representatives as defined in the Bylaws (although without a non-member ccTLD representative as specified in the Bylaws), i.e. with two appointed members and one interim member – all three representatives of ccTLDs that are members of the ccNSO. To date, the ccNSO has not been officially and formally informed about objections to this proposed path forward from any of the IFRT members appointing organisations. We believe that - unless a formal written objection to this plan from any appointing organisation is presented by 31 May 2019 - the IFRT should start its work as soon as possible with the current proposed membership. To date the proposed is supported by the RySG, GAC and SSAC. Discussion end of membership following transfer of management of ccTLD Introduction of topics Discussion on next steps Proposed Steps to clean-up ccNSO membership list To ensure that the ccNSO membership only includes ccTLD Managers, membership of entities that no longer are the Manager of a ccTLD needs to be ended and a termination process needs to be developed. Starting point for such a process is matching the ccNSO Membership with the IANA Database. In practice, a comparison is needed in case of transfer - on a per ccTLD basis - between the entity listed as ccNSO Member and the ccTLD Manager as included in the IANA delegation record. Once completed, those entities which are currently listed as Members, but are no longer the current ccTLD manager, should be informed and their membership should be ended. For future cases the secretariat and PTI staff are discussing an internal procedure to ensure the secretariat is kept abreast of transfers. Finally, the ccNSO Council is strongly advised to document how to end membership of the ccNSO after a transfer of management of the ccTLD and to inform the ccNSO Membership about it. There are two options to provide a sound basis for ending ccNSO membership after a transfer, revocation or retirement of the ccTLD: Without Bylaw change The documentation of the procedure is limited to documenting that following a transfer of the ccTLD management membership ends. One could argue that end of membership is implied, if the membership definition from the Bylaws is no longer met. Bylaw change Include in the Bylaws that if membership are not met anymore (i.e. the entity is no longer included in the IANA Rootzone database under the heading “ccTLD Manager” membership ends by means of the Bylaws. Moving forward, and in preparation of documenting a procedure, which option does Council prefer? Background: Included is an overview of changes recorded in the IANA Database since 1 January 2014. This search will now be extended going back to all changes affecting ccTLD management ( transfer and retirement) since 2003, the year when the ccNSO was established. Adoption Guideline: ccNSO Selection procedure Boards seats 11 and 12 For decision The GRC has updated the guideline to include the procedure to check background of candidates. Both the Council and membership have been offered opportunity to provide feed-back and comment. Draft Resolution Background The draft Guideline: ccNSO Nominations process ICANN Board seats 11 and 12, was shared with the Council and ccNSO membership to seek their input and feed-back on the proposed changes to section 3.5 of the 2016 Guideline. The proposed changes relate to the including a procedure with respect to a due diligence screening by an external provider. After considering comments received, the ccNSO Guideline Review Committee proposes to adopt the Guideline as presented to Council. Decision The ccNSO Council adopts the Guideline: ccNSO Nominations process ICANN Board seats 11 and 12, as presented (version – Draft Final May 2019), and requests the secretariat to publish the guideline on the ccNSO website and inform the community of this decision. This decision becomes effective seven ( 7) days after publication of the Guideline on the ccNSO website. Approval membership application .tr For Decision Draft Resolution The ccNSO Council approves the membership application of Bilgi Teknolojileri ve Iletisim Kurumu (BTK), the ccTLD Manager of .tr, and welcomes (BTK) as member of the ccNSO. Approval Amended Charter Meeting Programme Committee For Decision Draft Resolution The ccNSO Council adopts the amended Charter of the Meeting Programme Committee (MPC) as proposed, and request the secretariat to inform the MPC accordingly. Approval Amended Charter Triage Committee To reflect outcome of the workshop For Decision Draft Resolution The ccNSO Council adopts the amended Charter of its Triage Committee as proposed, and request the secretariat to publish it on the ccNSO Website and inform the community accordingly. Appointment chair IDN PDP Review team For decision Draft Resolution Background At the first meeting and in accordance with the Terms of Reference, the members of the IDN PDP Preliminary Review Team (IDN PRT) nominated Ajay Data, NomCom appointed Councillor to become their chair, which he accepted. Decision The ccNSO Council appoints Ajay Data, NomCom appointed Councillor as chair of the Chair of the IDN PDP Preliminary Review Team (IDN PRT). ccPDP 3 Part 1 Retirement – Update Informational Agenda Marrakesh Council meetings i. Prep meeting ii. Council meeting iii. Joint meeting with GNSO Council Tech Day & Members meeting Meeting with GAC WG meetings Update ECA & CSC ECA CSC CSC Selection process (for information only) Update ccNSO Review Updates chair, vice-chairs and Councillors, Regional Organisations, secretariat. Updates WG. GRC IGLC (progress to date) SOPC Meeting Programme Committee Emoji Study Group Update liaisons Update ALAC Liaison (written update) Update GNSO Liaison (written update) Next meetings June – Marrakech (26 June) July/August – 22 August September 19 October 17th November -Montreal (2-7 November) December 19th AOB Closure

2 1