CurrentPROPOSED STANDARDIETF stream

RFC 9904: DNSSEC Cryptographic Algorithm Recommendation Update Process

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9904
Published
November 2025
Authors
W. Hardaker; W. Kumari
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
13
Also known as
Obsoletes:
RFC 8624
Updates:
RFC 9157

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 6944 (2013)
  2. RFC 8624 (2019)
  3. RFC 9904 (2025)

Read the full history of DNSSEC Cryptographic Algorithm Recommendation Update Process

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9904-dnssec-cryptographic-algorithm-recommendation-update-process