February 2019 - Ccnso-council

MPC Update
by Alejandra Reynoso Feb. 14, 2019

Feb. 14, 2019

Dear All Please find in attachment the documents shared today in our call. 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

1 0

February Council call | 14 Feb @12:00 UTC
by Kimberly Carlson Feb. 14, 2019

Feb. 14, 2019

STARTING NOW Dear Councilors, Please find the details below for the February 14, 2019 Council call: Date: 14 February 2019 Time: 12:00 UTC Dial in numbers: http://www.adigo.com/icann/ Conference ID: 5258 Adobe Room: https://participate.icann.org/ccnsocouncil/ There will be two-way audio through Adobe. Please let me know if you will require a dial out. Kind regards, Kim Carlson

1 0

Draft comments on the CSC Effectiveness Review's report
by Katrina Sataki Feb. 14, 2019

Feb. 14, 2019

Dear Colleagues, As you may remember, CSC Effectiveness Review Team chose a light-weight approach and skillfully conducted the review, thus, showing that even in ICANN environment it is indeed possible to do things and get results quickly and efficiently. They have published the draft report: https://www.icann.org/en/system/files/files/csc-effectiveness-initial-16jan1 9-en.pdf To support the team, their findings and approach they used, the Council could submit their comments. The draft of Council's comments (Google docs, as agreed): https://docs.google.com/document/d/1ndCtyayeLIgh94Re7kyCk4oLWqPljJ1o-aPJeZjl ah0/edit Do you support the idea and the text? Is there anything else you would like to add? Please comment by 20 February. Thank you! Kind regards, ]{atrina

5 4

FINAL REMINDER - action required by today, Tuesday, 12 February 2019 (23:59 UTC)
by Joke Braeken Feb. 12, 2019

Feb. 12, 2019

Dear current members of the ccNSO Council, This is a final reminder about the selection process for the ccNSO appointed liaison to the GNSO. Your action is required by today, Tuesday, 12 February 2019 (23:59 UTC) To date, only 8 out of 18 council members have submitted their selection ranking to the ccNSO Secretariat. A reminder about the instructions: 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. 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

REMINDER: Next ccNSO Council call | 14 February @12:00 UTC
by Kimberly Carlson Feb. 12, 2019

Feb. 12, 2019

Dear Councilors: As a reminder, the next Council call will be this Thursday, 14 February at 14:00 UTC Please find the draft agenda attached. Details on how to join: Dial in numbers: http://www.adigo.com/icann/ [adigo.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.adigo.com_icann_&d=…> Conference ID: 5258 Adobe Room: https://participate.icann.org/ccnsocouncil/ Wiki Space: https://community.icann.org/x/IQn_BQ - attendance, recordings and prep material will be posted as they become available. Two-way audio will be available through the Adobe Room - let me know if you require a dial out. If you are unable to attend or will be late, please let Bart and I know as soon as possible. Thank you, Kim _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org<http://www.icann.org> Top of Form Bottom of Form

1 0

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

FW: [So-ac-sg-cleaders] Newcomers Day Invitation ICANN64
by Katrina Sataki Feb. 7, 2019

Feb. 7, 2019

