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:

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 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.
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.
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.
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.
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-XCW9vy2tDU7Bsmvin7SpKB3DpwYvB5tamwIumekTziMw

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