Automating DNSSEC Delegation Trust Maintenance
RFC 7344
|
| Document |
Type |
|
RFC - Informational
(September 2014; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-kumari-ogud-dnsop-cds
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Tim Wicinski
|
|
Shepherd write-up |
|
Show
(last changed 2014-05-05)
|
| IESG |
IESG state |
|
RFC 7344 (Informational)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Joel Jaeggli
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
IANA OK - Actions Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) W. Kumari
Request for Comments: 7344 Google
Category: Informational O. Gudmundsson
ISSN: 2070-1721 OGUD Consulting
G. Barwood
September 2014
Automating DNSSEC Delegation Trust Maintenance
Abstract
This document describes a method to allow DNS Operators to more
easily update DNSSEC Key Signing Keys using the DNS as a
communication channel. The technique described is aimed at
delegations in which it is currently hard to move information from
the Child to Parent.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7344.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Kumari, et al. Informational [Page 1]
RFC 7344 Delegation Trust Maintenance September 2014
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Requirements Notation . . . . . . . . . . . . . . . . . . 4
2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. DNS Delegations . . . . . . . . . . . . . . . . . . . . . 5
2.2. Relationship between Parent and Child DNS Operators . . . 5
2.2.1. Solution Space . . . . . . . . . . . . . . . . . . . 6
2.2.2. DNSSEC Key Change Process . . . . . . . . . . . . . . 7
3. CDS (Child DS) and CDNSKEY (Child DNSKEY) Record Definitions 7
3.1. CDS Resource Record Format . . . . . . . . . . . . . . . 8
3.2. CDNSKEY Resource Record Format . . . . . . . . . . . . . 8
4. Automating DS Maintenance with CDS/CDNSKEY Records . . . . . 8
4.1. CDS and CDNSKEY Processing Rules . . . . . . . . . . . . 9
5. CDS/CDNSKEY Publication . . . . . . . . . . . . . . . . . . . 9
6. Parent-Side CDS/CDNSKEY Consumption . . . . . . . . . . . . . 9
6.1. Detecting a Changed CDS/CDNSKEY . . . . . . . . . . . . . 10
6.1.1. CDS/CDNSKEY Polling . . . . . . . . . . . . . . . . . 10
6.1.2. Polling Triggers . . . . . . . . . . . . . . . . . . 11
6.2. Using the New CDS/CDNSKEY Records . . . . . . . . . . . . 11
6.2.1. Parent Calculates DS . . . . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 12
9. Security Considerations . . . . . . . . . . . . . . . . . . . 13
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
11.1. Normative References . . . . . . . . . . . . . . . . . . 15
11.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. RRR Background . . . . . . . . . . . . . . . . . . . 17
Appendix B. CDS Key Rollover Example . . . . . . . . . . . . . . 17
Kumari, et al. Informational [Page 2]
RFC 7344 Delegation Trust Maintenance September 2014
1. Introduction
The first time a DNS Operator signs a zone, they need to communicate
the keying material to their Parent through some out-of-band method
Show full document text