draft-ietf-dnsext-dnssec-registry-update-02.txt   draft-ietf-dnsext-dnssec-registry-update-03.txt 
DNS Extensions Working Group S. Rose DNS Extensions Working Group S. Rose
Internet-Draft NIST Internet-Draft NIST
Intended status: Standards Track April 19, 2012 Intended status: Standards Track June 11, 2012
Expires: October 21, 2012 Expires: December 13, 2012
DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry Updates DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry Updates
draft-ietf-dnsext-dnssec-registry-update-02 draft-ietf-dnsext-dnssec-registry-update-03
Abstract Abstract
The DNS Security Extensions (DNSSEC) requires the use of The DNS Security Extensions (DNSSEC) requires the use of
cryptographic algorithm suites for generating digital signatures over cryptographic algorithm suites for generating digital signatures over
DNS data. The algorithms specified for use with DNSSEC are reflected DNS data. The algorithms specified for use with DNSSEC are reflected
in an IANA maintained registry. This document presents a set of in an IANA maintained registry. This document presents a set of
changes for some entries of the registry. changes for some entries of the registry.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 21, 2012. This Internet-Draft will expire on December 13, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 15 skipping to change at page 3, line 15
1. Introduction 1. Introduction
The Domain Name System (DNS) Security Extensions (DNSSEC, defined by The Domain Name System (DNS) Security Extensions (DNSSEC, defined by
[RFC4033], [RFC4034], [RFC4035], [RFC4509], [RFC5155], and [RFC5702]) [RFC4033], [RFC4034], [RFC4035], [RFC4509], [RFC5155], and [RFC5702])
use digital signatures over DNS data to provide source authentication use digital signatures over DNS data to provide source authentication
and integrity protection. DNSSEC uses an IANA registry to list codes and integrity protection. DNSSEC uses an IANA registry to list codes
for digital signature algorithms (consisting of an asymmetric for digital signature algorithms (consisting of an asymmetric
cryptographic algorithm and a one-way hash function). cryptographic algorithm and a one-way hash function).
This document updates a set of entries in the IANA registry for This document updates a set of entries in the IANA registry for
Domain Name System Security (DNSSEC) Algorithm Numbers. These new Domain Name System Security (DNSSEC) Algorithm Numbers. These
entries are given in Section 2.2 below. This list includes changes updated entries are given in Section 2.2 below. This list includes
to selected entries originally set aside for future algorithm changes to selected entries originally set aside for future algorithm
specification that did not occur. These three entries are changed to specification that did not occur. These three entries are changed to
"Reserved" to avoid potential conflicts with older implementations. "Reserved" to avoid potential conflicts with older implementations.
This document also brings the list of references for entries up to This document also brings the list of references for entries up to
date. date.
There are auxillary registries related to the Domain Name System There are auxillary sub-registries related to the Domain Name System
Security (DNSSEC) Algorithm Numbers registry that deal with various Security (DNSSEC) Algorithm Numbers registry that deal with various
Diffie-Hellmen parameters used with DNSSEC. These registry tables Diffie-Hellmen parameters used with DNSSEC. These registry tables
are not altered by this document. are not altered by this document.
2. The DNS Security Algorithm Number Sub-registry 2. The DNS Security Algorithm Number Sub-registry
The DNS Security Algorithm Number sub-registry (part of the Domain The DNS Security Algorithm Number sub-registry (part of the Domain
Name System (DNS) Security Number registry) contains a set of entries Name System (DNS) Security Number registry) contains a set of entries
that contain errors. There are additional differences to entries that contain errors. There are additional differences to entries
that are described in sub-section 2.1 and the complete list of that are described in sub-section 2.1 and the complete list of
skipping to change at page 4, line 37 skipping to change at page 4, line 37
[RFC4034] [RFC4034]
9 Reserved [THISDOC] 9 Reserved [THISDOC]
11 Reserved [THISDOC] 11 Reserved [THISDOC]
15-122 Unassigned [RFC4034] 15-122 Unassigned [RFC4034]
123-251 Reserved [RFC4034], 123-251 Reserved [RFC4034],
[RFC6014] [RFC6014]
253 private PRIVATEDNS Y Y [RFC4034]
252 Reserved for INDIRECT N N [RFC4034]
Indirect keys
253 private PRIVATE Y Y [RFC4034]
algorithm algorithm
254 private PRIVATEOID Y Y [RFC4034] 254 private PRIVATEOID Y Y [RFC4034]
algorithm OID algorithm OID
255 Reserved [RFC4034]
3. IANA Considerations 3. IANA Considerations
This document updates a set of Domain Name System (DNS) Security This document updates a set of Domain Name System (DNS) Security
Algorithm Numbers registry entries as given in Section 2.2. The Algorithm Numbers registry entries as given in Section 2.2. The
changes include moving three registry entries to "Reserved" and changes include moving three registry entries to "Reserved" and
updating the reference list for entries. updating the reference list for entries.
The original Domain Name System (DNS) Security Algorithm Number The original Domain Name System (DNS) Security Algorithm Number
registry is available at registry is available at
skipping to change at page 5, line 18 skipping to change at page 5, line 14
4. Security Considerations 4. Security Considerations
This document replaces the Domain Name System (DNS) Security This document replaces the Domain Name System (DNS) Security
Algorithm Numbers registry with an updated table. It is not meant to Algorithm Numbers registry with an updated table. It is not meant to
be a discussion on algorithm superiority. No new security be a discussion on algorithm superiority. No new security
considerations are raised in this document. considerations are raised in this document.
5. Normative References 5. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2536] Eastlake, D., "DSA KEYs and SIGs in the Domain Name System
(DNS)", RFC 2536, 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 [RFC3110] Eastlake, D., "RSA/SHA-1 SIGs and RSA KEYs in the Domain
Name System (DNS)", RFC 3110, May 2001. Name System (DNS)", RFC 3110, May 2001.
[RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "DNS Security Introduction and Requirements", Rose, "DNS Security Introduction and Requirements",
RFC 4033, March 2005. RFC 4033, March 2005.
[RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Resource Records for the DNS Security Extensions", Rose, "Resource Records for the DNS Security Extensions",
RFC 4034, March 2005. RFC 4034, March 2005.
skipping to change at page 6, line 7 skipping to change at page 5, line 43
(DS) Resource Records (RRs)", RFC 4509, May 2006. (DS) Resource Records (RRs)", RFC 4509, May 2006.
[RFC5155] Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS [RFC5155] Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS
Security (DNSSEC) Hashed Authenticated Denial of Security (DNSSEC) Hashed Authenticated Denial of
Existence", RFC 5155, March 2008. Existence", RFC 5155, March 2008.
[RFC5702] Jansen, J., "Use of SHA-2 Algorithms with RSA in DNSKEY [RFC5702] Jansen, J., "Use of SHA-2 Algorithms with RSA in DNSKEY
and RRSIG Resource Records for DNSSEC", RFC 5702, and RRSIG Resource Records for DNSSEC", RFC 5702,
October 2009. October 2009.
[RFC5933] Dolmatov, V., Chuprina, A., and I. Ustinov, "Use of GOST
Signature Algorithms in DNSKEY and RRSIG Resource Records
for DNSSEC", RFC 5933, July 2010.
[RFC6014] Hoffman, P., "Cryptographic Algorithm Identifier [RFC6014] Hoffman, P., "Cryptographic Algorithm Identifier
Allocation for DNSSEC", RFC 6014, November 2010. Allocation for DNSSEC", RFC 6014, November 2010.
Author's Address Author's Address
Scott Rose Scott Rose
NIST NIST
100 Bureau Dr. 100 Bureau Dr.
Gaithersburg, MD 20899 Gaithersburg, MD 20899
USA USA
 End of changes. 9 change blocks. 
26 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/