Managing DS Records from the Parent via CDS/CDNSKEY
RFC 8078, “Managing DS Records from the Parent via CDS/CDNSKEY”, is a Proposed Standard document published in March 2017 by O. Gudmundsson, P. Wouters. It updates RFC 7344. It has since been updated by RFC 9615. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8078 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8077 Pseudowire Setup and Maintenance Using the Label Distribution Protocol
- RFC 8079 Guidelines for End-to-End Support of the RTP Control Protocol in Back-to-Back User Agents
- RFC 8076 A Usage for Shared Resources in RELOAD
- RFC 8080 Edwards-Curve Digital Security Algorithm for DNSSEC
- RFC 8075 Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol
- RFC 8081 The "font" Top-Level Media Type
- RFC 8074 Source Address Validation Improvement for Mixed Address Assignment Methods Scenario
- RFC 8082 Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs