metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC

Still current, but amended. Parts of this document are changed or extended by RFC 9157. Read both.

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

This document specifies how DNSSEC cryptographic algorithm identifiers in the IANA registries are allocated. It changes the requirement from "standard required" to "RFC Required". It does not change the list of algorithms that are recommended or required for DNSSEC implementations. [STANDARDS-TRACK]

Document record

Document ID
RFC6014
Published
November 2010
Authors
P. Hoffman
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
6
Also known as
—
Updates:
RFC 4033, RFC 4034, RFC 4035
Updated by:
RFC 9157

Topics

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/6014-cryptographic-algorithm-identifier-allocation-for-dnssec