DNS Extensions Working Group S. Rose Internet-Draft NIST Updates: 4034 (if approved) November 12, 2009 Intended status: Standards Track Expires: May 16, 2010 DNS Security (DNSSEC) DNSKEY IANA Registry Algorithm Status Addition draft-ietf-dnsext-dnssec-registry-fixes-01 Abstract The DNS Security Extensions (DNSSEC) has an IANA registry to allocate cryptographic algorithm suites for use in generating digital signatures over DNS data. Newly introduced cryptographic algorithms to DNSSEC mean implementors need to know which algorithms need to be implmented, which are optional, and which are obsolete. This document adds a column to the IANA registry table for Domain Name System Security (DNSSEC) Algorithm Numbers to list their status for use. Requirements Language The key words "MANDATORY", "OPTIONAL", "OBSOLETE", "DISCOURAGED", "ENCOURAGED" and "RESERVED" in this document are to be interpreted as described in [I-D.ogud-iana-protocol-maintenance-words] Status of This Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Rose Expires May 16, 2010 [Page 1]
Internet-Draft IANA-Registry-Fix November 2009 This Internet-Draft will expire on May 16, 2010. Copyright Notice Copyright (c) 2009 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 BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. DNS Security Algorithm Number Subregisitry Fixes . . . . . . . 3 2.1. Individual Domain Name System Security (DNSSEC) Algorithm Number Registry Entry Fixes . . . . . . . . . . . 3 2.2. Domain Name System Security (DNSSEC) Algorithm Number Registry . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. Normative References . . . . . . . . . . . . . . . . . . . . . 5 Rose Expires May 16, 2010 [Page 2]
Internet-Draft IANA-Registry-Fix November 2009 1. Introduction The DNS Security Extensions (DNSSEC) [RFC4033], [RFC4034], and [RFC4035] uses digital signatures over DNS data to provide source authentication and integrity protection. DNSSEC uses an IANA registry to allocate codes for digital signature algorithms (consisting of a cryptographic algorithm and one-way hash function). Certain digital signature algorithms are considered MANDATORY to implement for interoperability while others are listed as OPTIONAL or OBSOLETE. The original list of algorithm status is found in [RFC4034]. Other DNSSEC documents have added new algorithms or changed the status of algorithms in the registry. However, implementors must read through all the documents in order to discover which algorithms are mandatory to implement and which are optional or no longer used. This document requests a column to be added to the IANA registry for Domain Name System Security (DNSSEC) Algorithm Numbers. This column will list the current status of each digital signature algorithm in the registry. 2. DNS Security Algorithm Number Subregisitry Fixes The DNS Security Algorithm Number subregistry (part of the Domain Name System (DNS) Security Number registry) will be modified to include a new column. This column will contain the current implementation status of the given algorithm. This document does not make any changes to any other column in the registry table. There are additional fixes to entries that are described in sub- section 2.1. The overall new registry table is in sub-section 2.2. The values for the status were obtained from [RFC4034] with updates for algorithms specified after the originial DNSSEC specification. 2.1. Individual Domain Name System Security (DNSSEC) Algorithm Number Registry Entry Fixes This document changes three entries in the Domain Name System Security (DNSSEC) Algorithm Registry. They are: The description for allocation number 4 is changed to "Reserved until 2020". The description for allocation number 9 is changed to "Reserved until 2020". The description for allocation number 11 is changed to "Reserved Rose Expires May 16, 2010 [Page 3]
Internet-Draft IANA-Registry-Fix November 2009 until 2020". 2.2. Domain Name System Security (DNSSEC) Algorithm Number Registry As of the current time, the DNS Security Algorithm Number subregistry would look like the following: Zone Trans Number Description Mnem. Sign Sign Status Reference ------ ----------- ------ ---- ----- ------------ --------- 0 Reserved [RFC4398] 1 RSA/MD5 RSAMD5 N Y OBSOLETE [RFC4034], [RFC2537] 2 Diffie-Hellman DH N Y OPTIONAL [RFC2539] 3 DSA/SHA-1 DSASHA1 Y Y OPTIONAL [RFC3755], [RFC2536], FIPS 186-3, FIPS 180-3 4 Reserved until ECC 2020 5 RSA/SHA-1 RSASHA1 Y Y MANDATORY [RFC3755], [RFC3110] 6 DSA-NSEC3-SHA1 DSA-NSEC3 Y Y OPTIONAL [RFC5155] -SHA1 7 RSASHA1-NSEC3 RSASHA1- Y Y OPTIONAL [RFC5155] -SHA1 NSEC3- SHA1 8 RSA/SHA-256 RSASHA256 Y * OPTIONAL [RFC5702] 9 Reserved until 2020 10 RSA/SHA-512 RSASHA512 Y * OPTIONAL [RFC5702] 11 Reserved until 2020 12-251 Unassigned 252 Reserved for INDIRECT N N OPTIONAL [RFC4034] Indirect keys 253 private algo- PRIVATE Y Y OPTIONAL [RFC3755], domain name [RFC2535] 254 private algo- PRIVATEOID Y Y OPTIONAL [RFC3755], OID [RFC2535] 255 Reserved Newly allocated algorithms will need to state their intended status in their specification. The only way to change the status of an existing registry entry is to update RFC 4034; The IANA registry entry can be updated at the same time as the update to RFC 4034 is published. Rose Expires May 16, 2010 [Page 4]
Internet-Draft IANA-Registry-Fix November 2009 3. IANA Considerations This document consists entirely of DNS IANA Considerations and includes the following changes detailed in Section 2.1: The description of allocation 4 is changed from "Reserved for ECC" to "Reserved until 2020". The description of allocation 9 is changed from "Unassigned" to "Reserved until 2020". The description of allocation 11 is changed from "Unassigned" to "Reserved until 2020". The references to FIPS 180 and FIPS 186 have been updated (to FIPS 180-3 and FIPS 186-3 respectively) to reflect the latest versions. These revisions are maintenance updates and the main content of the FIPS document have not changed. The new table is in Section 2.2. The Domain Name System (DNS) Security Algorithm Number registry is available at http:// www.iana.org/assignments/dns-sec-alg-numbers/ dns-sec-alg-numbers.xhtml. 4. Security Considerations This document seeks to add a column to an existing IANA registry. It is not meant to be a discussion on algorithm superiority. No new security considerations are raised in this document. 5. Normative References [I-D.ogud-iana-protocol-maintenance-words] Gudmundsson, O. and S. Rose, "Definitions for expressing standards requirements in IANA registries.", draft-ogud- iana-protocol- maintenance-words-01 (work in progress), November 2009. [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, "DNS Security Introduction and Requirements", RFC 4033, March 2005. Rose Expires May 16, 2010 [Page 5]
Internet-Draft IANA-Registry-Fix November 2009 [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. Author's Address Scott Rose NIST 100 Bureau Dr. Gaithersburg, MD 20899 USA Phone: +1-301-975-8439 EMail: cyclescott@gmail.com Rose Expires May 16, 2010 [Page 6]