November 2018 - Ccnso-council

Draft Agenda and initial batch background material upcoming Council meeting 6 December 2018, 11.00 UTC
by Bart Boswinkel Dec. 9, 2018

Dec. 9, 2018

Dear all, Please find included draft agenda and initial set background documents Kind regards, Bart Agenda and resolutions ccNSO Council Meeting 6 December 2018, 11.00 UTC 1) Welcome and Apologies Attendance list is available at: http://ccnso.icann.org/about/council/attendance.htm 2) Minutes and Actions Minutes f-2-f meeting Barcelona Action Item 145-01: The ccNSO Council requests the Secretariat to publish this resolution as soon as possible after the closure of this ccNSO Council meeting (CCWG-Accountability) Completed Action Item 145-02: The GRC is requested to inform the Council and broader community on progress with respect implementation WS 2 recommendations at the next face to face meeting in Kobe (ICANN64). On-going Action Item 145-03: Secretariat to draft resolution and send it to the council list. Councilors to suggest edits and at the end have an online vote. Completed 3) Overview inter-meeting Council decisions ccNSO Council decision on CCEG Letter to CCWG IG on rescinding Letter on IFRT send to the Board, seeking structural solution. Selection and appointment ccNSO participants ICANN leadership training: Biyi Oladipo and Peter Koch Confirmation NomCom Selection criteria. Appointment Jordan Carter (.nz) ccNSO Review working party 4) Regular ccNSO Council Elections 2018 Approval of Election Report 5) Terms Of Reference Mentor/Mentee Project For decision. Adoption of Terms of Reference. Call for volunteers for committee 6) Letter Roelof Meijer on defensive nature Terms of Reference Emoji Study Group Roelof Meijer send a letter to Council on defensive nature of the Terms of Reference Emoji Study Group. Discussion response. 7) IFRT: next steps appointment volunteers Following appointment of 3 ccNSO members, including an interim appointment, ICANN informed the ccNSO Council that either the ccNSO should try again to find a non-ccNSO ccTLD manager who is interested, or support i.e. non – objection would be required from all appointing groups. If latter option either ccNSO Council could opt to seek support or ICANN Org would. 8) Guidelines ccNSO 8.1 Board Nomination Process Comments from Council Next steps: community consultation, updates by GRC if any, adoption by Council 8.2 Selection and Appointment Liaisons For adoption 8.3 Updated Travel Funding Guideline For Final Comments Council Next steps: community consultation, updates by GRC if any, adoption by Council 8.4 Review effectiveness ccTLD World list For discussion: Issues and way forward. The ccTLD World list was created in context of the IANA Stewardship Transition process to be able to reach out to and inform all ccTLD managers. After transition the list was maintained, however it has proven some entries on the list and procedural documentation are outdated. Proposed way forward: Short term. Subscribe individual councilors and Regional Organizations representatives, taking into account ICANN’s GDPR related procedures (consent form). Long term. Secretariat to review procedural documentation, also in light of GDPR related procedural requirements and develop maintenance plan. Review and plan to be completed by February Council, t inform the community at the Kobe meeting. 9) ccTLD Financial Contribution discussion: next steps 10) Nominate ICANN Fellowship Programme Mentor Alejandra volunteered 11) PDP Retirement Informational. Update progress (Stephen Deerhake) 12) ccNSO organizational review Progress to date and next steps (Katrina) 13) ECA, CSC and RZERC Update 13.1 ECA (Stephen Deerhake) 13.2 CSC (Byron) 13.3 CSC Effectiveness review (Debbie) 13.4 RZERC (placeholder) 14) ICANN64 Kobe 14.1 ccNSO Council meetings Council Workshop (Sunday, block 1 and 2) Council Prep Meeting (Sunday lunch) Council meeting with ALAC (Sunday, 17.00-17.45) Council meeting GNSO ( Monday lunch) Council meeting (Wednesday, block 5, other, smaller room) 14.2 ICANN64 ccNSO Meetings Agenda (Alejandra) Members day meetings Meeting with GAC Meeting the ICANN Board 14.3 WG & other meetings Tech Day (Monday) CSC meeting ( Monday morning) WG meetings (starting Saturday!!) ccNSOP Cocktail (Hiro) 15) Council Updates 15.1 Chair Update 15.2 Vice-Chair Update 15.3 Councilors Update 15.4 Regional Organizations Update 15.5 Secretariat update 16) WG update 16.1 GRC update (Katrina) 16.2 CCWG Auction Proceeds (Peter Vergote) 16.3 SOPC (Giovanni) 16.4 GNSO PDP Subsequent procedures WT 5 16.5 Emoji Study Group (Alejandra) 16.6 Update joint ccNSO-SSAC Working PartyGuidelines Risk Management Panel (Katrina) 17) Liaison Updates 17.1 GNSO Update (written updates) 17.2 ALAC update (written updates) 18) Next meetings (2019) Tentatively for 2019 January 17th February 14th March – Kobe (9-14 March) April 18th May 16 or 23rd June – Marrakech (24-27 June) July/August – 22 August September 19 October 17th November -Montreal (2-7 November) December 19th 19) AOB 20) Closure

