February 2019 - Ccnso-council

FINAL REMINDER - action required: selection process ccNSO appointed liaison to the GNSO
by Joke Braeken Feb. 11, 2019

Feb. 11, 2019

Dear members of the ccNSO council, This is a kind reminder about the selection process for the ccNSO appointed liaison to the GNSO. Your action is required by tomorrow, Tuesday, 12 February 2019 (23:59 UTC) Further information can be found in the email below. 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 [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…> From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Joke Braeken <joke.braeken(a)icann.org> Date: Tuesday, 5 February 2019 at 11:40 To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] action required: selection process ccNSO appointed liaison to the GNSO Dear councillors, The call for volunteers for the ccNSO appointed liaison to the GNSO closed yesterday, 4 February 2019, 23:59 UTC). The secretariat is now initiating the selection process for the ccNSO appointed liaison to the GNSO. Your action is required by Tuesday, 12 February 2019 (23:59 UTC) Please find included: * Description of the selection process (see below) * Application material as submitted by the 3 candidates, in alphabetical order: Espinoza, Luis Diego (Akamai Technologies) Moore, Alyssa (.ca) Simon, Maarten (.nl) INSTRUCTIONS: * Please select your preferred candidate by sending an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>, no later than Tuesday, 12 February 2019 (23:59 UTC) , with the subject line: ccNSO appointed Liaison to the GNSO. * Your most preferred candidate should receive three (3) points, the second candidate two (2) points, and the third and least preferred candidate one (1) point. If you believe a candidate does not meet the criteria: please assign zero (0) points. A kind reminder that the ccNSO Secretariat will track and publish for each council member its participation in an election process. Thank you and kind regards, Joke Braeken SELECTION PROCESS The applicants in alphabetical order: Espinoza, Luis Diego (Akamai Technologies) Moore, Alyssa (.ca) Simon, Maarten (.nl) The application material as submitted by the applicants is included in attachment. Selection and procedure You are requested to assess which candidate you find most suited as ccNSO appointed member to the GNSO, based on the material provided. To assist you in your assessment, the expectations and responsibilities of the ccNSO appointed liaison to the GNSO can be consulted here: https://ccnso.icann.org/en/announcements/announcement-21jan19-en.htm [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> INSTRUCTIONS: * Please select your preferred candidate by sending an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>, no later than Tuesday, 12 February 2019 (23:59 UTC) , with the subject line: ccNSO appointed Liaison to the GNSO. * Your most preferred candidate should receive three (3) points, the second candidate two (2) points, and the third and least preferred candidate one (1) point. If you believe a candidate does not meet the criteria: please assign zero (0) points. Administrative Procedure After we received your email, we will acknowledge receipt and include a ballot number and date of receipt. On Wednesday, 13 February 2019, the ccNSO Secretariat will circulate an email to the list, which will include an overview in the following format: - Ballot number, - Date ballot was received, - preferred candidate per ballot. This email will also include the total level of preference per candidate. The candidate receiving most supportive votes, is selected. In the event the two candidates are equally preferred; a run-off selection will be needed. The volunteer who receives the majority of the votes lodged shall be considered to be appointed by the ccNSO Council as of the date of adoption of the Election Report, foreseen for the 14 February 2019 council meeting. The Chair of the ccNSO will inform the ICANN Secretary and the respective Supporting Organization or Advisory Committee of the appointment. Background * ccNSO Guideline: Liaison and Observers https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/… [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…> * The current GNSO liaison, Biyi Oladipo (.ng), will take a seat on the ccNSO Council at the end of ICANN64 in Kobe. Consult the latest council election report here [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…>. * Announcement call for volunteers: https://ccnso.icann.org/en/announcements/announcement-21jan19-en.htm [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> 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 [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

Recommendations for Managing Internationalized Domain Name Variant Top-Level Domains Published
by Joke Braeken Feb. 8, 2019

Feb. 8, 2019

