RFC 8624: Algorithm Implementation Requirements and Usage Guidance for DNSSEC
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9904.
Current document in this lineage: 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 in order 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 a set of algorithm implementation requirements and usage guidelines to ensure that there is at least one algorithm that all implementations support. This document defines the current algorithm implementation requirements and usage guidance for DNSSEC. This document obsoletes RFC 6944.
Document record
- Document ID
- RFC8624
- Published
- June 2019
- Authors
- P. Wouters; O. Sury
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 6944 (2013)
- RFC 8624 (2019)
- RFC 9904 (2025) ✓
Read the full history of DNSSEC Cryptographic Algorithm Recommendation Update Process →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8630Resource Public Key Infrastructure (RPKI) Trust Anchor LocatorCurrent
August 2019
- RFC 8618Compacted-DNS (C-DNS): A Format for DNS Packet CaptureCurrent
September 2019
- RFC 8634BGPsec Router Certificate RolloverCurrent
August 2019
- RFC 8635Router Keying for BGPsecCurrent
August 2019
- RFC 8639Subscription to YANG NotificationsCurrent
September 2019
- RFC 8640Dynamic Subscription to YANG Events and Datastores over NETCONFCurrent
September 2019
- RFC 8608BGPsec Algorithms, Key Formats, and Signature FormatsCurrent
June 2019
- RFC 8641Subscription to YANG Notifications for Datastore UpdatesCurrent
September 2019
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?