DNS Extensions Working Group S. Rose
Internet-Draft NIST
Intended status: Standards Track August 2012
Expires: January 31, 2013

DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry Updates
draft-ietf-dnsext-dnssec-registry-update-04

Abstract

The DNS Security Extensions (DNSSEC) requires the use of cryptographic algorithm suites for generating digital signatures over DNS data. The algorithms specified for use with DNSSEC are reflected in an IANA maintained registry. This document presents a set of changes for some entries of the registry.

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 January 31, 2013.

Copyright Notice

Copyright (c) 2012 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

The Domain Name System (DNS) Security Extensions (DNSSEC, defined by [RFC4033], [RFC4034], [RFC4035], [RFC4509], [RFC5155], and [RFC5702]) use 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 an asymmetric cryptographic algorithm and a one-way hash function).

This document updates a set of entries in the IANA registry for Domain Name System Security (DNSSEC) Algorithm Numbers. These updated entries are given in Section 2.2 below. This list includes changes to selected entries originally set aside for future algorithm specification that did not occur. These three entries are changed to "Reserved" to avoid potential conflicts with older implementations. This document also brings the list of references for entries up to date.

There are auxillary sub-registries related to the Domain Name System Security (DNSSEC) Algorithm Numbers registry that deal with various Diffie-Hellman parameters used with DNSSEC. These registry tables are not altered by this document.

2. The DNS Security Algorithm Number Sub-registry

The DNS Security Algorithm Number sub-registry (part of the Domain Name System (DNS) Security Number registry) contains a set of entries that contain errors. There are additional differences to entries that are described in sub-section 2.1 and the complete list of changed registry entries is in sub-section 2.2.

2.1. Updates and Additions

This document updates three entries in the Domain Name System Security (DNSSEC) Algorithm Registry. They are:

The description for assignment number 4 is changed to "Reserved".

The description for assignment number 9 is changed to "Reserved".

The description for assignment number 11 is changed to "Reserved".

The above entries are changed to "Reserved" because they were placeholders for algorithms that were not fully specified for use with DNSSEC. Older implementations may still have these algorithm codes assigned, so these codes are reserved to prevent potential incompatibilities.

2.2. Domain Name System (DNS) Security Algorithm Number Registry Table

The list of Domain Name System (DNS) Security Algorithm Number registry entry changes are given below. All other existing entries in the registry table are unchanged by this document and are not shown. The other two tables in this registry (DNS KEY Record Diffie-Hellman Prime Lengths and DNS KEY Record Diffie-Hellman Well-Known Prime/Generator Pairs) are not changed in any way by this document.

  
                                          Zone  Trans.  
 Number  Description       Mnemonic       Sign   Sign      Reference
 ------  -----------       --------       ----  ------     ---------
   0      Reserved                                         [RFC4034],
                                                           [RFC4398]
  
   1      RSA/MD5           RSAMD5          N     Y        [RFC3110],
         (Deprecated,                                      [RFC4034]
         see 5)                                 
  
   4      Reserved                                         [THISDOC] 

   5      RSA/SHA-1         RSASHA1         Y     Y        [RFC3110]
			                                   [RFC4034]
 
   9      Reserved                                         [THISDOC]

  11      Reserved                                         [THISDOC]

15-122    Unassigned                                       [RFC4034]

123-251   Reserved	                                   [RFC4034],
                                                           [RFC6014]
  253     private           PRIVATEDNS      Y     Y        [RFC4034]
          algorithm 
  254     private           PRIVATEOID      Y     Y        [RFC4034]
          algorithm OID

3. IANA Considerations

This document updates a set of Domain Name System (DNS) Security Algorithm Numbers registry entries as given in Section 2.2. The changes include moving three registry entries to "Reserved" and updating the reference list for entries.

The original Domain Name System (DNS) Security Algorithm Number registry is available at http://www.iana.org/assignments/dns-sec-alg-numbers.

4. Security Considerations

This document replaces the Domain Name System (DNS) Security Algorithm Numbers registry with an updated table. It is not meant to be a discussion on algorithm superiority. No new security considerations are raised in this document.

5. References

[RFC3110] Eastlake, D., "RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)", RFC 3110, May 2001.
[RFC4033] Arends, R., Austein, R., Larson, M., Massey, D. and S. Rose, "DNS Security Introduction and Requirements", RFC 4033, March 2005.
[RFC4034] Arends, R., Austein, R., Larson, M., Massey, D. and S. Rose, "Resource Records for the DNS Security Extensions", RFC 4034, March 2005.
[RFC4035] Arends, R., Austein, R., Larson, M., Massey, D. and S. Rose, "Protocol Modifications for the DNS Security Extensions", RFC 4035, March 2005.
[RFC4398] Josefsson, S., "Storing Certificates in the Domain Name System (DNS)", RFC 4398, March 2006.
[RFC4509] Hardaker, W., "Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)", RFC 4509, May 2006.
[RFC5155] Laurie, B., Sisson, G., Arends, R. and D. Blacka, "DNS Security (DNSSEC) Hashed Authenticated Denial of Existence", RFC 5155, March 2008.
[RFC5702] Jansen, J., "Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC", RFC 5702, October 2009.
[RFC6014] Hoffman, P., "Cryptographic Algorithm Identifier Allocation for DNSSEC", RFC 6014, November 2010.

Author's Address

Scott Rose NIST 100 Bureau Dr. Gaithersburg, MD 20899 USA Phone: +1-301-975-8439 EMail: scottr.nist@gmail.com