Dear All, ICANN announced the release of the Recommendations for Managing Internationalized Domain Name (IDN) Variant Top-Level Domains (TLDs)<https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-0…> as a collection of six documents. https://www.icann.org/news/announcement-2019-02-05-en These recommendations have been developed by the ICANN organization with community feedback received during the Public Comment<https://www.icann.org/public-comments/managing-idn-variant-tlds-2018-07-25-…> period. A. IDN Variant TLD Implementation – Executive Summary<https://www.icann.org/en/system/files/files/idn-variant-tld-exec-summary-25…> [PDF, 70 KB] B. IDN Variant TLD Implementation – Motivation, Premises and Framework<https://www.icann.org/en/system/files/files/idn-variant-tld-motivation-prem…> [PDF, 391 KB] C. IDN Variant TLD Implementation – Recommendations and Analysis<https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations…> [PDF, 382 KB] D. IDN Variant TLD Implementation – Rationale for RZ-LGR<https://www.icann.org/en/system/files/files/idn-variant-tld-rationale-lgr-2…> [PDF, 497 KB] E. IDN Variant TLD Implementation – Risks and their Mitigation<https://www.icann.org/en/system/files/files/idn-variant-tld-risks-mitigatio…> [PDF, 230 KB] F. IDN Variant TLD Implementation – Appendices (A: Definitions, B: Use of ROID, C: Limiting Allocated Variant TLDs)<https://www.icann.org/en/system/files/files/idn-variant-tld-appendices-25ja…> [PDF, 530 KB] While the Internet community has often expressed a need for IDN variant TLDs, appropriate technical details and procedures have not been in place to support these. The ICANN Board resolved on 25 September 2010 that "no variants of gTLDs will be delegated ... until appropriate variant management solutions are developed." Subsequent work by the ICANN org and the community on the analysis of issues for Arabic<http://archive.icann.org/en/topics/new-gtlds/arabic-vip-issues-report-07oct…> [PDF, 1.06 MB], Chinese<http://archive.icann.org/en/topics/new-gtlds/chinese-vip-issues-report-03oc…> [PDF, 2.86 MB], Cyrillic<http://archive.icann.org/en/topics/new-gtlds/cyrillic-vip-issues-report-06o…> [PDF, 1 MB], Devanagari<http://archive.icann.org/en/topics/new-gtlds/devanagari-vip-issues-report-0…> [PDF, 461 KB], Greek<http://archive.icann.org/en/topics/new-gtlds/greek-vip-issues-report-07oct1…> [PDF, 354 KB], and Latin<http://archive.icann.org/en/topics/new-gtlds/latin-vip-issues-report-07oct1…> [PDF, 425 KB] scripts in 2011, integrated in the Integrated Issues Report (IIR)<https://www.icann.org/en/system/files/files/idn-vip-integrated-issues-final…> [PDF, 2.14 MB] (2012), identified two challenges: (i) there is no accepted definition for variant TLDs, and (ii) there is no 'variant management' mechanism for TLDs. For the first issue, the Root Zone Label Generation Rules (RZ-LGR) Procedure<https://www.icann.org/en/system/files/files/draft-lgr-procedure-20mar13-en.…> [PDF, 1.39 MB] was developed with the support of the community and adopted by the ICANN Board on 11 April 2013 for implementation. The Procedure has been implemented and RZ-LGR<https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en> has been developed for six scripts, while other scripts are being added as their proposals<https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en> are finalized by the relevant script communities<https://www.icann.org/resources/pages/generation-panel-2015-06-21-en>. This enables a transparent and predictable mechanism for identification of variant labels going forward For the second issue, the ICANN org has undertaken a detailed examination to develop a set of recommendations on variant management mechanisms for TLDs, which have been finalized based on the community input. The recommendations, in summary, include the following: 1. RZ-LGR must be the only source for valid TLDs and their variant labels. 2. IDN variant TLDs {t1, t1v1, …} must be allocated to same entity. 3. Same label under IDN variant TLDs s1.{t1, t1v1, …} must be registered to the same entity. 4. Second-level variant labels under IDN variant TLDs {s1, s1v1, …}.{t1, t1v1, …} must be registered to the same entity. 5. Second-level IDN tables offered under IDN variant TLDs must be harmonized. 6. IDN variant label allocatable or activated under IDN variant TLDs may not necessarily be the same. 7. The registry service providers must be the same for IDN variant TLDs. 8. Existing policies and associated procedures for TLDs must be updated to accommodate the recommendations for IDN variant TLDs. 9. All remaining existing TLD policies must apply to IDN variant TLDs, unless otherwise identified. These recommendations and associated analysis in the six documents will be presented for further consideration to the ICANN Board, anticipated in March 2019. 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

ICANN Publishes the First Monthly Report on Generic Top-Level Domain Security Threats
by Joke Braeken Feb. 8, 2019

Feb. 8, 2019

