Managing DS Records from the Parent via CDS/CDNSKEY
RFC 8078
| Document | Type |
RFC - Proposed Standard
(March 2017; Errata)
Updates RFC 7344
|
|
|---|---|---|---|
| Last updated | 2017-06-23 | ||
| Replaces | draft-ogud-dnsop-maintain-ds | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Tim Wicinski | ||
| Shepherd write-up | Show (last changed 2016-06-21) | ||
| IESG | IESG state | RFC 8078 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Joel Jaeggli | ||
| Send notices to | "Tim Wicinski" <tjw.ietf@gmail.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) O. Gudmundsson
Request for Comments: 8078 CloudFlare
Updates: 7344 P. Wouters
Category: Standards Track Red Hat
ISSN: 2070-1721 March 2017
Managing DS Records from the Parent via CDS/CDNSKEY
Abstract
RFC 7344 specifies how DNS trust can be maintained across key
rollovers in-band between parent and child. This document elevates
RFC 7344 from Informational to Standards Track. It also adds a
method for initial trust setup and removal of a secure entry point.
Changing a domain's DNSSEC status can be a complicated matter
involving multiple unrelated parties. Some of these parties, such as
the DNS operator, might not even be known by all the organizations
involved. The inability to disable DNSSEC via in-band signaling is
seen as a problem or liability that prevents some DNSSEC adoption at
a large scale. This document adds a method for in-band signaling of
these DNSSEC status changes.
This document describes reasonable policies to ease deployment of the
initial acceptance of new secure entry points (DS records).
It is preferable that operators collaborate on the transfer or move
of a domain. The best method is to perform a Key Signing Key (KSK)
plus Zone Signing Key (ZSK) rollover. If that is not possible, the
method using an unsigned intermediate state described in this
document can be used to move the domain between two parties. This
leaves the domain temporarily unsigned and vulnerable to DNS
spoofing, but that is preferred over the alternative of validation
failures due to a mismatched DS and DNSKEY record.
Gudmundsson & Wouters Standards Track [Page 1]
RFC 8078 Managing DS Records March 2017
Status of This Memo
This is an Internet Standards Track document.
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). Further information on
Internet Standards is available in Section 2 of RFC 7841.
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/rfc8078.
Copyright Notice
Copyright (c) 2017 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.
Gudmundsson & Wouters Standards Track [Page 2]
RFC 8078 Managing DS Records March 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Introducing a DS Record . . . . . . . . . . . . . . . . . 3
1.2. Removing a DS Record . . . . . . . . . . . . . . . . . . 4
1.3. Notation . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
2. The Three Uses of CDS . . . . . . . . . . . . . . . . . . . . 5
2.1. The Meaning of the CDS RRset . . . . . . . . . . . . . . 5
3. Enabling DNSSEC via CDS/CDNSKEY . . . . . . . . . . . . . . . 6
3.1. Accept Policy via Authenticated Channel . . . . . . . . . 6
3.2. Accept with Extra Checks . . . . . . . . . . . . . . . . 6
3.3. Accept after Delay . . . . . . . . . . . . . . . . . . . 7
3.4. Accept with Challenge . . . . . . . . . . . . . . . . . . 7
3.5. Accept from Inception . . . . . . . . . . . . . . . . . . 7
4. DNSSEC Delete Algorithm . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6.1. Promoting RFC 7344 to Standards Track . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 9
Show full document text