Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm Implementation Status
RFC 6944
| Document | Type |
RFC - Proposed Standard
(April 2013; Errata)
Obsoleted by RFC 8624
|
|
|---|---|---|---|
| Author | Scott Rose | ||
| Last updated | 2020-01-21 | ||
| Replaces | draft-srose-dnssec-algo-imp-status | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized with errata bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6944 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Ralph Droms | ||
| IESG note | Andrew Sullivan (ajs@anvilwalrusden.com) is the Document Shepherd | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) S. Rose
Request for Comments: 6944 NIST
Updates: 2536, 2539, 3110, 4034, 4398, April 2013
5155, 5702, 5933
Category: Standards Track
ISSN: 2070-1721
Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm
Implementation Status
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6944.
Rose Standards Track [Page 1]
RFC 6944 DNSSEC DNSKEY Algorithm Status April 2013
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3
2. The DNS Security Algorithm Implementation Status Lists . . . . 3
2.1. Status Definitions . . . . . . . . . . . . . . . . . . . . 3
2.2. Algorithm Implementation Status Assignment Rationale . . . 4
2.3. DNSSEC Implementation Status Table . . . . . . . . . . . . 4
2.4. Specifying New Algorithms and Updating the Status of
Existing Entries . . . . . . . . . . . . . . . . . . . . . 5
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Normative References . . . . . . . . . . . . . . . . . . . 6
5.2. Informative References . . . . . . . . . . . . . . . . . . 7
Rose Standards Track [Page 2]
RFC 6944 DNSSEC DNSKEY Algorithm Status April 2013
1. Introduction
The Domain Name System (DNS) Security Extensions (DNSSEC) ([RFC4033],
[RFC4034], [RFC4035], [RFC4509], [RFC5155], and [RFC5702]) uses
digital signatures over DNS data to provide source authentication and
integrity protection. DNSSEC uses an IANA registry to list codes for
digital signature algorithms (consisting of a cryptographic algorithm
and one-way hash function).
The original list of algorithm status is found in [RFC4034]. Other
DNSSEC RFCs have added new algorithms or changed the status of
algorithms in the registry. However, implementers must read through
all the documents in order to discover which algorithms are
considered wise to implement, which are not, and which algorithms may
become widely used in the future.
This document defines the current implementation status for all
registered algorithms. If the status of algorithms changes, this
document will be replaced with a new one establishing the new status;
see Section 2.4.
This document updates the following: [RFC2536], [RFC2539], [RFC3110],
[RFC4034], [RFC4398], [RFC5155], [RFC5702], and [RFC5933].
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
Show full document text