Dear All, ICANN published the first monthly report providing statistics and insight into security threats to generic top-level domains (gTLDs). https://www.icann.org/news/announcement-2019-02-04-en This report of the Domain Abuse Activity Reporting (DAAR) System provides the first in an ongoing series of domain name security threat reports which will be released on a monthly basis. This release is accompanied by a context document explaining the methodology behind the DAAR System. Monthly reports from previous months (January 2018 through Dec 2018) will be published before the end of February 2019. DAAR was created in response to community requests for neutral, reliable, persistent, and reproducible data from which security threat and abuse analyses could be performed. The DAAR project has produced a system using a published and community-vetted methodology for studying and reporting domain name registration and security threat behavior across top-level domain (TLD) registries and registrars. The overarching purpose of DAAR is to aggregate and analyze security threats as monitored by the publicly-available domain reputation providers and report findings to the ICANN community. This data can be used to facilitate informed policy decisions. DAAR provides only gTLD registry reports at the moment. More detailed registrar portfolio reporting would require identifiable domain name registration data. A system that will collect and analyze the necessary registrar data remains under development. ICANN's Security, Stability, and Resiliency (SSR) team expects to add registrar reporting in the future. Inclusion of country code TLD (ccTLD) registries, where the ccTLD registry information is voluntarily provided by the ccTLD administrator, is also planned for future releases. Access the DAAR January 2019 report here<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_a0…> [PDF, 514 KB] and the context document here<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_j1…> For more information, visit DAAR's dedicated webpage by clicking here<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_G0…>. 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

ANN's Security Stability and Resiliency (SSR) Team Responds to Public Input on Domain Abuse Activity Reporting (DAAR) Reviews
by Joke Braeken Feb. 8, 2019

Feb. 8, 2019

Dear all, ICANN published a summary of the public input on the Domain Abuse Activity Reporting (DAAR) methodology. The Office of the Chief Technology Officer Security, Stability, and Resiliency (OCTO-SSR) Team carefully reviewed the recent public input submissions from the ICANN community and provided responses where relevant. DAAR was designed to provide the ICANN community with reliable, persistent, and reproducible data from which security threat (abuse) analyses could be performed. To foster confidence in the DAAR system, the ICANN organization has engaged two independent experts to review the methodology paper, comment on the threat data, and experiment with the reporting system. To further incorporate community opinion on DAAR and the independent reviews, ICANN org asked for public input between 20 July 2018 and 24 August 2018. The findings and recommendations from the reviewers and parties who provided input will be considered in the final drafting of the methodology paper and future modifications to the DAAR system. Here are links to the DAAR methodology paper, reviews, and public input: https://www.icann.org/news/announcement-2019-02-01-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

ICANN Releases its Third Report on Global Legislative and Regulatory Developments
by Joke Braeken Feb. 8, 2019

Feb. 8, 2019

Dear all, ICANN has released its third report on global legislative and regulatory developments<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_kC…>, highlighting a limited list of recent and pending legislative and regulatory initiatives on privacy/data protection and cybersecurity across the world. The report is a continuation of the initiative launched last year to identify legislative efforts across the globe early-on, to raise awareness within ICANN, and consider potential impacts. Moving forward, the global legislative and regulatory developments reports will be published three times a year, parallel to the publishing of the ICANN Organization Report to the Board. ICANN would like to take this opportunity to thank everyone who has provided feedback on the previous two reports<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_kC…>, and looks forward to hearing from you about any high-impact developments in the e-privacy and cybersecurity ecosystem that should be tracked in future reports. You can send your comments and/or information about new developments in your region to trackingfeedback(a)icann.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_lh…>. Read more: https://www.icann.org/news/announcement-2019-01-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

Community Dialogues on Consumer Safeguards
by Joke Braeken Feb. 8, 2019

Feb. 8, 2019

Dear all, ICANN recently published a recording of a recent discussion on consumer safeguards in the Domain Name System (DNS). The recording<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_uZ…>, presentation<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_VM…> and supplementary documents are now available. The meeting, held on 11 January 2019, in Washington, D.C., was intended to gauge local interest in holding a community-wide dialogue on consumer safeguards topics, such as DNS infrastructure abuse, at a future ICANN meeting. Nearly 50 ICANN community members participated and concluded that a sub-group of the participants should attempt to draft an agenda for a community-wide dialogue at a future ICANN meeting. If you have additional input on these topics as well as the safeguards summary document<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_z0…>, please send it to Jamie Hedlund, Senior Vice President for Contractual Compliance & Consumer Safeguards at jamie.hedlund(a)icann.org<mailto:jamie.hedlund@icann.org>, or Bryan Schilling, Consumer Safeguards Director at bryan.schilling(a)icann.org<mailto:bryan.schilling@icann.org>. Read more here: https://www.icann.org/news/announcement-2-2019-01-28-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

Re: [ccnso-council] action required: selection process ccNSO appointed liaison to the GNSO
by Joke Braeken Feb. 8, 2019