2 1

ccNSO Review Survey Available for Community Input
by Joke Braeken Nov. 29, 2018

Nov. 29, 2018

Dear all, Meridian Institute<http://www.merid.org/>, the independent examiner conducting the second review of the Country Code Names Supporting Organization (ccNSO), has published a survey for community input. https://www.icann.org/news/announcement-2-2018-11-27-en Click here<https://www.surveymonkey.com/r/ccnsoreview> to take the survey now. The aim of the survey is to collect input from those who have interacted with ccNSO or have suggestions for ways to improve it. The survey is informed by learnings from Meridian Institute's research and interviews conducted to date. Following the close of the survey on 21 December 2018 at 23:59 UTC, Meridian Institute will evaluate responses, along with input received via interviews and other forums, as input to its assessment report. The assessment report is expected to be posted for community consultation in February 2019. As with all ICANN Organizational Reviews<https://www.icann.org/resources/reviews/org>, the second ccNSO Review is following a two-phased approach, in which the independent examiner first completes its assessment and then makes recommendations to address the findings noted during the assessment. Background The purpose of the Bylaws-mandated<https://www.icann.org/resources/pages/governance/bylaws-en/#article4.4> ccNSO Review is to determine (i) whether the ccNSO has a continuing purpose within the ICANN structure; (ii) how effectively the ccNSO fulfills its purpose and whether any change in its structure or operations is desirable to improve the ccNSO's effectiveness; and (iii) the extent to which the ccNSO as a whole is accountable to its organizations, committees, constituencies, and stakeholder groups. Meridian Institute was selected to conduct the second ccNSO Review in August 2018<https://www.icann.org/news/announcement-2-2018-08-31-en>. 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

looking back at ICANN63: MPC feedback on ccNSO members meeting satisfaction survey results
by Joke Braeken Nov. 29, 2018

Nov. 29, 2018

Dear all, The ccNSO Meetings Programme Committee has finalised its ICANN63 “Feedback on feedback”: this document aims to evaluate the community feedback received regarding the ccNSO Members meeting in Barcelona and provides the feedback from the ccNSO Meetings Programme Working Group in response. Consult the document here: https://ccnso.icann.org/en/meetings/barcelona63/evaluation.htm 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

proposed triage recommendation(s) [58 until 60 - 2018]
by Joke Braeken Nov. 28, 2018

Nov. 28, 2018

