|DNS Extensions Working Group||S. Rose|
|Updates: 2536, 2539, 3110, 4034, 4398, 5155, 5702, 5933 (if approved)||November 18, 2011|
|Intended status: Best Current Practice|
|Expires: May 21, 2012|
Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm Implementation Status
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 that is incomplete in that it lacks the recommended implementation status of each algorithm. This document provides an applicability statement on algorithm implementation compliance status for DNSSEC implementations. 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.
Status of this Memo
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 21, 2012.
Copyright (c) 2011 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
- 1.1. Requirements Language
- 2. The DNS Security Algorithm Implementation Status Lists
- 2.1. Algorithm Implementation Status Assignement Rationale
- 2.2. DNSSEC Implementation Status Table
- 2.3. Specifying New Algorithms and Updating Status of Existing Entries
- 3. IANA Considerations
- 4. Security Considerations
- 5. References
- Author's Address
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 RFC's 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 includes the current compliance status for certain algorithms.
This compliance status indication is only to be considered for implementation, not deployment or operations. Operators are free to deploy any digital signature algorithm available in implementations or algorithms chosen by local security policies. This status is to measure compliance to this RFC only.
This document updates the following: [RFC2536], [RFC2539], [RFC3110], [RFC4034], [RFC4398], [RFC5155], [RFC5702], and [RFC5933].
1.1. Requirements Language
The key words "MUST", "MUST NOT", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
2. The DNS Security Algorithm Implementation Status Lists
2.1. Algorithm Implementation Status Assignement Rationale
The status of RSASHA1-NSEC3-SHA1 is set to RECOMMENDED TO IMPLEMENT. This is due to the fact that RSA/SHA-1 is a MUST IMPLEMENT. The status of RSA/SHA-256 and RSA/SHA-512 are also set to RECOMMENDED TO IMPLEMENT as it is believed that these algorithms will replace an older algorithm (e.g. RSA/SHA-1) that have a perceived weakness in its hash algorithm (SHA-1).
2.2. DNSSEC Implementation Status Table
The DNSSEC algorithm implementation status table is listed below. Only the algorithms already specified for use with DNSSEC (at the time of writing) are listed.
+------------+------------+-----------------+-------------+ | MUST | MUST NOT | RECOMMENDED | OPTIONAL | | IMPLEMENT | IMPLEMENT | TO IMPLEMENT | | +------------+------------+-----------------+-------------+ | | | | | | RSASHA1 | RSAMD5 | RSASHA256 | DSASHA1 | | | | RSASHA1-NSEC3 | DH | | | | -SHA1 | DSA-NSEC3 | | | | RSASHA512 | -SHA1 | | | | | GOST-ECC | | | | | | +------------+------------+-----------------+-------------+
This table does not list the Reserved values in the IANA registry table or the values for INDIRECT (252), PRIVATE (253) and PRIVATEOID (254). These values may relate to more than one algorithm and are therefore up to the implementer's discretion. Their implementation (or lack thereof) therefore cannot be included when judging compliance to this document.
2.3. Specifying New Algorithms and Updating Status of Existing Entries
[RFC6014] establishes a parallel procedure for adding a registry entry for a new algorithm other than a standards track document. Algorithms entered into the registry using that procedure are to be considered OPTIONAL for implementation purposes. Specifications that follow this path do not need to obsolete or update this document.
Adding a newly specified algorithm to the registry with a compliance status SHALL entail obsolescing this document and replacing the registry table (with the new algorithm entry). Altering the status column value of any existing algorithm in the registry SHALL entail obsolescing this document and replacing the registry table.
This document cannot be updated, only made obsolete and replaced by a successor document.
3. IANA Considerations
This document lists the implementation status of cryptographic algorithms used with DNSSEC. These algorithms are maintained in an IANA registry. There are no changes to the registry in this document. However this document asks to be listed as a reference for the entire registry.
4. Security Considerations
This document replaces the Domain Name System (DNS) Security Algorithm Numbers registry. It is not meant to be a discussion on algorithm superiority. No new security considerations are raised in this document.