Feb. 8, 2019

Dear members of the ccNSO council, This is a kind reminder about the selection process for the ccNSO appointed liaison to the GNSO. Your action is required by Tuesday, 12 February 2019 (23:59 UTC) Further information can be found in the email below. 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 From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Joke Braeken <joke.braeken(a)icann.org> Date: Tuesday, 5 February 2019 at 11:40 To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] action required: selection process ccNSO appointed liaison to the GNSO Dear councillors, The call for volunteers for the ccNSO appointed liaison to the GNSO closed yesterday, 4 February 2019, 23:59 UTC). The secretariat is now initiating the selection process for the ccNSO appointed liaison to the GNSO. Your action is required by Tuesday, 12 February 2019 (23:59 UTC) Please find included: * Description of the selection process (see below) * Application material as submitted by the 3 candidates, in alphabetical order: Espinoza, Luis Diego (Akamai Technologies) Moore, Alyssa (.ca) Simon, Maarten (.nl) INSTRUCTIONS: * Please select your preferred candidate by sending an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>, no later than Tuesday, 12 February 2019 (23:59 UTC) , with the subject line: ccNSO appointed Liaison to the GNSO. * Your most preferred candidate should receive three (3) points, the second candidate two (2) points, and the third and least preferred candidate one (1) point. If you believe a candidate does not meet the criteria: please assign zero (0) points. A kind reminder that the ccNSO Secretariat will track and publish for each council member its participation in an election process. Thank you and kind regards, Joke Braeken SELECTION PROCESS The applicants in alphabetical order: Espinoza, Luis Diego (Akamai Technologies) Moore, Alyssa (.ca) Simon, Maarten (.nl) The application material as submitted by the applicants is included in attachment. Selection and procedure You are requested to assess which candidate you find most suited as ccNSO appointed member to the GNSO, based on the material provided. To assist you in your assessment, the expectations and responsibilities of the ccNSO appointed liaison to the GNSO can be consulted here: https://ccnso.icann.org/en/announcements/announcement-21jan19-en.htm [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> INSTRUCTIONS: * Please select your preferred candidate by sending an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>, no later than Tuesday, 12 February 2019 (23:59 UTC) , with the subject line: ccNSO appointed Liaison to the GNSO. * Your most preferred candidate should receive three (3) points, the second candidate two (2) points, and the third and least preferred candidate one (1) point. If you believe a candidate does not meet the criteria: please assign zero (0) points. Administrative Procedure After we received your email, we will acknowledge receipt and include a ballot number and date of receipt. On Wednesday, 13 February 2019, the ccNSO Secretariat will circulate an email to the list, which will include an overview in the following format: - Ballot number, - Date ballot was received, - preferred candidate per ballot. This email will also include the total level of preference per candidate. The candidate receiving most supportive votes, is selected. In the event the two candidates are equally preferred; a run-off selection will be needed. The volunteer who receives the majority of the votes lodged shall be considered to be appointed by the ccNSO Council as of the date of adoption of the Election Report, foreseen for the 14 February 2019 council meeting. The Chair of the ccNSO will inform the ICANN Secretary and the respective Supporting Organization or Advisory Committee of the appointment. Background * ccNSO Guideline: Liaison and Observers https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/… [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…> * The current GNSO liaison, Biyi Oladipo (.ng), will take a seat on the ccNSO Council at the end of ICANN64 in Kobe. Consult the latest council election report here [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…>. * Announcement call for volunteers: https://ccnso.icann.org/en/announcements/announcement-21jan19-en.htm [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> 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 [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

Re: [ccnso-council] draft agenda and preliminary draft resolutions ccNSO Council meeting 14 February noon UTC
by Bart Boswinkel Feb. 8, 2019

Feb. 8, 2019

