metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 6944: Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm Implementation Status

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8624.

Current document in this lineage: RFC 9904 — DNSSEC Cryptographic Algorithm Recommendation Update Process

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

The DNS Security Extensions (DNSSEC) requires the use of cryptographic algorithm suites for generating digital signatures over DNS data. There is currently an IANA registry for these algorithms, but there is no record of the recommended implementation status of each algorithm. This document provides an applicability statement on algorithm implementation status for DNSSEC component software. This document lists each algorithm's status based on the current reference. In the case that an algorithm is specified without an implementation status, this document assigns one. This document updates RFCs 2536, 2539, 3110, 4034, 4398, 5155, 5702, and 5933.

Document record

Document ID
RFC6944
Published
April 2013
Authors
S. Rose
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
7
Also known as
—
Obsoleted by:
RFC 8624
Updates:
RFC 2536, RFC 2539, RFC 3110, RFC 4034, RFC 4398, RFC 5155, RFC 5702, RFC 5933

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 →

Referenced by

One later RFC formally updates or obsoletes part of this document.

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/6944-applicability-statement-dns-security-dnssec-dnskey-algorithm-implementation-stat