Dear Colleagues, Who would like to meet with newcomers and tell them more about the ccNSO? Please, note, that on Sunday we have many Council-related sessions. Thank you! ]{atrina From: So-ac-sg-cleaders [mailto:so-ac-sg-cleaders-bounces@icann.org] On Behalf Of Deborah Escalera Sent: Tuesday, February 05, 2019 11:13 PM To: so-ac-sg-cleaders(a)icann.org Cc: Heidi Ullrich <Heidi.Ullrich(a)icann.org>; Nigel Hickson <nigel.hickson(a)icann.org> Subject: [So-ac-sg-cleaders] Newcomers Day Invitation ICANN64 Importance: High Dear Community Leaders, The Public Responsibility Support department will be hosting Newcomers Day for ICANN64. We will be featuring two community sessions; one session focusing on the work of the Supporting Organization Councils and Advisory Committees, and the second session highlighting the work of the Stakeholder Groups and Constituencies. We would like to invite your community group to designate a representative by Friday, 22 February to attend the relevant session. Your remarks should be focused toward the Newcomers and will be followed by a brief question and answer session. Together, this should not exceed 10 minutes. We will provide standard slides but you are welcome to send us any slides as well. We will share the deck once it is finalized. We know not every community group will be available to participate in the program because Sunday (10 March) is a busy working day at ICANN64. We will distribute a schedule of suggested meetings/sessions throughout ICANN64 and encourage newcomers to attend them to learn more about the ICANN community. Please confirm your participation with us as soon as possible. Calendar invitations will be sent as appropriate. Below is the timeline of the meeting (see attached schedule). Please let us know if you have any questions. Best regards, Deborah and Siranush 10:00-12:20 Morning Session (broken up by 10 minute slots) 12:20-13:20 Lunch 13:20- 3:00 Afternoon Session (broken up by 10 minute slots)

1 1

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

Feb. 7, 2019

Dear All, When submitting their Expressions of Interest as ccNSO appointed liaison to the GNSO, interested individuals were invited to provide the following: * A resume, curriculum vitae, or biography * A letter of motivation detailing your interest in serving as ccNSO Liaison to the GNSO and what you will bring to this position. * Letter from your employer supporting you with respect to the required time commitments, confirming that you will attend GNSO meetings regularly and inform the ccNSO Council and broader ccTLD community. * If not directly linked to or employed by a ccTLD Manager, demonstrate active backing by a ccTLD manager * Statement of interest that identifies potential conflict of interest in your service as Liaison The active backing by a ccTLD Manager for Luis Diego Espinoza’s candidacy can be found in attachment. 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

Call for Volunteers: the ccNSO seeks 1 mentor and 1 mentee for the ccNSO Community Onboarding Programme (COP)
by Joke Braeken Feb. 6, 2019

Feb. 6, 2019

Dear all, The ccNSO seeks 1 mentor and 1 mentee for the ccNSO Community Onboarding Programme (COP). If you are interested in joining either as mentor or mentee to the ccNSO COP, kindly review the section “how to join” included below. The application window opens Wednesday, 6 February 2019 (noon UTC). The closing date of this call for volunteers is 20 February 2019, 23:59 UTC. Applications received prior to the opening date or after the closing date will not be considered. Objective of the ccNSO COP The ccNSO COP is designed to improve engagement and retention of new participants within the ccNSO by creating a structured, year-round onboarding process and mentorship structure, tailored by and for the ccNSO. ccNSO COP mentor/mentee: role & term of appointment 1. ccNSO COP mentor A mentor is defined as an experienced member of the community best suited to share knowledge of and experience in the ccNSO environment. The role of the mentor: ● Be available to the mentee through previously agreed upon communication channels, at reasonable time frames throughout the experience (pre-, during and post- an ICANN meeting) ● Guide the mentee through all available resources and share relevant information ● Respond in a timely manner to any queries from the mentee ● Facilitate introductions to Community Members, for instance while attending ICANN meetings ● Provide an update the ccNSO Council and/or Secretariat when requested to do so ● Whenever possible, attend ccNSO-relevant sessions at ICANN meetings. The term of appointment of the ccNSO COP mentor shall be one (1) year. A mentor may be re-appointed for two additional terms (in total 3 terms). 2. ccNSO COP mentee A mentee is defined as a relatively new member of the community who has demonstrated both the potential and desire to actively engage and participate in the work of the ccNSO. The role of the mentee: ● Be available to the mentor through previously agreed upon communication channels, at reasonable time frames throughout the experience (pre-, during and post- an ICANN meeting) ● Read the available ccNSO onboarding materials, and where possible provide suggestions for improvements ● Be a good listener and have an open mind to allow guidance through the ccNSO activities ● Work towards the goal of contributing to the work of the ccNSO ● Provide an update the ccNSO Council and/or Secretariat when requested to do so ● Whenever possible, attend ccNSO-relevant sessions at ICANN meetings. The term of appointment of the ccNSO COP mentee shall be one (1) year. A mentee cannot be re-appointed. Who can join? People associated with a ccTLD manager, whether members or non-members of the ccNSO, may apply for the role of ccNSO COP mentor/mentee. Decisions on whether to award the role of ccNSO COP mentor/mentee shall be based on the merits of each application and the criteria included in the Terms of Reference located here<https://ccnso.icann.org/en/about/ccnso-draft-cop-06dec18-en.pdf>. The ccNSO COP mentor and mentee will be selected based on how well the application material they submitted meets the following set of criteria: Requirements for mentees: * Able to work and communicate in written and spoken English * Have a basic knowledge of ICANN and specifically the ccNSO * Be a fairly new community member * Show genuine interest to contribute to the work of the ccNSO * Should be employed or have active backing by a ccTLD manager and should demonstrate the support by the ccTLD manager in respect to the required time commitment to participate actively in the ccNSO COP Requirements for mentors: * Able to work and communicate in written and spoken English * Have a good knowledge of ICANN and specifically the ccNSO * Actively contributes to the work of the ccNSO * Be approachable and accessible, with the goal of advancing the onboarding experience of the mentee * Ability and willingness to share best practices and experiences * Should be employed or have active backing by a ccTLD manager and should demonstrate the support by the ccTLD manager in respect to the required time commitment to participate actively in the ccNSO COP How to join and next steps If you are interested in joining either as mentor or mentee to the ccNSO COP, kindly fill out the application form located here (https://www.surveymonkey.com/r/ccNSOCOP) starting from Wednesday 6 February 2019 (noon UTC). Additional background application materials - such as the active backing by the ccTLD Manager - can be sent via e-mail to joke.braeken(a)icann.org Closing date of this call for volunteers is Wednesday, 20 February 2019, 23:59 UTC. Applications received prior to the opening date or after the closing date will not be considered. Once the application window closed, the ccNSO COP Selection Committee members will evaluate all applications. The outcome of the ccNSO COP Selection Committee deliberations will be published on the ccNSO website, latest by Friday, 15 March 2019. All applicants will receive a personal notification as well. Background and links * About the ccNSO COP The ICANN Community Onboarding Programme results from discussions between the community and the ICANN starting at ICANN49 and concluding at ICANN51. This broader consultation process sought to address volunteer burnout and improve newcomer retention rates. In January 2016, the ICANN COP Pilot was launched to develop an individualized, tailored mentorship process. The programme concluded at the end of ICANN’s FY18. The objective of the ccNSO COP is to continue a COP tailored to the needs and within the limits of the ccNSO environment. * ccNSO funded travel support The ccNSO Travel Support Programme is provided by ICANN to advance the work of the ccNSO as a whole and is therefore aimed at supporting the attendance to ICANN public meetings for community members that are contributing towards its work. ICANN provides support for a limited number of ccNSO slots. Candidates from all regions and sectors, including the ccNSO COP mentor and mentee, may apply for ccNSO travel support. Decisions on whether to award travel support to an application shall be based on the merits of each application and the criteria included in the ccNSO Travel Support Guideline as published on the ccNSO website. Read more here on how to apply for travel funding for ICANN65, Marrakech: https://ccnso.icann.org/en/announcements/announcement-01feb19-en.htm * Links * About the ccNSO COP Selection Committee: https://ccnso.icann.org/en/about/cop-selection * Terms of Reference ccNSO COP: https://ccnso.icann.org/en/about/ccnso-draft-cop-06dec18-en.pdf * Announcement call for volunteers: https://ccnso.icann.org/en/announcements/announcement-05feb19-en.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

ccNSO Activity Summary | January 2019
by Kimberly Carlson Feb. 5, 2019

Feb. 5, 2019

ccNSO Activity Summary January 2019 ICANN64: Meeting page: https://meetings.icann.org/en/kobe64 Registration: https://registration.icann.org/ ccNSO-related sessions: https://community.icann.org/x/wwT_BQ (page will be updated with remote participation details as they become available) TechDay at ICANN64! Please contact the Tech WG<mailto:ccNSO-techday@icann.org> if you have questions or interested in presenting at TechDay Working/Study Group Meeting Output: Recordings of various Working Group Meetings can be found here: http://ccnso.icann.org/calendar 31 January - ccPDP on Retirement Working Group Telephone Conference - Wiki<https://community.icann.org/x/OIANBg> 30 January - ccNSO Study Group on Use of Emoji as SLD Telephone Conference - Wiki<https://community.icann.org/x/L4ANBg> 23 January - TLD OPS Standing Committee and Playbook Drafting Team Telephone Conference 21 January - Meetings Programme Committee - Wiki<https://community.icann.org/x/mgSfB> 17 January - ccPDP on Retirement Working Group Telephone Conference - Wiki<https://community.icann.org/x/WQn_BQ> 16 January - ccNSO Study Group on Use of Emoji as SLD Telephone Conference - Wiki<https://community.icann.org/x/KoANBg> 14 January - Guidelines Review Committee Telephone Conference - Wiki<https://community.icann.org/x/GQb_BQ> ccNSO Council: ccNSO Council call 17 January - wiki<https://community.icann.org/x/QolHBQ> ccNSO Council preparation material and output can be found here: http://ccnso.icann.org/about/council/minutes.htm ccNSO Council Decisions and Resolutions: http://ccnso.icann.org/about/council/decisions-resolutions.htm ccNSO Council Wiki space <https://community.icann.org/x/BiyAAw> Links and Announcements regarding the IANA Stewardship Transfer and ICANN's Accountability Process: IANA Stewardship Transition Implementation Page<https://www.icann.org/stewardship-implementation> CSC Reports and Findings<https://www.icann.org/en/csc/reports> Initial Report on CSC Effectiveness<https://www.icann.org/news/announcement-2019-01-16-en> - 16 January 2019 Other Announcements: Public Comment Opportunities<https://www.icann.org/public-comments> 2021 ICANN Public Meeting - Annual General Meeting Location Announced<https://www.icann.org/news/announcement-2-2019-01-31-en> - 31 January 2019 ICANN Board Reaffirms Temporary Specification for gTLD Registration Data<https://www.icann.org/news/announcement-2019-01-29-en> - 29 January 2019 ICANN Board Creates Working Group on Anti-Harassment<https://www.icann.org/news/announcement-2019-01-28-en> - 28 January 2019 EPDP Team Makes Substantial Progress Toward Final Report<https://www.icann.org/news/blog/epdp-team-makes-substantial-progress-toward…> - 24 January 2019 ICANN Publishes Documents Regarding the Implementation of the Procedure for Release of Two-Character Labels<https://www.icann.org/news/announcement-2-2019-01-22-en> - 22 January 2019 Opportunities to Participate: ICANN Reviews<https://www.icann.org/news/announcement-2019-01-22-en> - 22 January 2019 Apply Now for ICANN and PTI Leadership Positions<https://www.icann.org/news/announcement-2019-01-17-en> - 17 January 2019 2019 Nominating Committee Priorities and Agenda<https://www.icann.org/news/blog/2019-nominating-committee-priorities-and-ag…> - 9 January 2019 Amendment to the IANA Naming Functions Contract, Annex A<https://www.icann.org/news/announcement-2-2019-01-07-en> - 7 January 2019 SSAC2 Review: Final Report Available<https://www.icann.org/news/announcement-2019-01-07-en> - 7 January 2019 _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org<http://www.icann.org> Top of Form Bottom of Form

1 0

action required: selection process ccNSO appointed liaison to the GNSO
by Joke Braeken Feb. 5, 2019

Feb. 5, 2019

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 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/… * 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<https://ccnso.icann.org/sites/default/files/field-attached/election-report-…>. * Announcement call for volunteers: https://ccnso.icann.org/en/announcements/announcement-21jan19-en.htm 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

action required: review application material ccNSO appointed Liaison to the ALAC
by Joke Braeken Feb. 5, 2019

Feb. 5, 2019

Dear All, The call for volunteers for the position of ccNSO appointed Liaison to the ALAC closed yesterday, Monday 4 February 2019 at 23:59 UTC. One candidate stepped forward: Akano Olusegun Sunday (.ng). Included you will be able to find the information as submitted by Segun, who is eligible to participate in the appointment process, as per the applicable guideline. The roles and responsibilities of the ccNSO Liaison to the ALAC are: As specified in the ccNSO Guideline Liaison and Observers (https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/…) the ccNSO appointed liaison to the ALAC shall report to the ccNSO Council not less than monthly on the activities of the respective organization. The ccNSO appointed Liaison to the ALAC shall represent ccNSO values in these efforts, shall pursue specific direction from the ccNSO Council as and when given, and shall seek ccNSO Council advice as and when needed. Furthermore, the ccNSO Liaison to the ALAC is committed to: * Participate diligently and actively in the meetings and activities of the ALAC on an ongoing and long-term basis * Communicate and advocate the positions of the ccNSO to the ALAC; * Report to the ccNSO on current and upcoming activities of the ALAC that may be of relevance to the ccNSO and broader ccTLD community. * If feasible and considered relevant ask to the ccNSO for advance guidance, if any, on matters that are going to be discussed by the ALAC. * Participate in ALAC-ccNSO Council meetings agenda committee to prepare the f-2-f meetings, if any. The ccNSO liaison to the ALAC shall not be a member of or entitled to vote on the ccNSO council or the Councils of other organizations, but otherwise shall be entitled to participate in the respective Council meetings. Quote from the ccNSO Guideline Liaisons and Observers, 5.1.2 Selection of Liaisons: […] In the event only one person has volunteered, this person shall be appointed by the ccNSO Council at the first meeting following the call for volunteers. In the event two or more persons have volunteered for the same position, the ccNSO Council will conduct an email vote for the appointment. The Secretariat will then act as Selection manager. The volunteer who receives the majority of the votes lodged shall be considered to be appointed by the ccNSO Council as of the date the results are published by the election manager. The Chair of the ccNSO will inform the ICANN Secretary and the respective Supporting Organization or Advisory Committee of the appointment. […] Next steps The adoption of the Election Report is 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 The ccNSO is looking for a member of the ccTLD community to be appointed as ccNSO liaison to the ALAC. Read the announcement here: https://ccnso.icann.org/en/announcements/announcement-2-21jan19-en.htm The call for volunteers included the requirements for candidates, details on how to apply, and how the selection will occur, are specified in the ccNSO Guideline Liaison and Observers (https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/… <https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…> ) 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

Apply for ccNSO travel funding for ICANN65, Marrakech. Starting tomorrow, Tue 5 Febr.
by Joke Braeken Feb. 4, 2019

Feb. 4, 2019

Dear all, Between tomorrow, Tuesday, 5 February 2019 (noon UTC) and Friday, 15 February 2019 (noon UTC) it is possible to apply for ccNSO travel funding to attend the ICANN65 public meeting, taking place at the end of June 2019 in Marrakech, Morocco. No early/late submissions will be accepted. What are the requirements for applicants? The applicant actively participates in the work of the ccNSO and makes a special contribution to its projects and meetings. 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. Important: Applications which do not clearly state an active contribution, are not eligible and will not be taken into consideration. What is included? The funding covers an economy class ticket to the travel destination, the hotel costs for the time of the meeting and a per diem (either full funding, or partial funding). ccNSO Travel Fund Guideline: https://ccnso.icann.org/en/about/guidelines.htm <https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_abo…> How to apply? Full details on how to submit your application can be found here: http://ccnso.icann.org/about/travel-funding<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org_about_t…>. 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 on 26 February 2019. All applicants will receive a personal notification as well. 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

triage recommendations 01-2019 until 09-2019
by Joke Braeken Feb. 1, 2019

Feb. 1, 2019

Dear Councillors, We have received several requests for input, that were addressed via triage recommendations. Below I have included an overview of all recommendations as formulated by the Triage Committee. The summary and background of the recommendations, the proposed action for each of them and the relevant deadlines, are included in the tables further down in this e-mail. If you do not agree with the recommendations, kindly let me know by 5 February 2019, 23:59 UTC. Thank you! Overview triage recommendation number + topic: 01-2019: Nomination Period Opens for ICANN Multistakeholder Ethos Award | Award Targeted for ICANN65 | Nominations Close 22 March 2019 02-2019: ICANN Draft FY20 Operating Plan and Budget and Five-Year Operating Plan Update 03-2019: Updated Operating Standards for Specific Reviews 04-2019: Proposed changes to the Registrar Stakeholder Group (RrSG) Charter 05-2019: Deadline extended: ccNSO Review Survey available for community input 06-2019: ICANN Strategic Plan for fiscal years 2021 - 2025 07-2019: First Consultation on a 2-Year Planning Process 08-2019: Amendment to the IANA naming function contract, Annex A 09-2019: Apply now for ICANN and PTI Leadership positions Apologies for deviating from the proposed template: all recommendations were incorporated in 1 single email, instead of sending 9 separate ones. Kindly let me know if there are any concerns regarding this approach. Number: 01-2019 Topic: Nomination Period Opens For ICANN Multistakeholder Ethos Award | Award Targeted for ICANN65 | Nominations Close 22 March 2019 Request from: ICANN Summary: ICANN announced the opening of the nomination period for ICANN's Multistakeholder Ethos Award. Launched in 2014 at ICANN50 in London, the Multistakeholder Ethos Award recognizes ICANN participants who have deeply invested in consensus-based solutions, acknowledging the importance of ICANN's multistakeholder model of Internet governance, and contributed in a substantive way to the higher interests of ICANN's organization and its community. Close date: 22 March 2019 Read more: https://www.icann.org/news/announcement-2018-12-17-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: Share with the following mailing lists: ccnso-members, broader ccTLD community, ccnso-council. Share via the ccNSO twitter account. (completed) Impact on ccNSO/ccTLDs: LOW Number: 02-2019 Topic: ICANN Draft FY20 Operating Plan and Budget and Five-Year Operating Plan Update Request from: ICANN org Summary: Focusing on ICANN's commitment to the multistakeholder model, ICANN's Draft FY20 Operating Plan and Budget and the current year update to the Five-Year Operating Plan are provided for community discussion and public comment. ICANN seeks structured feedback on the plans described in these documents. The documents incorporate improvements on previous years based on regular interaction with the ICANN community and reflect FY20's planned accomplishments towards the Five-Year Strategic Plan, which was adopted by the ICANN Board in October 2014. Close date: 08 February 2019 Read more: https://www.icann.org/news/announcement-2-2018-12-17-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: The SOPC is aware of this public comment proceeding and will submit its input by 6 February 2019. Impact on ccNSO/ccTLDs: HIGH Number: 03-2019 Topic: Updated Operating Standards for Specific Reviews Request from: Multistakeholder Strategy and Strategic Initiatives (MSSI) Summary: This public comment proceeding seeks to solicit input on the updated Draft Operating Standards for Specific Reviews [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> (Operating Standards). The Operating Standards aim to ensure that ICANN's Specific Reviews are conducted in a transparent, consistent, efficient, and predictable manner, while supporting the community's work to derive the expected benefit and value from review processes. Areas of guidance in the Operating Standards, as mandated by the ICANN Bylaws, include review team selection process, conflict of interest practices, confidential disclosure to review teams, review team decision-making practices, and guidelines on how review teams are to work with and consider independent expert advice. Specific Review teams currently conducting reviews are encouraged to use these Draft Operating Standards as a reference for their work. The current draft is an update to the Draft Operating Standards [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> that were published for public comment in October 2017. Close date: 11 February 2019 Read more: https://www.icann.org/news/announcement-3-2018-12-17-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: Forward the announcement to the GRC mailing list, with the request to respond. (completed) Impact on ccNSO/ccTLDs: HIGH Number: 04-2019 Topic: Proposed changes to the Registrar Stakeholder Group (RrSG) Charter Request from: ICANN Board of Directors, GNSO, RrSG Summary: The purpose of this public comment proceeding is to obtain community input on proposed changes to the charter of the GNSORegistrar Stakeholder Group (RrSG). The changes have been approved by the membership of the RrSG and are awaiting ICANN Board review and approval. Due to the extent of the revisions and consistent with the ICANN Board Process for Amending GNSO Stakeholder Group and Constituency Charters [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…>, the ICANN Board Organizational Effectiveness Committee has authorized this public comment proceeding. Close date: 5 February 2019 Read more: https://www.icann.org/public-comments/rrsg-charter-2018-12-18-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> Recommended action: none Impact on ccNSO/ccTLDs: NO IMPACT Number: 05-2019 Topic: Deadline extended: ccNSO Review Survey available for community input Request from: Independent examiner, MSSI Summary: The deadline to take the Country Code Names Supporting Organization (ccNSO) Review survey has been extended until Friday 11 January 2019 at 23:59 UTC. Close date: 11 January 2019 (23:59 UTC) Read more: https://www.icann.org/news/announcement-2018-12-19-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: Share with the following mailing lists: ccnso-members, broader ccTLD community, ccnso-council. Share via the ccNSO twitter account. (completed) Impact on ccNSO/ccTLDs: MEDIUM Number: 06-2019 Topic: ICANN Strategic Plan for fiscal years 2021 - 2025 Request from: ICANN org, MSSI Summary: The purpose of this public comment is to seek community input on ICANN’s draft five-year strategic plan for fiscal years 2021 through 2025 Close date: 11 February 2019 Read more: https://www.icann.org/news/announcement-2018-12-20-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: The SOPC is aware of this public comment proceeding and will submit its input by 11 February 2019. Impact on ccNSO/ccTLDs: HIGH Number: 07-2019 Topic: First Consultation on a 2-Year Planning Process Request from: ICANN org Summary: Purpose: Obtain community input on needs and improvements to the planning process. Current Status: First consultation to evaluate the potential benefit of implementing a 2-year planning process. Next Steps: After receiving public comments, ICANN org will use the input to develop a proposed planning process that may include a 2-year duration. Close date: 20 February 2019 Read more: https://www.icann.org/public-comments/two-year-planning-2018-12-21-en[icann…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> Recommended action: The SOPC has been made aware of the request for community input. The SOPC chair will present a draft version of the input to the SOPC by 7 February 2019. Impact on ccNSO/ccTLDs: HIGH Number: 08-2019 Topic: Amendment to the IANA naming function contract, Annex A Request from: Global Domains Division Summary: The purpose of this public comment proceeding is to obtain community input on a proposed Amendment to the IANA Naming Functions Contract between ICANN and Public Technical Identifiers (PTI) [pti.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__pti.icann.org_&d=DwMFa…>. If approved, the Amendment would allow the Customer Standing Committee (CSC) and PTI/ICANN to change the IANA Naming Function's Service Level Agreements (SLAs) without the need to do a contract amendment every time an SLA change is needed. Instead, the SLA change would follow an SLA Change Process that provides a process to achieve amendments to the SLAs in a timely fashion while requiring consultations with the IANA Function naming customers and broader ICANN community as appropriate. Close date: 18 February 2019 Read more: https://www.icann.org/news/announcement-2-2019-01-07-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: Share with the following mailing lists: ccnso-members, broader ccTLD community, ccnso-council. Share via the ccNSO twitter account. (completed) Impact on ccNSO/ccTLDs: low Number: 09-2019 Topic: Apply now for ICANN and PTI Leadership positions Request from: ICANN NomCom Summary: The ICANN Nominating Committee (NomCom) invites interested individuals to submit an expression of interest in key leadership positions within ICANN and Public Technical Identifiers (PTI). Selected individuals will have a unique opportunity to work with accomplished colleagues from around the globe to help shape the Internet's technical coordination and policy development. Close date: 18 March 2019 (23:59 UTC) Read more: https://www.icann.org/news/announcement-2019-01-17-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: Share with the following mailing lists: ccnso-members, broader ccTLD community, ccnso-council. Share via the ccNSO twitter account. (completed) Impact on ccNSO/ccTLDs: medium 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

FW: [CORRECTION] Notice of Board Approval of FY20 IANA Budget
by Katrina Sataki Feb. 1, 2019

Feb. 1, 2019

Dear Colleagues, This triggers a 21 days long Rejection Action Petition Period. Next step – I will inform the community accordingly. Kind regards, ]{atrina From: Peg Rettino [mailto:peg.rettino@icann.org] Sent: Friday, February 01, 2019 1:26 AM To: ecadmin(a)icann.org; chair(a)nro.net; maureen.hilyard(a)gmail.com; katrina(a)nic.lv; Drazek, Keith <kdrazek(a)verisign.com>; Manal Ismail <manal(a)tra.gov.eg> Cc: Cherine Chalaby <cherine.chalaby(a)board.icann.org>; Goran Marby <goran.marby(a)icann.org> Subject: [CORRECTION] Notice of Board Approval of FY20 IANA Budget Greetings, Attached please find the *corrected* notice. My apologies for any inconvenience. Best, Peg -- Peg Rettino Project Specialist & Executive Assistant to John Jeffrey General Counsel and Secretary ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 peg.rettino(a)icann.org <mailto:peg.rettino@icann.org> Skype: peg.rettino Direct: 310-301-3868 From: Peg Rettino <peg.rettino(a)icann.org <mailto:peg.rettino@icann.org> > Date: Thursday, January 31, 2019 at 1:21 PM To: "ecadmin(a)icann.org <mailto:ecadmin@icann.org> " <ecadmin(a)icann.org <mailto:ecadmin@icann.org> >, "chair(a)nro.net <mailto:chair@nro.net> " <chair(a)nro.net <mailto:chair@nro.net> >, "maureen.hilyard(a)gmail.com <mailto:maureen.hilyard@gmail.com> " <maureen.hilyard(a)gmail.com <mailto:maureen.hilyard@gmail.com> >, "katrina(a)nic.lv <mailto:katrina@nic.lv> " <katrina(a)nic.lv <mailto:katrina@nic.lv> >, "Drazek, Keith" <kdrazek(a)verisign.com <mailto:kdrazek@verisign.com> >, Manal Ismail <manal(a)tra.gov.eg <mailto:manal@tra.gov.eg> > Cc: Cherine Chalaby <cherine.chalaby(a)board.icann.org <mailto:cherine.chalaby@board.icann.org> >, Goran Marby <goran.marby(a)icann.org <mailto:goran.marby@icann.org> > Subject: Notice of Board Approval of FY20 IANA Budget Greetings, Please see the attached notice sent on behalf of John Jeffrey. Best, Peg -- Peg Rettino Project Specialist & Executive Assistant to John Jeffrey General Counsel and Secretary ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 <mailto:peg.rettino@icann.org> peg.rettino(a)icann.org Skype: peg.rettino Direct: 310-301-3868

1 0