Dear all, Please find included background material with respect to agenda items 9 and 14.2. Kind regards, Bart From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Thursday, 7 February 2019 at 20:36 To: "ccnso-council(a)icann.org" <ccnso-council(a)icann.org> Subject: [ccnso-council] draft agenda and preliminary draft resolutions ccNSO Council meeting 14 February noon UTC Dear all, Please find included the draft agenda and preliminary resolutions for the upcoming ccNSO Council meeting Agenda and preliminary Draft Resolutions ccNSO Council Meeting 14 February 2019, 12.00 (noon) UTC 1) Welcome and Apologies Attendance list is available at: http://ccnso.icann.org/about/council/attendance.htm 2) Minutes and Actions Minutes, circulated 29 January 2019, no comments received Ongoing/open from meeting prior meeting 147: Action Item 146-08: Secretariat to develop maintenance plan ccTLD World email list, to be presented at the February meeting. Completed, on agenda as item 6. Action Item 146-10: The Chair of the ccNSO Council along with Peter Vergote and the Secretariat to inform the community of the topic of moving the joint meeting with the GAC to Sunday so they can prepare for a more meaningful discussion on this subject. To be send late January or in February Overtaken by events, see item <meeting with GAC> Action Items meeting 147: Action Item 147-01: Chair is requested to inform relevant ICANN staff regarding ccNSO members Ethos Award Panel Completed Action Item 147-02: Call for volunteers for both the ccNSO liaison to the GNSO and the ccNSO Liaison to ALAC. Completed, item 4 on agenda Action Item 147-03: The secretariat is requested to inform the ccTLD community regarding adoption of statement/comment - Supplemental Initial Report of the New gTLD Subsequent Procedures Policy Development Process Working Group Completed Action Item 147-04: Chair/secretariat - create a repository of Bylaw changes that are needed over time and those which are already identified Completed, item 7.1 on the agenda Action Item 147-05: Chair, Secretariat and/or GRC determine recommended path forward by next meeting in February (include description of issue, analysis of what is needed in sense of change, what type of bylaw change is requested [rejection action, pdp, etc]). Repository has been created, discussion item 7.2 and 7.3 on the agenda. 3) Overview inter-meeting Council decisions No Intersessional decisions 4) Appointment ccNSO Liaisons to GNSO and ALAC For decision Background material: Guideline: ccNSO Liaisons and Observers (https://ccnso.icann.org/sites/default/files/field-attached/guideline-liaiso…) Draft resolution Background The current liaison to the GNSO (Biyi Oladipo) will take a seat on Council starting after the ccNSO Council meeting in Kobe. The current liaison to the ALAC (Wafa Dahmani), has accepted a position on the ASO AC, and by March 2019 her first 2 years term ends. In order to ensure continuity, the Council is advised to launch a call for volunteers. At meeting 17 January 2019 the Council decided to launch a call for volunteers for both the ccNSO liaison to the GNSO and the ccNSO Liaison to ALAC in accordance with the Guideline: ccNSO Liaisons and Observers. Accordingly the secretariat send the call by Monday 21 January 2019 to the relevant email lists and received 3 application for position GNSO liaison (Maarten Simon (.nl), Luis Diego Espinoza (related to .NA), and Alyssa Moore (.ca)) and 1 application for ALAC liaison (Segun Akano, (.ng)). Council then selected 1 GNSO liaison candidate, following the procedure included in the Guideline, Council selected the GNSO liaison. Decision In accordance with the Guideline: ccNSO Liaisons and Observers (https://ccnso.icann.org/sites/default/files/field-attached/guideline-liaiso…) as adopted by Council, the following persons were selected by Council: < insert name > as Liaison to the GNSO <insert name> as liaison to the ALAC. Both Liaisons will take their seat at the end of the ccNSO Council meeting in Kobe, Japan and invited to attend the ccNSO Council workshop. The chair is requested to inform the ALAC and GNSO of the appointments and the secretariat is requested to add them to the relevant ccNSO email lists. 5) Appointment volunteers SOPC For decision. Draft Resolution Background The SOPC has reviews its current membership and would like to seek new members to ensure continuity. The secretariat launched a call for volunteers and the following persons put their name forward: Dmitry Kohmanyuk (.ua) Biyi Oladipo (.ng) Atsushi Endo (.jp) In addition, and for the record, Nicholas Lisse applied to be observer to the group. To become an observer does not require an action from Council. Decision The ccNSO Council appoints the listed candidates as members of the SOPC for a term of 2 years taking effect immediately. The ccNSO Council requests the Secretariat to inform the candidates and include them on the relevant email list and list them on the SOPC webpage. 6) Update ccTLD World email procedure Introduction In preparation of the December Council meeting, the Secretariat prepared a document, listing the issues as identified in the text of the procedural background documentation for the ccTLD world mailing list, and a high-level analysis of the current list of subscribers. To remedy the issues identified with the ccTLD world mailing list two actions are proposed: update of the procedural documentation update procedure to ensure the list of subscribers is up to date The background material provides more details. For decision: adoption of the amended ccTLD world email list procedural documentation. A redline version is available at: https://docs.google.com/document/d/1tVZ3SyeUDMeWHx2KeNZWhOm97Uem1Ol6PiaGjh-…. Once adopted the secretariat will implement procedure to ensure list of subscribers is up to date. 7) ccNSO related ICANN Bylaw changes 7.1 Repository to be maintained by the ccNSO See Background material 7.2 Change definition of ccNSO membership For discussion & Next steps Background. The membership definition of the ccNSO was changed late in the CWG Stewardship process. Change process. As Article x is not a fundamental Bylaw, it follows the pattern of a regular Bylaw change, open to rejection action by the Decisional participants. Using the post October 2016 change of Article XI (GNSO) as an example (see: GNSO Resolution 20180130-1 Adoption of Revised GNSO Operating Procedures and Proposed Modifications of the ICANN Bylaws consistent with the recommendations of the Bylaws Drafting Team.). Proposed actions. The ccNSO Council consults ccNSO membership on proposed change. Staff is requested to prepare a slide deck. Suggestion is to check whether broader consultation is needed and consult broader community as well (public comment on requested change, requests the Board to change the relevant section in Article X. Note the Board will have to follow its procedure to allow for a standard bylaw change. 7.3 Change ccNSO Council appointed members requirement IFRT(section 18 ICANN Bylaws) For discussion & Next steps Background The IANA naming Function review was launched by the ICANN Board of Directors in September 2018. However, the Review Team has not been formed to date. One of the issue is the requirement that the ccNSO Council appoints a representative from a ccTLD Manager that is not a member of the ccNSO. As indicated before to the ICANN Org and Board, the ccNSO Council anticipates that this problem will only get worse over time, with the increase of members in the ccNSO and in light of the relative small size of the vast majority of the non-ccNSO members and required skill and expertise and time-commitment. As Article 18 is one of the Fundamental Bylaws, and introduced as part of the IAAN Stewardship Transition Process, further discussion with community, ICANN Org and ICANN Board is warranted on next steps. 8) Adoption ccNSO Terms Of Reference ccNSO Internet Governance Liaison Committee For decision Background material. Draft Terms of Reference for Committee Background In November 2018, the ccNSO Council decided to withdraw from the CCWG Interne Governance and not to support the CCEG Charter. However, the ccNSO Council decided that in light of the importance of Internet Governance and interest of ccTLD member is the topic, to create a IG Liaison Committee to further liaise with the members of the CCWG IG / CCEG, ICANN staff and other active participants from the broader ICANN community. If adopted secretariat will send out a call for volunteers. 9) Support Approach joint ccNSO – SSAC Working Party re Risk Mitigation Panel Fast Track Process For discussion and/or decision (Katrina Sataki) Background material: Final draft Guideline Risk Implementation Cover letter 10) CSC Effectiveness Review 10.1 Update of Review (Debbie) 10.2 ccNSO Council statement 11) PDP Retirement Update Informational. Update progress (Stephen Deerhake) 12) ccNSO organizational review Progress to date and next steps (Katrina Sataki) 13) ECA, CSC and RZERC Update 13.1 ECA (Stephen Deerhake) 13.2 CSC (Byron) 13.3 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) Note that the Council will need to select its chair and two(2) vice-chairs 14.2 Council Workshop: topics for discussion Facilitated workshop - Workplan 2019-2020 - Table top exercises: Rejection Action Process & Triage Committee - Expectations of role of a councilor - Assignment Roles and Responsibilities Councillors Please note the included overview of current roles and responsibilities. 14.3 ICANN64 ccNSO Meetings Agenda (Alejandra) - Members day meetings - Meeting with GAC - Meeting the ICANN Board: Suggest topics for meeting with Board? 14.4 WG & other meetings Tech Day (Monday) CSC meeting ( Monday morning) WG meetings (starting Saturday!!) ccNSO Cocktail 15) Council Updates 15.1 Chair Update Background: notes ccNSo Chair and vice-chairs call with CEO & president ICANN 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 Emoji Study Group (Alejandra) 17) Liaison Updates 17.1 GNSO Update (written update) 17.2 ALAC update (written update) 18) Next meetings (2019) 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

1 0

draft agenda and preliminary draft resolutions ccNSO Council meeting 14 February noon UTC
by Bart Boswinkel Feb. 7, 2019

Feb. 7, 2019

Dear all, Please find included the draft agenda and preliminary resolutions for the upcoming ccNSO Council meeting Agenda and preliminary Draft Resolutions ccNSO Council Meeting 14 February 2019, 12.00 (noon) UTC 1) Welcome and Apologies Attendance list is available at: http://ccnso.icann.org/about/council/attendance.htm 2) Minutes and Actions Minutes, circulated 29 January 2019, no comments received Ongoing/open from meeting prior meeting 147: Action Item 146-08: Secretariat to develop maintenance plan ccTLD World email list, to be presented at the February meeting. Completed, on agenda as item 6. Action Item 146-10: The Chair of the ccNSO Council along with Peter Vergote and the Secretariat to inform the community of the topic of moving the joint meeting with the GAC to Sunday so they can prepare for a more meaningful discussion on this subject. To be send late January or in February Overtaken by events, see item <meeting with GAC> Action Items meeting 147: Action Item 147-01: Chair is requested to inform relevant ICANN staff regarding ccNSO members Ethos Award Panel Completed Action Item 147-02: Call for volunteers for both the ccNSO liaison to the GNSO and the ccNSO Liaison to ALAC. Completed, item 4 on agenda Action Item 147-03: The secretariat is requested to inform the ccTLD community regarding adoption of statement/comment - Supplemental Initial Report of the New gTLD Subsequent Procedures Policy Development Process Working Group Completed Action Item 147-04: Chair/secretariat - create a repository of Bylaw changes that are needed over time and those which are already identified Completed, item 7.1 on the agenda Action Item 147-05: Chair, Secretariat and/or GRC determine recommended path forward by next meeting in February (include description of issue, analysis of what is needed in sense of change, what type of bylaw change is requested [rejection action, pdp, etc]). Repository has been created, discussion item 7.2 and 7.3 on the agenda. 3) Overview inter-meeting Council decisions No Intersessional decisions 4) Appointment ccNSO Liaisons to GNSO and ALAC For decision Background material: Guideline: ccNSO Liaisons and Observers (https://ccnso.icann.org/sites/default/files/field-attached/guideline-liaiso…) Draft resolution Background The current liaison to the GNSO (Biyi Oladipo) will take a seat on Council starting after the ccNSO Council meeting in Kobe. The current liaison to the ALAC (Wafa Dahmani), has accepted a position on the ASO AC, and by March 2019 her first 2 years term ends. In order to ensure continuity, the Council is advised to launch a call for volunteers. At meeting 17 January 2019 the Council decided to launch a call for volunteers for both the ccNSO liaison to the GNSO and the ccNSO Liaison to ALAC in accordance with the Guideline: ccNSO Liaisons and Observers. Accordingly the secretariat send the call by Monday 21 January 2019 to the relevant email lists and received 3 application for position GNSO liaison (Maarten Simon (.nl), Luis Diego Espinoza (related to .NA), and Alyssa Moore (.ca)) and 1 application for ALAC liaison (Segun Akano, (.ng)). Council then selected 1 GNSO liaison candidate, following the procedure included in the Guideline, Council selected the GNSO liaison. Decision In accordance with the Guideline: ccNSO Liaisons and Observers (https://ccnso.icann.org/sites/default/files/field-attached/guideline-liaiso…) as adopted by Council, the following persons were selected by Council: < insert name > as Liaison to the GNSO <insert name> as liaison to the ALAC. Both Liaisons will take their seat at the end of the ccNSO Council meeting in Kobe, Japan and invited to attend the ccNSO Council workshop. The chair is requested to inform the ALAC and GNSO of the appointments and the secretariat is requested to add them to the relevant ccNSO email lists. 5) Appointment volunteers SOPC For decision. Draft Resolution Background The SOPC has reviews its current membership and would like to seek new members to ensure continuity. The secretariat launched a call for volunteers and the following persons put their name forward: Dmitry Kohmanyuk (.ua) Biyi Oladipo (.ng) Atsushi Endo (.jp) In addition, and for the record, Nicholas Lisse applied to be observer to the group. To become an observer does not require an action from Council. Decision The ccNSO Council appoints the listed candidates as members of the SOPC for a term of 2 years taking effect immediately. The ccNSO Council requests the Secretariat to inform the candidates and include them on the relevant email list and list them on the SOPC webpage. 6) Update ccTLD World email procedure Introduction In preparation of the December Council meeting, the Secretariat prepared a document, listing the issues as identified in the text of the procedural background documentation for the ccTLD world mailing list, and a high-level analysis of the current list of subscribers. To remedy the issues identified with the ccTLD world mailing list two actions are proposed: update of the procedural documentation update procedure to ensure the list of subscribers is up to date The background material provides more details. For decision: adoption of the amended ccTLD world email list procedural documentation. A redline version is available at: https://docs.google.com/document/d/1tVZ3SyeUDMeWHx2KeNZWhOm97Uem1Ol6PiaGjh-…. Once adopted the secretariat will implement procedure to ensure list of subscribers is up to date. 7) ccNSO related ICANN Bylaw changes 7.1 Repository to be maintained by the ccNSO See Background material 7.2 Change definition of ccNSO membership For discussion & Next steps Background. The membership definition of the ccNSO was changed late in the CWG Stewardship process. Change process. As Article x is not a fundamental Bylaw, it follows the pattern of a regular Bylaw change, open to rejection action by the Decisional participants. Using the post October 2016 change of Article XI (GNSO) as an example (see: GNSO Resolution 20180130-1 Adoption of Revised GNSO Operating Procedures and Proposed Modifications of the ICANN Bylaws consistent with the recommendations of the Bylaws Drafting Team.). Proposed actions. The ccNSO Council consults ccNSO membership on proposed change. Staff is requested to prepare a slide deck. Suggestion is to check whether broader consultation is needed and consult broader community as well (public comment on requested change, requests the Board to change the relevant section in Article X. Note the Board will have to follow its procedure to allow for a standard bylaw change. 7.3 Change ccNSO Council appointed members requirement IFRT(section 18 ICANN Bylaws) For discussion & Next steps Background The IANA naming Function review was launched by the ICANN Board of Directors in September 2018. However, the Review Team has not been formed to date. One of the issue is the requirement that the ccNSO Council appoints a representative from a ccTLD Manager that is not a member of the ccNSO. As indicated before to the ICANN Org and Board, the ccNSO Council anticipates that this problem will only get worse over time, with the increase of members in the ccNSO and in light of the relative small size of the vast majority of the non-ccNSO members and required skill and expertise and time-commitment. As Article 18 is one of the Fundamental Bylaws, and introduced as part of the IAAN Stewardship Transition Process, further discussion with community, ICANN Org and ICANN Board is warranted on next steps. 8) Adoption ccNSO Terms Of Reference ccNSO Internet Governance Liaison Committee For decision Background material. Draft Terms of Reference for Committee Background In November 2018, the ccNSO Council decided to withdraw from the CCWG Interne Governance and not to support the CCEG Charter. However, the ccNSO Council decided that in light of the importance of Internet Governance and interest of ccTLD member is the topic, to create a IG Liaison Committee to further liaise with the members of the CCWG IG / CCEG, ICANN staff and other active participants from the broader ICANN community. If adopted secretariat will send out a call for volunteers. 9) Support Approach joint ccNSO – SSAC Working Party re Risk Mitigation Panel Fast Track Process For discussion and/or decision (Katrina Sataki) Background material: Final draft Guideline Risk Implementation Cover letter 10) CSC Effectiveness Review 10.1 Update of Review (Debbie) 10.2 ccNSO Council statement 11) PDP Retirement Update Informational. Update progress (Stephen Deerhake) 12) ccNSO organizational review Progress to date and next steps (Katrina Sataki) 13) ECA, CSC and RZERC Update 13.1 ECA (Stephen Deerhake) 13.2 CSC (Byron) 13.3 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) Note that the Council will need to select its chair and two(2) vice-chairs 14.2 Council Workshop: topics for discussion Facilitated workshop - Workplan 2019-2020 - Table top exercises: Rejection Action Process & Triage Committee - Expectations of role of a councilor - Assignment Roles and Responsibilities Councillors Please note the included overview of current roles and responsibilities. 14.3 ICANN64 ccNSO Meetings Agenda (Alejandra) - Members day meetings - Meeting with GAC - Meeting the ICANN Board: Suggest topics for meeting with Board? 14.4 WG & other meetings Tech Day (Monday) CSC meeting ( Monday morning) WG meetings (starting Saturday!!) ccNSO Cocktail 15) Council Updates 15.1 Chair Update Background: notes ccNSo Chair and vice-chairs call with CEO & president ICANN 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 Emoji Study Group (Alejandra) 17) Liaison Updates 17.1 GNSO Update (written update) 17.2 ALAC update (written update) 18) Next meetings (2019) 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

1 0

ccNSO Strategic and Operating Standing Committee (SOPC) submits comment on ICANN's Draft FY20 Operating Plan and Budget and the current year update to the Five-Year Operating Plan
by Kimberly Carlson Feb. 7, 2019

Feb. 7, 2019

Dear all, ICANN's Draft FY20 Operating Plan and Budget and the current year update to the Five-Year Operating Plan was published for public comment in December 2018. Link: https://www.icann.org/public-comments/fy20-budget-2018-12-17-en On 5 February, the Strategic and Operational Planning Standing Committee (SOPC) submitted comments on behalf of the ccNSO (see attached and here). For more information on the ccNSO SOPC please visit their webpage here<ccNSO%20Strategic%20and%20Operational%20Planning%20Standing%20Committee>. As always, if you have any additional comments or suggestions please do not hesitate to contact me. 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