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

        
        RFC 9904

        Title:      DNSSEC Cryptographic Algorithm Recommendation Update 
                    Process 
        Author:     W. Hardaker,
                    W. Kumari
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2025
        Mailbox:    [email protected],
                    [email protected]
        Pages:      13
        Obsoletes:  RFC 8624
        Updates:    RFC 9157

        I-D Tag:    draft-ietf-dnsop-rfc8624-bis-13.txt

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

        DOI:        10.17487/RFC9904

The DNSSEC protocol makes use of various cryptographic algorithms to
provide authentication of DNS data and proof of nonexistence.  To
ensure interoperability between DNS resolvers and DNS authoritative
servers, it is necessary to specify both a set of algorithm
implementation requirements and usage guidelines to ensure that there
is at least one algorithm that all implementations support. This
document replaces and obsoletes RFC 8624 and moves the canonical
source of algorithm implementation requirements and usage guidance
for DNSSEC from RFC 8624 to the IANA DNSSEC algorithm registries.
This is done to allow the list of requirements to be more easily
updated and referenced. Extensions to these registries can be made in
future RFCs. This document also updates RFC 9157 and incorporates the
revised IANA DNSSEC considerations from that RFC.

This document does not change the recommendation status (MUST, MAY,
RECOMMENDED, etc.) of the algorithms listed in RFC 8624; that is the
work of future documents.

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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team


_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org

Reply via email to