Dear ccNSO council members, Please find below the proposed triage recommendation(s) [58 until 60 - 2018]. Kindly provide me with your input by the end of 30 November 2018, 23:59 UTC, in case you do not agree with the proposed recommendation(s). Thank you. = = = = Number: 58-2018 Topic: Policy Status Report: Inter-Registrar Transfer Policy (IRTP) Summary: ICANN Org seeks community input on the IRTP Policy Status Report. In addition to feedback on the report, ICANN Org also requests that interested registrars and registrants complete the online survey athttps://www.surveymonkey.com/r/FLQRD3K [surveymonkey.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.surveymonkey.com_r…> to provide further details on their experience with domain name transfers. Read more: https://www.icann.org/news/announcement-2018-11-14-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Date received: 16 November 2018 Last day for comments/input/response, if any: 24 December 2018 Recommended action, if any: None Expertise needed, if any: Inter-registrar transfers, domain name transfers, transfer policy, gTLDs Date of submission to Triage Committee: 22 November 2018 Deadline Triage Committee input: 26 November 2018, 23:59 UTC Date of submission to Council: 28 November 2018 Deadline Council decision: 30 November 2018, 23:59 UTC Impact on ccNSO/ccTLDs: Low = = = = Number: 59-2018 Topic: Application for New Uniform Domain Name Dispute Resolution Policy (UDRP) Dispute-Resolution Service Provider Summary: ICANN Org requests community feedback on an application from an organization seeking approval as a new Uniform Domain Name Dispute Resolution Policy (UDRP) dispute-resolution service provider. Read more: https://www.icann.org/news/announcement-2018-11-16-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Date received: 19 November 2018 Last day for comments/input/response, if any: 4 January 2019 Recommended action, if any: Share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>, ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and possibly on the ccNSO social media channels Expertise needed, if any: Domain name dispute resolution, gTLDs Date of submission to Triage Committee: 22 November 2018 Deadline Triage Committee input: 26 November 2018, 23:59 UTC Date of submission to Council: 28 November 2018 Deadline Council decision: 30 November 2018, 23:59 UTC Impact on ccNSO/ccTLDs: Low = = = = Number: 60-2018 Topic: Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team Summary: This public comment proceeding seeks to obtain input on the Initial Report of the EPDP on the Temporary Specification for gTLD Registration Data Team. The EPDP Team is tasked with evaluating the Temporary Specification on gTLD Registration Data (Temp Spec) and deciding whether it should become an ICANN Consensus Policy as is, or with modifications, while complying with the GDPR and other relevant privacy and data protection laws and regulations. The EPDP Team will hold a webinar on Thursday, 29 November at 14:00 UTC. The webinar will provide an overview of the Initial Report as well as more information on how to submit public comments. Read more: https://www.icann.org/news/announcement-2-2018-11-21-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Date received: 22 November 2018 Last day for comments/input/response, if any: 21 December 2018 Recommended action, if any: Share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>, ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and possibly on the ccNSO social media channels (completed – seen the short deadline) Expertise needed, if any: Contracted Party Agreements, Policy Development, Privacy, Top-Level Domains Date of submission to Triage Committee: 22 November 2018 Deadline Triage Committee input: 26 November 2018, 23:59 UTC Date of submission to Council: 28 November 2018 Deadline Council decision: 30 November 2018, 23:59 UTC Impact on ccNSO/ccTLDs: low 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

public comments period Initial Report of the New gTLD Auction Proceeds Cross-Community Working Group extended
by Joke Braeken Nov. 28, 2018

Nov. 28, 2018

Dear all, In order to ensure the community has sufficient time to respond, the public comment period for the Initial Report of the New gTLD Auction Proceeds Cross-Community Working Group<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> has been extended to 11 December 2018 at 23:59 UTC. Further information can be found in the email below and here: https://www.icann.org/news/announcement-2018-11-26-en 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-members <ccnso-members-bounces(a)icann.org> on behalf of Joke Braeken <joke.braeken(a)icann.org> Date: Monday, 22 October 2018 at 10:36 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org>, ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-members] Initial Report of the New gTLD Auction Proceeds Cross-Community Working Group is out for public comments Dear all, The Initial Report of the New gTLD Auction Proceeds Cross-Community Working Group is out for public comments. This public comment proceeding seeks to obtain input on the Initial Report of the New generic Top Level Domain (gTLD) Auction Proceeds Cross-Community Working Group (CCWG). The CCWG is tasked with providing guidance on a framework to disburse the funds generated from auctions of last resort in 2012 application round of the new gTLD Program. According to the CCWG's charter, the objective of the group is to develop a proposal(s) for consideration by the chartering organizations: Address Supporting Organization (ASO), the At-Large Advisory Committee (ALAC), the Country Code Names Supporting Organization (ccNSO), the Generic Names Supporting Organization (GNSO), the Governmental Advisory Committee (GAC), the Security and Stability Advisory Committee (SSAC), and the Root Server System Advisory Committee (RSSAC). Deadline for comments: 27 November 2018 (23:59 UTC) Read more here: https://www.icann.org/public-comments/new-gtld-auction-proceeds-initial-201… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> The CCWG-AP at ICANN63 * Monday, 22 October 2018 | room 115 Join a meeting of the CCWG during which it expects to share its Initial Report and proposed recommendations with the broader community, encourage input to the public comment forum and answer any questions there may be. https://63.schedule.icann.org/meetings/901647 [63.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__63.schedule.icann.org_…> * Tuesday, 23 October 2018 | room 114 ccNSO-appointed co-chair to the CCWG new gTLD Auction Proceeds Working Group Ching Chiao will provide an update and explanation of the next steps during the ICANN63 ccNSO Members Meeting. Consult the agenda and remote participation details here: https://community.icann.org/pages/viewpage.action?pageId=90768548 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 0

Minutes for review: 24 October Barcelona
by Kimberly Carlson Nov. 27, 2018

Nov. 27, 2018

Dear Councilors, Here are the minutes from the 24 October meeting in Barcelona for review. Thank you, Kim _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org Top of Form Bottom of Form

1 0

EPDP Webinar replacing EPDP Team meeting on Thursday 29 November at 14:00 UTC
by Kimberly Carlson Nov. 27, 2018

Nov. 27, 2018

Dear all, Please note that a webinar is planned for Thursday 29 November at 14.00 UTC, replacing the EPDP Team meeting, to provide those interested with an overview of the Initial Report as well as more information on how to submit public comments. To sign up for the webinar, please contact gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Kind regards, Kim Carlson _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org Top of Form Bottom of Form

1 0

Election results: ccNSO Council member - European region
by Joke Braeken Nov. 26, 2018

Nov. 26, 2018

Dear all, The voting in the elections for the position of ccNSO council member - European region closed last week, on Thursday, 22 November 2018 (23:59 UTC). This is to inform you about the election results. In accordance to the applicable rules, two candidates from the European region were nominated, seconded and have accepted their nomination. Consequently, an election was held among the ccNSO members of the European Region according to the timeline previously agreed upon by the ccNSO Council. Election Results Only ccNSO members from a Geographic Region are allowed to vote for candidates to the ccNSO Council from that Geographic Region. When the ballots were distributed, the ccNSO counted 44 members from the European region. Out of 44 ccNSO members from the European region, 34 members (77%) casted their votes: Marta Moreira Dias received 6 votes, Nick Wenban-Smith received 28 votes. There were no members that voted for the option “none of the above”. Next Steps The Election Report as prepared by the Election Manager, will be discussed at the ccNSO Council meeting on 6 December. (add link). As only one candidate was nominated and seconded within the nomination period for the African, Asia-Pacific, Latin American / Caribbean and North American regions, no elections needed to be held in those regions. Since at the close of nominations there are no more valid candidates in the aforementioned geographic regions than there are seats on the ccNSO Council available for those regions, then the nominated candidates shall be selected to serve on the ccNSO Council. Links * Announcement call for nominations: https://ccnso.icann.org/en/announcements/announcement-11sep18-en<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> * Announcement closure call for nominations: https://ccnso.icann.org/en/announcements/announcement-04oct18-en<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> * Announcement candidate list: https://ccnso.icann.org/en/announcements/announcement-11oct18-en.htm<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> * Nominations and secondments archive: https://mm.icann.org/pipermail/ccnso-nominations/ * Timeline: https://community.icann.org/download/attachments/88574272/Timeline2018_elec… * Applicable ccNSO guideline: https://ccnso.icann.org/sites/default/files/field-attached/guideline-ccnso-… * Recordings Q&A session, ccNSO Members meeting ICANN63, Barcelona: Download .ZIP of All Audio: http://audio.icann.org/meetings/bcn63/bcn63-OPEN-2018-10-23-T1207-114-ccNSO…<https://urldefense.proofpoint.com/v2/url?u=http-3A__audio.icann.org_meeting…> Adobe Connect: https://participate.icann.org/p4icjgtssq5/ English Audio: http://audio.icann.org/meetings/bcn63/bcn63-OPEN-2018-10-23-T1207-114-en-cc…<https://urldefense.proofpoint.com/v2/url?u=http-3A__audio.icann.org_meeting…> * Candidate statement by Nick Wenban-Smith<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_wor…> * Candidate statement by Marta Moreira Dias<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_wor…> 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

