RFC 9615 on Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator

A new Request for Comments is now available in online RFC libraries.

        RFC 9615

        Title:      Automatic DNSSEC Bootstrapping Using
                    Authenticated Signals from the Zone's Operator 
        Author:     P. Thomassen,
                    N. Wisiol
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2024
        Mailbox:    peter@desec.io,
                    nils@desec.io
        Pages:      12
        Updates:    RFC 7344, RFC 8078

        I-D Tag:    draft-ietf-dnsop-dnssec-bootstrapping-11.txt

        URL:        https://www.rfc-editor.org/info/rfc9615

        DOI:        10.17487/RFC9615

This document introduces an in-band method for DNS operators to
publish arbitrary information about the zones for which they are
authoritative, in an authenticated fashion and on a per-zone basis.
The mechanism allows managed DNS operators to securely announce
DNSSEC key parameters for zones under their management, including for
zones that are not currently securely delegated.

Whenever DS records are absent for a zone's delegation, this signal
enables the parent's registry or registrar to cryptographically
validate the CDS/CDNSKEY records found at the child's apex. The
parent can then provision DS records for the delegation without
resorting to out-of-band validation or weaker types of cross-checks
such as "Accept after Delay".

This document establishes the DS enrollment method described in
Section 4 of this document as the preferred method over those from
Section 3 of RFC 8078. It also updates RFC 7344.

This document is a product of the Domain Name System Operations Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC