idnits 2.17.1 draft-ietf-dnsext-dnssec-registry-update-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 3, 2012) is 4277 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'THISDOC' is mentioned on line 139, but not defined Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DNS Extensions Working Group S. Rose 3 Internet-Draft NIST 4 Intended status: Standards Track August 3, 2012 5 Expires: February 4, 2013 7 DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry Updates 8 draft-ietf-dnsext-dnssec-registry-update-04 10 Abstract 12 The DNS Security Extensions (DNSSEC) requires the use of 13 cryptographic algorithm suites for generating digital signatures over 14 DNS data. The algorithms specified for use with DNSSEC are reflected 15 in an IANA maintained registry. This document presents a set of 16 changes for some entries of the registry. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on February 4, 2013. 35 Copyright Notice 37 Copyright (c) 2012 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. The DNS Security Algorithm Number Sub-registry . . . . . . . . 3 55 2.1. Updates and Additions . . . . . . . . . . . . . . . . . . . 3 56 2.2. Domain Name System (DNS) Security Algorithm Number 57 Registry Table . . . . . . . . . . . . . . . . . . . . . . 4 59 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 61 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 63 5. Informative References . . . . . . . . . . . . . . . . . . . . 5 65 1. Introduction 67 The Domain Name System (DNS) Security Extensions (DNSSEC, defined by 68 [RFC4033], [RFC4034], [RFC4035], [RFC4509], [RFC5155], and [RFC5702]) 69 use digital signatures over DNS data to provide source authentication 70 and integrity protection. DNSSEC uses an IANA registry to list codes 71 for digital signature algorithms (consisting of an asymmetric 72 cryptographic algorithm and a one-way hash function). 74 This document updates a set of entries in the IANA registry for 75 Domain Name System Security (DNSSEC) Algorithm Numbers. These 76 updated entries are given in Section 2.2 below. This list includes 77 changes to selected entries originally set aside for future algorithm 78 specification that did not occur. These three entries are changed to 79 "Reserved" to avoid potential conflicts with older implementations. 80 This document also brings the list of references for entries up to 81 date. 83 There are auxillary sub-registries related to the Domain Name System 84 Security (DNSSEC) Algorithm Numbers registry that deal with various 85 Diffie-Hellman parameters used with DNSSEC. These registry tables 86 are not altered by this document. 88 2. The DNS Security Algorithm Number Sub-registry 90 The DNS Security Algorithm Number sub-registry (part of the Domain 91 Name System (DNS) Security Number registry) contains a set of entries 92 that contain errors. There are additional differences to entries 93 that are described in sub-section 2.1 and the complete list of 94 changed registry entries is in sub-section 2.2. 96 2.1. Updates and Additions 98 This document updates three entries in the Domain Name System 99 Security (DNSSEC) Algorithm Registry. They are: 101 The description for assignment number 4 is changed to "Reserved". 103 The description for assignment number 9 is changed to "Reserved". 105 The description for assignment number 11 is changed to "Reserved". 107 The above entries are changed to "Reserved" because they were 108 placeholders for algorithms that were not fully specified for use 109 with DNSSEC. Older implementations may still have these algorithm 110 codes assigned, so these codes are reserved to prevent potential 111 incompatibilities. 113 2.2. Domain Name System (DNS) Security Algorithm Number Registry Table 115 The list of Domain Name System (DNS) Security Algorithm Number 116 registry entry changes are given below. All other existing entries 117 in the registry table are unchanged by this document and are not 118 shown. The other two tables in this registry (DNS KEY Record Diffie- 119 Hellman Prime Lengths and DNS KEY Record Diffie-Hellman Well-Known 120 Prime/Generator Pairs) are not changed in any way by this document. 122 Zone Trans. 123 Number Description Mnemonic Sign Sign Reference 124 ------ ----------- -------- ---- ------ --------- 125 0 Reserved [RFC4034], 126 [RFC4398] 128 1 RSA/MD5 RSAMD5 N Y [RFC3110], 129 (Deprecated, [RFC4034] 130 see 5) 132 4 Reserved [THISDOC] 134 5 RSA/SHA-1 RSASHA1 Y Y [RFC3110] 135 [RFC4034] 137 9 Reserved [THISDOC] 139 11 Reserved [THISDOC] 141 15-122 Unassigned [RFC4034] 143 123-251 Reserved [RFC4034], 144 [RFC6014] 145 253 private PRIVATEDNS Y Y [RFC4034] 146 algorithm 147 254 private PRIVATEOID Y Y [RFC4034] 148 algorithm OID 150 3. IANA Considerations 152 This document updates a set of Domain Name System (DNS) Security 153 Algorithm Numbers registry entries as given in Section 2.2. The 154 changes include moving three registry entries to "Reserved" and 155 updating the reference list for entries. 157 The original Domain Name System (DNS) Security Algorithm Number 158 registry is available at 159 http://www.iana.org/assignments/dns-sec-alg-numbers. 161 4. Security Considerations 163 This document replaces the Domain Name System (DNS) Security 164 Algorithm Numbers registry with an updated table. It is not meant to 165 be a discussion on algorithm superiority. No new security 166 considerations are raised in this document. 168 5. Informative References 170 [RFC3110] Eastlake, D., "RSA/SHA-1 SIGs and RSA KEYs in the Domain 171 Name System (DNS)", RFC 3110, May 2001. 173 [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. 174 Rose, "DNS Security Introduction and Requirements", 175 RFC 4033, March 2005. 177 [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. 178 Rose, "Resource Records for the DNS Security Extensions", 179 RFC 4034, March 2005. 181 [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. 182 Rose, "Protocol Modifications for the DNS Security 183 Extensions", RFC 4035, March 2005. 185 [RFC4398] Josefsson, S., "Storing Certificates in the Domain Name 186 System (DNS)", RFC 4398, March 2006. 188 [RFC4509] Hardaker, W., "Use of SHA-256 in DNSSEC Delegation Signer 189 (DS) Resource Records (RRs)", RFC 4509, May 2006. 191 [RFC5155] Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS 192 Security (DNSSEC) Hashed Authenticated Denial of 193 Existence", RFC 5155, March 2008. 195 [RFC5702] Jansen, J., "Use of SHA-2 Algorithms with RSA in DNSKEY 196 and RRSIG Resource Records for DNSSEC", RFC 5702, 197 October 2009. 199 [RFC6014] Hoffman, P., "Cryptographic Algorithm Identifier 200 Allocation for DNSSEC", RFC 6014, November 2010. 202 Author's Address 204 Scott Rose 205 NIST 206 100 Bureau Dr. 207 Gaithersburg, MD 20899 208 USA 210 Phone: +1-301-975-8439 211 EMail: scottr.nist@gmail.com