Comment Close
Date
Statement
Name 

Status

Assignee(s) and
RALO(s)

Call for
Comments
Call for
Comments
Close 
Vote
Announcement 
Vote OpenVote
Reminder
Vote CloseDate of SubmissionStaff Contact and EmailStatement Number
12.04.2013Consultation on Root Zone KSK RolloverNo Statementn/an/an/an/an/an/an/an/aJoe Abley
joe.abley@icann.org
 
n/a
Comment / Reply Periods (*)
Comment Open Date: 
8 March 2013
Comment Close Date: 
12 April 2013 - 23:59 UTC
Reply Open Date: 
26 April 2013
Reply Close Date: 
31 May 2013 - 23:59 UTC
Important Information Links
Brief Overview
Originating Organization: 
IANA Department
Categories/Tags: 
  • Reviews/Improvements
  • Security/Stability
Purpose (Brief): 

The Internet Assigned Numbers Authority (IANA) Functions contract (SA1301-­12-­CN-­0035) between ICANNand the United States Department of Commerce, National Telecommunications Information Administration (NTIA) to perform services related to certain interdependent Internet technical management functions calls for a public consultation from all interested and affected parties to help satisfy the following objective:

C.2.9.2.f Root Domain Name System Security Extensions (DNSSEC) Key Management –The Contractor shall be responsible for the management of the root zone Key Signing Key (KSK), including generation, publication, and use for signing the Root Keyset. As delineated in the Requirements at Appendix 2 entitled Baseline Requirements for DNSSEC in the Authoritative Root Zone  that is incorporated by reference herein as if fully set forth. The Contractor shall work collaboratively with NTIA and the Root Zone Maintainer, in the performance of this function.

More specifically, this consultation involves "Appendix 2: Baseline Requirements for DNSSEC in the Authoritative Root Zone," that articulates the contract requirement to perform a scheduled root zone KSK rollover.

The consultation is being conducted using the ICANN Public Comment Process, consistent with the contract requirements. The feedback received during this consultation will inform the Root Zone Management Partners on the subject of KSK rollover, so that a schedule and a detailed implementation plan for KSK rollovers can be established.

Current Status: 
Planning for scheduled KSK rollover in the root zone is anticipated, but work is deferred pending the results of this public consultation.
Next Steps: 
Planning for scheduled KSK rollover in the root zone will proceed, informed by the results of this public consultation.
Staff Contact: 
Joe Abley
Detailed Information
Section I: Description, Explanation, and Purpose: 

ICANN, consistent with the terms of the IANA functions contract, is committed to executing a KSK rollover in the root zone and now seeks public feedback with respect to developing a detailed scheduling and implementation plan.

Comments are welcome on any aspect of KSK management related to KSK rollover, and specifically on the following questions:

  1. What prerequisites need to be considered prior to a first scheduled KSK rollover?
  2. When should the first scheduled KSK rollover take place?
  3. What should the IANA Functions Operator (ICANN) and the other Root Zone Management Partners do to gauge the technical and end-user impact of a KSK rollover following the first scheduled KSK rollover?
  4. How often should a scheduled KSK rollover take place, following the first one?
  5. How far should the published calendar for scheduled KSK rollovers extend into the future?
  6. What public notification should take place in advance of a scheduled KSK rollover?
  7. What other considerations are necessary for the Root Zone Management Partners to take into consideration prior, during, and after a planned key roll over?
Section II: Background: 
Please refer to the document, "Consultation on Root Zone KSK Rollover" [PDF, 371 KB]
Section III: Document and Resource Links: 
Please refer to the document, "Consultation on Root Zone KSK Rollover" [PDF, 371 KB]
Section IV: Additional Information: 
None

(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.

FINAL VERSION TO BE SUBMITTED IF RATIFIED

The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote. 

FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.

FIRST DRAFT SUBMITTED

The first draft submitted will be placed here before the call for comments begins.

 

  • No labels