DNS Extensions Working Group S. Rose Internet-Draft NIST Intended status: Standards Track October 14, 2009 Expires: April 17, 2010 DNS Security (DNSSEC) DNSKEY IANA Registry Algorithm Status Addition draft-ietf-dnsext-dnssec-registry-fixes-00 Status of This Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. 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. 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. This Internet-Draft will expire on April 17, 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 Rose Expires April 17, 2010 [Page 1]
Internet-Draft IANA-Registry-Fix October 2009 Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. 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 "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 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. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5.1. Normative References . . . . . . . . . . . . . . . . . . . 5 5.2. Informative References . . . . . . . . . . . . . . . . . . 5 Rose Expires April 17, 2010 [Page 2]
Internet-Draft IANA-Registry-Fix October 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 algorithm (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. Other DNSSEC documents have added new algorithms or changed the status of algorithms in the registry. However, without reading all the documents, implementors must read through all the documents to discover which algorithms are MANDATORY to implement and which are OPTIONAL or obsolete. 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 status . 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. 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 8 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 until 2020". Rose Expires April 17, 2010 [Page 3]
Internet-Draft IANA-Registry-Fix October 2009 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 OPTOINAL [RFC2539] 3 DSA/SHA-1 DSASHA1 Y Y OPTIONAL [RFC3755], [RFC2536], FIPS 186, FIPS 180-1 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 RFC-ietf- dnsext-dnssec- rsasha256-14 9 Reserved until 2020 10 RSA/SHA-512 RSASHA512 Y * OPTIONAL RFC-ietf- dnsext-dnssec- rsasha256-14 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. Any changes to a previously allocated algorithm's status MUST be done by a standards track document. Rose Expires April 17, 2010 [Page 4]
Internet-Draft IANA-Registry-Fix October 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 8 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 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. References 5.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [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. 5.2. Informative References [RFC2535] Eastlake, D., "Domain Name System Security Extensions", RFC 2535, March 1999. Rose Expires April 17, 2010 [Page 5]
Internet-Draft IANA-Registry-Fix October 2009 [RFC2536] Eastlake, D., "DSA KEYs and SIGs in the Domain Name System (DNS)", RFC 2536, March 1999. [RFC2537] Eastlake, D., "RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)", RFC 2537, March 1999. [RFC2539] Eastlake, D., "Storage of Diffie-Hellman Keys in the Domain Name System (DNS)", RFC 2539, March 1999. [RFC3110] Eastlake, D., "RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)", RFC 3110, May 2001. [RFC3755] Weiler, S., "Legacy Resolver Compatibility for Delegation Signer (DS)", RFC 3755, May 2004. [RFC4398] Josefsson, S., "Storing Certificates in the Domain Name System (DNS)", RFC 4398, March 2006. [RFC5155] Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS Security (DNSSEC) Hashed Authenticated Denial of Existence", RFC 5155, March 2008. Author's Address Scott Rose NIST 100 Bureau Dr. Gaithersburg, MD 20899 USA Phone: +1-301-975-8439 EMail: scott.rose@nist.gov Rose Expires April 17, 2010 [Page 6]