CORRECTION regarding my stated views regarding the proposall to have the Board make an "interpretation" regarding the Bylaw IRFT Bylaw problem
by Stephen Deerhake ＠ ASNIC Nov. 24, 2018

Nov. 24, 2018

My comment regarding this should have read: Being a rather strict Being a rather strict constructionalist when it comes to the Bylaws, I cannot concur with Katrina’s suggestion regarding having the Board “interpret” the relevant Bylaw. To me, that’s a very slippery slope. Best regards, /Stephen

2 1

Letter to the Board re IFRT - CONSOLIDATED&UPDATED
by Katrina Sataki Nov. 23, 2018

Nov. 23, 2018

Dear Colleagues, Here’s the new version that takes into account Giovanni’s and Hiro’s suggestions and proposes a new version for the last paragraph: -- During the bilateral meeting between the ICANN Board and ccNSO on 24 October, 2018, we briefly discussed the issue the ccNSO is facing in selecting a non-ccNSO member for the IANA Function Review team (IFRT). As agreed, the ccNSO Council is happy to share its considerations on this matter. According to section 18.7 (a) and (b) of the ICANN Bylaws, the ccNSO Council is required to appoint 3 members on the IFRT: (a) Two representatives from ccNSO member ccTLD registry operator representatives; (b) at least one (1) non-ccNSO ccTLD representative who is associated with a ccTLD registry operator that is not a representative of the ccNSO. This needs to be read in the context of section 18.8 (c): the ccNSO and Registries Stakeholder Group shall not appoint multiple members who are citizens of countries from the same ICANN Geographic Region. On 20 July 2018, a communication about the coming call for volunteers was sent out to all ccNSO email lists and to the ccTLD world list to which all ccTLD managers are subscribed. Subsequently: * From 10 August to 24 August 2018, the call for volunteers was announced to all email lists; * From 27 August to 10 September 2018, the second call for volunteers was announced to all email lists; * As suggested in the Bylaws, the ccNSO Council reached out to the regional ccTLD organisations that informed their membership and encouraged those who were interested to apply; * An announcement was published on the ccNSO Website on 16 August 2018; * We sent reminders to the email lists on 14 August, 21 August and 7 September 2018. Unfortunately, despite the above efforts, the ccNSO was not able to find a volunteer from a ccTLD registry operator that is not a member of the ccNSO. To ensure that the ccTLD community at large is properly represented, the ccNSO Council decided to appoint three members to the IFRT. The third person, also a representative of a member of the ccNSO, is appointed on an interim basis. This person will step down and be replaced on the IFRT if a candidate from a non-ccNSO ccTLD manager with the required skills and experience, as defined in the original call for volunteers, steps forward. It must be noted that if this person is from an ICANN Geographic Region of one of the two other selected and most preferred representatives from the ccNSO membership, it will have a knock-on effect: to meet the hard-coded diversity criteria, the representative will have to step down. Since 1 October 2016 when the new ICANN Bylaws came into effect, the membership of the ccNSO has grown by 6%, and about two-thirds of ccTLD registries have already become members of the ccNSO. In future, the continuing growth of the ccNSO and/or the geographic diversity requirement will make it harder and harder - if not impossible - to select the most qualified representatives of ccTLDs as members to the IFRT. Therefore, we propose that we agree on a common understanding of the section 18.7 (a) and (b) to make sure that the ccTLD community is fully represented on the first IFRT. -- Kind regards, ]{atrina From: Stephen Deerhake @ ASNIC [mailto:sdeerhake@nic.as] Sent: Friday, November 23, 2018 4:00 PM To: Katrina Sataki <katrina(a)nic.lv> Cc: Giovanni Seppia <Giovanni.Seppia(a)eurid.eu>; ccNSO Council <ccnso-council(a)icann.org> Subject: Re: [ccnso-council] Letter to the Board re IFRT Katrina/Giovanni, I concur with Giovanni’s modifications to Katrina’s original, as well as Katrina’s modifications to Giovanni’s text. I think it’s a “go”. Being a rather strict constructionalist when it comes to the Bylaws, I can concur with Katrina’s suggestion regarding having the Board “interpret” the relevant Bylaw. To me, that’s a very slippery slope. Best, /Stephen PS: The Board could act fairly quickly; the hold up will be with the ECA, particularly if this ends up being a fundamental bylaw change, which would trigger an Approval Action, which are tricker to manage than a Rejection Action. Depuis mon mobile, désolé pour le style On Nov 22, 2018, at 12:24, Katrina Sataki <katrina(a)nic.lv <mailto:katrina@nic.lv> > wrote: Hi Giovanni, Thank you for your suggestions. A few comments back: >On 20 July 2018, initial information a communication about the coming call for volunteers was sent out to all ccNSO email lists under auspices of the ccNSO, including the ccTLD world list to which all ccTLD managers are subscribed. Technically, the ccTLD World list is not a ccNSO mailing list. Calling it a ccNSO email list is not correct. Any other suggestions how to say that? >Since 1 October 2016 when the new ICANN Bylaws came into effect, the membership of the ccNSO has grown by 6%. In future, the continuing growth of the ccNSO and/or the geographic diversity requirement will make it harder and harder - if not impossible - to select the most qualified representatives of ccTLDs-non ccNSO members as members to the IFRT. No, we won’t be able to select the most qualified representatives from ccTLDs, not just non ccNSO members. The idea is that if we have, for example, one qualified ccNSO member and one non-qualified non member, we have to select the non-member. That inevitably leads to the situation when we cannot have the best people. We should be able to select the most qualified people, whether they are members or non-members should not play any role. Therefore, I would like to keep it the way it was, i.e. “representatives of ccTLDs” >Therefore, our advice would be to change / interpret amend the section 18.7 (a) and (b) to mean as follows: We won’t be able to amend the Bylaws so quickly. The Board needs to approve the IFRT. I think we should ask them to interpret the Bylaws in a way that would allow us to appoint three members, instead of two. Any other suggestions for this wording? Kind regards, ]{atrina From: Ccnso-council <ccnso-council-bounces(a)icann.org <mailto:ccnso-council-bounces@icann.org> > On Behalf Of Katrina Sataki Sent: 22 November 2018 17:23 To: 'ccNSO Council' <ccnso-council(a)icann.org <mailto:ccnso-council@icann.org> > Subject: [ccnso-council] Letter to the Board re IFRT Dear Colleagues, As you remember, the Board asked us to put in writing our struggle with the selection of ccTLD representatives to the IFRT. Please find a draft below. Please let me know by 30 November if you have any suggestions on how to improve the text. Thank you! ]{atrina -- During the bilateral meeting between the ICANN Board and ccNSO on Wednesday, 24 October, 2018, we briefly touched upon the issue the ccNSO is facing in selecting a non-ccNSO member on the IANA Function Review team (IFRT). As agreed, the ccNSO Council is sending you a more detailed explanation of the issue. According to section 18.7 (a) and (b) of the ICANN Bylaws, the ccNSO Council is required to appoint 3 members on the IFRT: (a) Two representatives from ccNSO member ccTLD registry operator representatives; (b) at least one (1) non-ccNSO ccTLD representative who is associated with a ccTLD registry operator that is not a representative of the ccNSO. This needs to be read in the context of section 18.8 (c ): the ccNSO and Registries Stakeholder Group shall not appoint multiple members who are citizens of countries from the same ICANN Geographic Region. On 20 July, initial information about the coming call for volunteers was sent out to all email lists under auspices of the ccNSO, including the ccTLD world list to which all ccTLD managers are subscribed. Following that, * from 10 August to 24 August, the call for volunteers was announced to all email lists; * from 27 August to 10 September, second call for volunteers was announced to all email lists; * as suggested in the Bylaws, the ccNSO Council reached out to the Regional ccTLD organisations who informed their members on their respective email lists and encouraged their members to apply; * An announcements was published on the ccNSO Website; * Several reminders we sent to the email lists – 14 August, 21 August, 7 September. Unfortunately, despite the efforts listed above, the ccNSO was not able to secure a volunteer from a ccTLD registry operator that is not a member of the ccNSO. To ensure that the ccTLD community at large is properly represented, the ccNSO Council decided to appoint three members to the IFRT. The third person, also a representative of a member of the ccNSO, is appointed on an interim basis. This person will step down and be replaced on the IFRT if a candidate from a non-ccNSO ccTLD manager with the required skills and experience, as defined in the original call for volunteers, steps forward. It must be noted that if this person is from an ICANN Geographic Region of one of the two other selected and most preferred representatives from the ccNSO membership, it will have a knock-on effect: to meet the hard-coded diversity criteria, the representative will have to step down. Since 1 October 2016 when the new ICANN Bylaws came into effect, the membership of the ccNSO has grown by 6%. In future, the continuing growth of the ccNSO and/or the geographic diversity requirement will make it harder and harder - if not impossible - to select the most qualified representatives of ccTLDs as members to the IFRT. Our advice would be to change / interpret the section 18.7 (a) and (b) to mean: “Three representatives appointed by the ccNSO from ccTLD registry operator representatives; to the extent possible and reasonable, the ccNSO should strive to appoint at least one non-ccNSO ccTLD representative who is associated with a ccTLD registry operator that is not a representative of the ccNSO.” -- Disclaimer: This email and any attachment hereto is intended solely for the person to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient or if you have received this email in error, please delete it and immediately contact the sender by telephone or email, and destroy any copies of this information. You should not use or copy it, nor disclose its content to any other person or rely upon this information. Please note that any views presented in the email and any attachment hereto are solely those of the author and do not necessarily represent those of EURid. Any processing of personal data via email is done in accordance with our Privacy Policy <https://eurid.eu/en/other-infomation/privacy-policy> . While all care has been taken to avoid any known viruses, the recipient is advised to check this email and any attachment for presence of viruses. Other languages: English <http://www.eurid.eu/en/legal-disclaimer> Estonian <http://www.eurid.eu/et/legal-disclaimer> Italian <http://www.eurid.eu/it/legal-disclaimer> Maltese <http://www.eurid.eu/mt/legal-disclaimer> Romanian <http://www.eurid.eu/ro/legal-disclaimer> Swedish <http://www.eurid.eu/sv/legal-disclaimer> Czech <http://www.eurid.eu/cs/legal-disclaimer> Spanish <http://www.eurid.eu/es/legal-disclaimer> Latvian <http://www.eurid.eu/lv/legal-disclaimer> Dutch <http://www.eurid.eu/nl/legal-disclaimer> Slovak <http://www.eurid.eu/sk/legal-disclaimer> Greek <http://www.eurid.eu/el/legal-disclaimer> Danish <http://www.eurid.eu/da/legal-disclaimer> French <http://www.eurid.eu/fr/legal-disclaimer> Lithuanian <http://www.eurid.eu/lt/legal-disclaimer> Polish <http://www.eurid.eu/pl/legal-disclaimer> Slovenian <http://www.eurid.eu/sl/legal-disclaimer> Bulgarian <http://www.eurid.eu/bg/legal-disclaimer> German <http://www.eurid.eu/de/legal-disclaimer> Gaelic <http://www.eurid.eu/ga/legal-disclaimer> Hungarian <http://www.eurid.eu/hu/legal-disclaimer> Portuguese <http://www.eurid.eu/pt/legal-disclaimer> Finnish <http://www.eurid.eu/fi/legal-disclaimer> Croatian <http://www.eurid.eu/hr/legal-disclaimer> _______________________________________________ Ccnso-council mailing list Ccnso-council(a)icann.org <mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-council

2 1