November 2019 - Ccnso-council

Formal Approval to the ECA
by Katrina Sataki Nov. 22, 2019

Nov. 22, 2019

Dear Councillors, By 27 November, we should formally approve Board's decision (as per our request) to amend Fundamental Bylaws with respect to the composition of the IANA Function Review team. Any edits/comments to the attached draft? Please let me know by Friday, 22 November. Kind regards, ]{atrina

10 10

FW: Appointments to the Root Server System Governance Working Group
by Katrina Sataki Nov. 22, 2019

Nov. 22, 2019

Dear Colleagues, As you can see from the email below, ICANN Board has passed a resolution to initiate the Root Server System Governance Working Group (CWG). We are requested to appoint 2 representatives. To ensure that we select two subject matter experts, I suggest that we develop a set of requirements and issue a call for volunteers. To make sure that we meet the deadline of 10 January, we should issue the call no later than 9 December. So, here’s a draft plan: - Develop requirements (including time commitment) – first draft: 27 November (Secretariat) - Develop requirements (including time commitment) – finalised: 6 December (All) - Call for volunteers: 9 December 00:01 UTC – 22 December 23:59 UTC (Secretariat) - List of volunteers to Council: 26 December (Secretariat) - Top candidates from the Council: 7 January (Councillors) - Inform GWC: 8 January (Chair) I tried to take into account Season’s holidays as much as possible. How does the plan look to you? Any comments/suggestions? Kind regards, ]{atrina From: Carlos Reyes [mailto:carlos.reyes@icann.org] Sent: Friday, November 15, 2019 2:38 PM To: Katrina Sataki <katrina(a)nic.lv> Cc: David Olive <david.olive(a)icann.org>; ccnsosecretariat(a)icann.org Subject: Appointments to the Root Server System Governance Working Group Importance: High Dear Katrina, As you may know, the ICANN Board recently passed a resolution to initiate <https://www.icann.org/resources/board-material/resolutions-2019-11-07-en#2.d> the Root Server System Governance Working Group (GWG). The GWG is the core of the community-driven process to develop a final cooperation and governance model for the Root Server System (RSS). The GWG shall present its deliverable to the Root Server System Advisory Committee (RSSAC), ICANN Board, Internet Architecture Board/Internet Engineering Task Force (IAB/IETF), and Root Server Operators (RSOs). The GWG shall comprise ten (10) invited representatives due to subject matter expertise: * Two (2) from the Country Code Names Supporting Organization (ccNSO) * Two (2) from the IAB/IETF * Two (2) from the Registries Stakeholder Group (RySG) * Three (3) from the RSOs * One (1) from the Security and Stability Advisory Committee (SSAC) The GWG shall also comprise three (3) liaisons, one each from the ICANN Board, Internet Assigned Numbers Authority (IANA), and Root Zone Maintainer (RZM). GWG representatives and liaisons will provide input that informs GWG discussions and decisions. The GWG work plan estimates a two-year effort. However, most of the work for the GWG will take place in the first year. The GWG will determine its work cadence: Regular teleconferences (e.g., every other week) will drive the process with potential work sessions at ICANN Public Meetings as necessary. In carrying out its work, the GWG shall embrace the principles outlined in “RSSAC037: A Proposed Governance Model for the DNS Root Server System” (RSSAC037) and refer to RSSAC037 and the Concept Paper as source documents, as well as the feedback from Public Comment. The GWG charter, operating procedures, and work plan as well as relevant resources are published on its workspace <https://community.icann.org/pages/viewpage.action?pageId=120820189> . By Friday, 10 January 2020, please provide the name and email address of the two ccNSO representatives to carlos.reyes(a)icann.org <mailto:carlos.reyes@icann.org> for onboarding. Every member of the GWG will provide a statement of interest and disclose potential conflicts of interest. GWG members are not compensated. The goal is to provide the final composition of the GWG to the ICANN Board at its 24-26 January 2020 workshop and convene the GWG for its first teleconference the week of 27 January 2020. I will be leading the support function for the GWG and look forward to working with the ccNSO representatives. Please do not hesitate to contact me with any questions or concerns. Best Regards, Carlos Reyes Carlos Reyes Strategic Policy Planning Director Internet Corporation for Assigned Names and Numbers (ICANN) +1 202 802 8019 www.icann.org <http://www.icann.org>

10 10

SLA change approval
by Katrina Sataki Nov. 22, 2019

Nov. 22, 2019

Dear Colleagues, We should inform the CSC that we have approved SLA change. Any edits/comments to the attached draft? Please let me know by Friday, 22 November. Kind regards, ]{atrina

9 8

proposed draft resolution: Termination ccNSO membership tzNIC
by Joke Braeken Nov. 21, 2019

Nov. 21, 2019

Dear Councillors, Please find below a draft resolution, presented to you for an online decision. Kindly provide me with your input by the end of Monday, 25 November 2019, 23:59 UTC, in case you do not agree with the proposed resolution. Termination ccNSO membership For decision End of ccNSO membership of Tanzania Network Information Center (tzNIC), the previous .tz ccTLD manager. Background Following a recent transfer of the .tz ccTLD to a new TLD manager, there is a discrepancy between the data of the ccTLD manager in the IANA delegation record and the ccTLD manager data as included in the ccNSO member database. Draft Resolution The ccNSO Council concludes that the ccNSO membership of Tanzania Network Information Center (tzNIC) has ended after completion of the transfer process of .tz to Tanzania Communications Regulatory Authority (TCRA). The secretariat is requested to take all necessary steps to inform tzNIC on behalf of Council about this decision, and to remove references to tzNIC as .tz ccTLD manager from the ccNSO website and membership records, including removing all tzNIC email addresses from the ccNSO mailing lists. This resolution becomes effective seven (7) days after publication on the ccNSO Website. 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

6 5

Post-ICANN66 Policy Report out now
by Joke Braeken Nov. 21, 2019

Nov. 21, 2019

Dear all, The Post-ICANN66 Policy Report is now available. Download the report here: https://go.icann.org/post66. This report captures updates from the Supporting Organizations and Advisory Committees. 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

heads up: the ccNSO will soon launch a call for volunteers for the Root Server System Governance Working Group
by Joke Braeken Nov. 20, 2019

Nov. 20, 2019

Hello everyone, This is a heads-up, about an upcoming call for volunteers. The ICANN Board recently passed a resolution to initiate the Root Server System (RSS) Governance Working Group (GWG): consequently, the ccNSO needs to appoint two (2) volunteers to the Root Server System CWG. A call for volunteers will be published in approximately a week from now, and it will include among others further background details on the RSS GWG, information on how to join, the candidate qualification requirements and the selection process. About the RSS GWG The GWG is the core of the community-driven process to develop a final cooperation and governance model for the Root Server System (RSS). In carrying out its work, the GWG shall embrace the principles outlined in “RSSAC037: A Proposed Governance Model for the DNS Root Server System” (RSSAC037) and refer to RSSAC037 and the Concept Paper as source documents, as well as the feedback from Public Comment. Consult the GWG charter, its operating procedures and work plan as well as relevant resources on its workspace<https://community.icann.org/pages/viewpage.action?pageId=120820189>, or read the ICANN Board resolution to initiate the RSS GWG here<https://www.icann.org/resources/board-material/resolutions-2019-11-07-en#2.d>. 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

RZERC flash report for the ccNSO Council
by Joke Braeken Nov. 20, 2019

Nov. 20, 2019

Dear all, I am not sure whether Peter's original email was delivered to the council mailing list: hence this forward. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org On 08/11/2019, 01:01, "Ccnsosecretariat on behalf of Peter Koch" <ccnsosecretariat-bounces(a)icann.org on behalf of pk(a)DENIC.DE> wrote: Dear ccNSO Council, please find attached a flash report on RZERC and an addendum. Best regards, Peter ----------------------------------------------------------------------------- 2019-11-07, Peter Koch, DENIC (DE) ccNSO appointee to the Root Zone Evolution Review Committee (RZERC) <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_rzerc&d=… > ----------------------------------------------------------------------------- The work of RZERC is made transparent by means of the website above and the publicly accessible mailing list archive at <http://mm.icann.org/pipermail/rzerc/>. ----------------------------------------------------------------------------- The committee held its face to face meeting on 6 Nov 2019, 17:00-18:00 EST during the ICANN meeting in Montreal. RZERC has been dormant since its public meeting at ICANN63 in Barcelona. The recent meeting was conducted to comply with the operational procedures which demand at least one meeting per year. No issues of substance were brought to the attention of the committee. However, two matters of housekeeping will need attention: 1) The term lengths and limits of the committee members are governed by the appointing organisations. This leads to appointments from one to three years and even essentialy unlimited. In addition, appointment periods are not synchronized, so that they could start at any point in time across the year, leading to somne uncertainty regarding the appointment staus of individual committee members. 2) The situation described above complicates the appointment of a chair, whose term length is currently two years. Part of this could be mitigated by reducing the chair's term to the length of the shortest appointment period (if that is considered an issue), but it would still limit the effective eligibility of committee members if they would face term timeout inmidst their chair tenure. The RZERC charter is up for review in 2021 the latest, so part of the situation could be addressed during that review. The committee is going to keep track of potential clarifications as the review deadline approaches. During the meeting, committee members identified some issues of substance that merit initial evaluation and discussion. These will be addressed in virtual meetings in December and/or January. ----------------------------------------------------------------------------- Suggested Action: review ccNSO appointment procedure document for opportunities for clarification as outlined above ----------------------------------------------------------------------------- OFF RECORD remarks and suggestions: The first issue appears to be a communications issue that can be improved by communicating the exact date of the appointment, which together with the appointment period, would indicate the renewal date. Appointing organisations should keep track of these dates and initiate a confirmation or appointment action according to their resepctive procedures. To that extent, the ccNSO document for RZERC appointment might benefit from an amendment since it expects a call from ICANN. The current working assumption is that my current 3 year term starts with the date of the ccNSO Council resolution. Regarding the synchronization it appears to me that the change might look minor but would need more discussion between the sending entities and thus might be deferred until after charter review has been conducted. The more important issue is to get clarity and agreement regarding the actual role of the committee - and potential issues that members have now suggested to discuss. ----------------------------------------------------------------------------- _______________________________________________ Ccnsosecretariat mailing list Ccnsosecretariat(a)icann.org https://mm.icann.org/mailman/listinfo/ccnsosecretariat _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_… ) and the website Terms of Service (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_… ). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

FW: Approval of new IANA Naming Function SLA: Publication of LGRs
by Katrina Sataki Nov. 20, 2019

Nov. 20, 2019

FYI From: Julie Bisland [mailto:julie.bisland@icann.org] Sent: Tuesday, November 19, 2019 8:24 PM To: Lars-Johan Liman <liman(a)netnod.se> Cc: Kim Davies <kim.davies(a)iana.org>; katrina(a)nic.lv; gnso-chairs(a)icann.org; gnso-secs(a)icann.org Subject: Approval of new IANA Naming Function SLA: Publication of LGRs Sent on behalf of Keith Drazek, Chair, GNSO Council Dear Lars-Johan, On 18 October 2019, the Chairs of the ccNSO and GNSO were <https://gnso.icann.org/sites/default/files/file/field-file-attach/liman-to-…> informed that the Customer Standing Committee (CSC) and Public Technical Identifiers (PTI) agreed to establish a set of new Service Level Agreements (SLAs) for the publication of the Internationalized Domain Name (IDN) tables and Label Generation Rulesets (LGRs) in the IDN Practices Repository. As described in the <https://www.icann.org/en/system/files/files/iana-naming-function-sla-amendm…> process developed and agreed to by the CSC and PTI to amend SLAs, the CSC should seek approval from the ccNSO and GNSO Councils for new SLAs. The GNSO Council has duly reviewed the proposed SLA change request and discussed it as well with the ccNSO Council during the respective joint session at ICANN66. The purpose of this letter is to inform you that on 6 November 2019, the GNSO Council passed a resolution ( <https://gnso.icann.org/en/council/resolutions#201911> See GNSO resolution) to approve the SLA change request. Best regards, Keith Drazek, Chair, GNSO Council -- Julie Bisland GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: <mailto:julie.bisland@icann.org> julie.bisland(a)icann.org Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global calendar <https://features.icann.org/calendar>

1 0

Bilateral meetings with GNSO
by Katrina Sataki Nov. 19, 2019

Nov. 19, 2019

Dear All, In Montreal, I had a brief conversation with Pam, Vice Chair of the GNSO Council. She explored the possibility to move our bilateral meetings from the lunch time on Monday to Sunday as they meet with other constituencies on Sundays. Sundays are usually pretty busy for us - we start with Council workshop (as decided, we are going to have Council workshops at least at meetings A and C, if possible at meetings B too), then we have Council prep meeting (any bilateral meetings should take place after the Council prep meeting to give us an opportunity to discuss issues before meeting with others), then working group meetings start (many Councillors are on different working groups). At the end of Sundays, we usually schedule our meeting with ALAC. If this meeting takes place in parallel with WG meetings, the Councillors who are on WGs, cannot attend meetings with ALAC. To be honest, looking at the current schedule, I do not see how we could meet with the GNSO Council on Sunday without changing our current meeting structure, e.g. by moving WG meetings to Saturday (when we already have WG meetings.). I understand Sundays would work better for the GNSO but, at the moment, I cannot suggest any reasonable way to accommodate this request. Would you have any suggestions? Kind regards, ]{atrina P.S. That's all for today from me :)

5 4

Country Code Top-Level Domains Can Now Participate in ICANN’s Domain Abuse Activity Reporting (DAAR) System
by Joke Braeken Nov. 19, 2019

Nov. 19, 2019

Dear All, Today, the Internet Corporation for Assigned Names and Numbers (ICANN) announced that country code top-level domain (ccTLD) operators will now be able to actively participate in the Domain Abuse Activity Reporting (DAAR) system. ICANN's DAAR system is used to study and report on domain name registration and security threat behavior across top-level domain (TLD) registries. The data is obtained from a curated list of Domain Name System (DNS) reputation providers. Now, ccTLD operators can pull their own aggregated DAAR data via the Monitoring System Application Programing Interface (MoSAPI). The MoSAPI interface allows registry operators to retrieve information collected by the ICANN Service Level Agreement Monitoring (SLAM) system. While ccTLD operators will not be subject to the SLAs the SLAM system monitors, using MoSAPI will allow a consistent interface for all registries participating in DAAR. The aggregated data counts security threats broken down by threat type (e.g., phishing, botnet command and control, malware distribution, and spam) per TLD. These data sets will be similar to those of the generic top-level domains (gTLDs) that are currently provided via MoSAPI. Having access to such data will enable ccTLD operators to monitor the DAAR security threat levels per threat type per month in the same way as gTLD operators. The ICANN organization invites all ccTLD operators to participate in the DAAR project to promote a greater understanding of DNS abuse across the global DNS. To participate, ccTLD operators should send a request to globalsupport(a)icann.org <mailto:globalsupport@icann.org%20> to begin the process. More Information For additional discussions regarding DAAR project data sharing and any other measurement of DNS security threats and abuse related topics please join the DNS-Abuse-Measurements<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_T…> mailing list. DAAR webpage: https://www.icann.org/octo-ssr/daar<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_k…>. Read this new alert here: https://www.icann.org/news/announcement-2019-11-19-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