Dear Brett, Thank you for your reply. I think getting input form the TCRs is a great idea as well. I can point to the following as ways to engage: 1. The list of TCRs is posted on the IANA website, please see https://www.iana.org/dnssec/tcrs. The CSC may want to use this list to reach out to TCRs in the community for their input. 2. Please note that the CSC has a TCR member as well, Dmitry Burkov. I am sure he has valuable input for this committee having been a TCR for a number of years. 3. There are other frequent ICANN meeting attendees that serve as TCRs and the CSC may want to reach out to them if they wish. Fred Neves in particular comes to mind as he is co-chair of the IFR as well and may want to engage with CSC on that too. We have already sent a heads up to Fred that the CSC is interested in the DNSSEC monitoring and may want to engage. I hope you find the above information helpful. Best regards, Naela From: Brett Carr <brett.carr@nominet.uk> Date: Tuesday, February 11, 2020 at 3:23 AM To: Naela Sarras <naela.sarras@iana.org>, "icann-csc@icann.org" <ICANN-CSC@icann.org> Subject: [Ext] Re: [ICANN-CSC] CSC Meeting 36: Recording, Notes, & Chat Naela, Thanks for this, I think it would be very interesting and useful if there Is a presentation on this in Cancun. I wonder if also it may be worth trying to engage with a TCR who has been active recently to give their view on the current processes and whether there are any issues or potential areas for improvement. Brett -- Brett Carr Manager DNS and Network Engineering Nominet UK From: ICANN-CSC <icann-csc-bounces@icann.org> on behalf of Naela Sarras <naela.sarras@iana.org> Date: Monday, 10 February 2020 at 16:30 To: "icann-csc@icann.org" <ICANN-CSC@icann.org> Subject: Re: [ICANN-CSC] CSC Meeting 36: Recording, Notes, & Chat Dear CSC, Per the action item assigned to PTI from the December 2019 CSC meeting, we are providing more information on the DNSSEC portion of the work performed under the IANA Naming Function Contract. The DNSSEC-related operations performed by the IANA function predominantly relates to maintaining the key signing key (KSK) for the authoritative root zone are part of the IANA Naming Function agreement (section 4 of the agreement). The performance and monitoring of this includes the following mechanisms: 1. Trusted Community Representatives (TCRs), volunteers from the Internet community with security expertise who participate in the root key generation and signing ceremonies. As described at https://iana.org/tcr<http://iana.org/tcr> and elsewhere, “TCRs are ambassadors on behalf of the broader technical and operational communities. To support trust in the system, TCRs report back to the community that the KSK is being managed in an appropriate and trustworthy way.” Participants are highly active in the key ceremonies and also provide constant improvement feedback to allow the process to evolve. 2. Third-party Audit Certification of the Root Zone Key Signing Key (KSK) system according to relevant trust service principles and criteria in line with industry standards. 3. Comprehensive and high level of transparency of KSK ceremonies, including a full recording of each ceremony, fully open sourced software, and data inputs and outputs. 4. Engaging with the broader community, using mechanisms such as the ICANN public meetings and public comment forum, and the use of specialized community design teams, in relation to significant operational changes such as for the “rollovers” of the root zone KSK. 5. Two IANA staff members dedicated to managing the KSK for the root zone We would like to offer that IANA staff give a presentation to the CSC during the ICANN67 meeting to explain in greater details these mechanisms so the CSC and PTI can further discuss the CSC’s role in monitoring the performance under the IANA Naming Function Contract for direct customers of the Naming Function. If this offer is of interest to you, I will work with my colleagues on organizing a presentation for the CSC meeting during ICANN67. Best regards, Naela Sarras Director, IANA Operations Office: +1 310 301 5819 Mobile: +1 310 463 9669 From: ICANN-CSC <icann-csc-bounces@icann.org> on behalf of Maria Otanes <maria.otanes@icann.org> Date: Thursday, December 19, 2019 at 9:36 AM To: "icann-csc@icann.org" <icann-csc@icann.org> Subject: [ICANN-CSC] CSC Meeting 36: Recording, Notes, & Chat Dear CSC, Please find notes and chat from the December CSC meeting attached. Zoom Recording: https://icann.zoom.us/recording/share/fdrp89wVt-XCW9vy2tDU7Bsmvin7SpKB3DpwYv... [icann.zoom.us]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_recording...> Action Items Action 01 36 2019: PTI to send latest version amended SLA creation and transfer to CSC to seek formal approval Action 02 36 2019: CSC and PTI to approve proposed amended SLA formally Action 03 36 2019: After CSC and PTI have approved SLA change, CSC to seek approval for amendment from ccNSO & GNSO Councils Action 04 36 2019: PTI to provide update implementation amended SLA creation and transfer ccTLDs by next meeting Action 05 36 2019: PTI to provide overview of items to consider CSC is entitled and / or should monitor under the IANA Naming Function Contract (including the SOW) by the February meeting Action 06 36 2019: CSC secretariat to provide overview of work items under CSC charter by the February meeting Action 07 36 2019: Chair ensure discussion on scope of performance monitoring topic of March face-to-face meeting (ICANN67) Action 08 36 2019: Amy to draft email request, to be sent by Liman to chair BTC Action 09 36 2019: Liman to send email request to chair BTC Action 10 36 2019: CSC Secretariat to confirm November and December 2020 meeting dates and time after completion 2020 selection process CSC members Best, Ria