draft-ietf-dnsext-dnssec-alg-allocation-03.txt   rfc6014.txt 
Network Working Group P. Hoffman Internet Engineering Task Force (IETF) P. Hoffman
Internet-Draft VPN Consortium Request for Comments: 6014 VPN Consortium
Updates: 2535, 3755, 4034 March 22, 2010 Updates: 4033, 4034, 4035 November 2010
(if approved) Category: Standards Track
Intended status: Standards Track ISSN: 2070-1721
Expires: September 23, 2010
Cryptographic Algorithm Identifier Allocation for DNSSEC Cryptographic Algorithm Identifier Allocation for DNSSEC
draft-ietf-dnsext-dnssec-alg-allocation-03
Abstract Abstract
This document specifies how DNSSEC cryptographic algorithm This document specifies how DNSSEC cryptographic algorithm
identifiers in the IANA registries are allocated. It changes the identifiers in the IANA registries are allocated. It changes the
requirement from "standard required" to "RFC required". It does not requirement from "standard required" to "RFC Required". It does not
change the list of algorithms that are recommended or required for change the list of algorithms that are recommended or required for
DNSSEC implementations. DNSSEC implementations.
Status of this Memo 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 This is an Internet Standards Track document.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html. (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on September 23, 2010. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6014.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
1. Introduction 1. Introduction
[RFC2535] specifies that that IANA registry for DNS Security [RFC2535] specifies that the IANA registry for DNS Security Algorithm
Algorithm Numbers be updated by IETF Standards Action only, with the Numbers be updated by IETF Standards Action only, with the exception
exception of two values 253 and 254. In essence, this means that for of two values -- 253 and 254. In essence, this means that for an
an algorithm to get its own entry in the registry, the algorithm must algorithm to get its own entry in the registry, the algorithm must be
be defined in an RFC on the Standards Track as defined in [RFC2026]. defined in an RFC on the Standards Track as defined in [RFC2026].
The requirement from RFC 2535 is repeated in [RFC3755] and [RFC4034]. The requirement from RFC 2535 is repeated in [RFC3755] and the
combination of [RFC4033], [RFC4034], and [RFC4035].
RFC 2535 allows algorithms that are not on the Standards Track to use RFC 2535 allows algorithms that are not on the Standards Track to use
private values 253 and 254 in signatures. In each case, an private values 253 and 254 in signatures. In each case, an
unregistered private name must be included with each use of the unregistered private name must be included with each use of the
algorithm in order to differentiate different algorithms that use the algorithm in order to differentiate different algorithms that use the
value. value.
2. Requirements for Assignments in the DNS Security Algorithm Numbers 2. Requirements for Assignments in the DNS Security Algorithm Numbers
Registry Registry
skipping to change at line 105 skipping to change at page 3, line 25
able to be put on the Standards Track. Another example is that able to be put on the Standards Track. Another example is that
the algorithm might have unclear intellectual property rights that the algorithm might have unclear intellectual property rights that
prevents the algorithm from being put on the Standards Track. prevents the algorithm from being put on the Standards Track.
o Although the size of the registry is restricted (about 250 o Although the size of the registry is restricted (about 250
entries), new algorithms are proposed infrequently. It could entries), new algorithms are proposed infrequently. It could
easily be many decades before there is any reason to consider easily be many decades before there is any reason to consider
restricting the registry again. restricting the registry again.
Some developers will care about the standards level of the RFCs that Some developers will care about the standards level of the RFCs that
are in the registry. The registry should be updated to reflect the are in the registry. The registry has been updated to reflect the
current standards level of each algorithm listed. current standards level of each algorithm listed.
To address concerns about the registry eventually filling up, the To address concerns about the registry eventually filling up, the
IETF should re-evaluate the requirements for entry into this registry IETF should re-evaluate the requirements for entry into this registry
when approximately 120 of the registry entries have been assigned. when approximately 120 of the registry entries have been assigned.
That evaluation may lead to tighter restrictions or a new mechanism That evaluation may lead to tighter restrictions or a new mechanism
for extending the size of the registry. In order to make this for extending the size of the registry. In order to make this
evaluation more likely, IANA is requested to mark about half of the evaluation more likely, IANA has marked about half of the currently
currently-available entries as "Reserved" in order to make the timing available entries as "Reserved" in order to make the timing for that
for that re-evaluation more apparent. re-evaluation more apparent.
The private-use values, 253 and 254, are still useful for developers The private-use values, 253 and 254, are still useful for developers
who want to test, in private, algorithms for which there is no RFC. who want to test, in private, algorithms for which there is no RFC.
This document does not change the semantics of those two values. This document does not change the semantics of those two values.
3. Expectations For Implementations 3. Expectations for Implementations
It is important to note that, according to RFC 4034, DNSSEC It is important to note that, according to RFC 4034, DNSSEC
implementations are not expected to include all of the algorithms implementations are not expected to include all of the algorithms
listed in the IANA registry; in fact, RFC 4034 and the IANA registry listed in the IANA registry; in fact, RFC 4034 and the IANA registry
list an algorithm that implementations should not include. This list an algorithm that implementations should not include. This
document does nothing to change the expectation that there will be document does nothing to change the expectation that there will be
items listed in the IANA registry that need not be (and in some items listed in the IANA registry that need not be (and in some
cases, should not be) included in all implementations. cases, should not be) included in all implementations.
There are many reasons why a DNSSEC implementation might not include There are many reasons why a DNSSEC implementation might not include
one or more of the algorithms listed, even those on the Standards one or more of the algorithms listed, even those on the Standards
Track. In order to be compliant with the RFC 4034, an implementation Track. In order to be compliant with RFC 4034, an implementation
only needs to implement the algorithms listed as mandatory to only needs to implement the algorithms listed as mandatory to
implement in that standard, or updates to that standard. This implement in that standard, or updates to that standard. This
document does nothing to change the list of mandatory to implement document does nothing to change the list of mandatory-to-implement
algorithms in RFC 4034. This document does not change the algorithms in RFC 4034. This document does not change the
requirements for when an algorithm becomes mandatory to implement. requirements for when an algorithm becomes mandatory to implement.
Such requirements should come in a separate, focused document. Such requirements should come in a separate, focused document.
It should be noted that the order of algorithms in the IANA registry It should be noted that the order of algorithms in the IANA registry
does not signify or imply cryptographic strength or preference. does not signify or imply cryptographic strength or preference.
4. IANA Considerations 4. IANA Considerations
This document updates allocation requirements for unassigned values This document updates allocation requirements for unassigned values
in the "Domain Name System Security (DNSSEC) Algorithm Numbers" in the "Domain Name System Security (DNSSEC) Algorithm Numbers"
registry located at http://www.iana.org/assignments/ registry located at http://www.iana.org/assignments/
dns-sec-alg-numbers/dns-sec-alg-numbers.xhtml, in the sub-registry dns-sec-alg-numbers, in the sub-registry titled "DNS Security
titled "DNS Security Algorithm Numbers". The registration procedure Algorithm Numbers". The registration procedure for values that are
for values that are assigned after this document is published is "RFC assigned after this document is published is "RFC Required".
Required".
IANA is requested to mark values 123 through 251 as "Reserved". The IANA has marked values 123 through 251 as "Reserved". The registry
registry should note that this reservation is made in [[ THIS RFC ]]] notes that this reservation is made in RFC 6014 (this RFC) so that
so that when most of the unreserved values are taken, the future IANA when most of the unreserved values are taken, future users and IANA
and users will have an easy pointer to where the reservation will have a pointer to where the reservation originated and its
originated and its purpose. purpose.
IANA is requested to add a textual notation to the "References" IANA has added a textual notation to the "References" column in the
column in the registry that gives the current standards status for registry that gives the current standards status for each RFC that is
each RFC that is listed in the registry. listed in the registry.
5. Security Considerations 5. Security Considerations
An algorithm described in an RFC that is not on the Standards Track An algorithm described in an RFC that is not on the Standards Track
may have weaker security than one that is on the Standards Track; in may have weaker security than one that is on the Standards Track; in
fact, that may be the reason that the algorithm was not allowed on fact, that may be the reason that the algorithm was not allowed on
Standards Track. Note, however, that not being on the Standards Standards Track. Note, however, that not being on the Standards
Track does not necessarily mean that an algorithm is weaker. Track does not necessarily mean that an algorithm is weaker.
Conversely, algorithms that are on the Standards Track should not Conversely, algorithms that are on the Standards Track should not
necessarily be considered better than algorithms that are not on the necessarily be considered better than algorithms that are not on the
Standards Track. There are other reasons (such as intellectual Standards Track. There are other reasons (such as intellectual
property concerns) that can keep algorithms that are widely property concerns) that can keep algorithms that are widely
considered to be strong off of Standards Track. considered to be strong off the Standards Track.
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2535] Eastlake, D., "Domain Name System Security Extensions", [RFC2535] Eastlake, D., "Domain Name System Security Extensions",
RFC 2535, March 1999. RFC 2535, March 1999.
[RFC3755] Weiler, S., "Legacy Resolver Compatibility for Delegation [RFC3755] Weiler, S., "Legacy Resolver Compatibility for Delegation
Signer (DS)", RFC 3755, May 2004. Signer (DS)", RFC 3755, May 2004.
[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. [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.
[RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Protocol Modifications for the DNS Security
Extensions", RFC 4035, March 2005.
6.2. Informative References 6.2. Informative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
Appendix A. Experimental and Documentation Values Appendix A. Experimental and Documentation Values
During the early discussion of this document, it was proposed that During the early discussion of this document, it was proposed that
maybe there should be a small number of values reserved for maybe there should be a small number of values reserved for
"experimental" purposes. This proposal was not included in this "experimental" purposes. This proposal was not included in this
skipping to change at line 214 skipping to change at page 6, line 23
experimental value associated with a particular extension, experimental value associated with a particular extension,
competitors would code their systems to test interoperability, and competitors would code their systems to test interoperability, and
then no one wanted to change the values in their software to the then no one wanted to change the values in their software to the
"real" value that was later assigned. "real" value that was later assigned.
There was also a proposal that IANA should reserve two values to be There was also a proposal that IANA should reserve two values to be
used in documentation only, similar to the way that "example.com" has used in documentation only, similar to the way that "example.com" has
been reserved as a domain name. That proposal was also not included been reserved as a domain name. That proposal was also not included
in this document because all values need to be associated with some in this document because all values need to be associated with some
algorithm, and there is no problem with having examples that point to algorithm, and there is no problem with having examples that point to
commonly-deployed algorithms. commonly deployed algorithms.
Appendix B. Change History
This section is to be removed before publication as an RFC.
B.1. Differences between draft-hoffman-dnssec-alg-allocation-00 and -01
A few editorial nits that really should have been caught in the -00.
Added the section on "Expectations For Implementations" to clarify
that this document is not changing any such expectations or updating
that part of RFC 4034.
B.2. Differences between draft-hoffman-dnssec-alg-allocation-01 and
draft-ietf-dnsext-dnssec-alg-allocation-00
First WG draft.
Clarified the intent of the document in the Abstract by adding "It
does not change the list of algorithms that are recommended or
required for DNSSEC implementations".
Added to Section 3: "It should be noted that the order of algorithms
in the IANA registry does not signify or imply cryptographic strength
or preference."
B.3. Differences between draft-ietf-dnsext-dnssec-alg-allocation-00 and
draft-ietf-dnsext-dnssec-alg-allocation-01
Various editorial changes and clarifications that came during WG LC.
Asked IANA to mark values 123 through 250 as "Reserved".
In the expectations for implementers, added "This document does not
change the requirements for when an algorithm because mandatory to
implement. Such requirements should come in a separate, focused
document."
B.4. Differences between draft-ietf-dnsext-dnssec-alg-allocation-01 and
draft-ietf-dnsext-dnssec-alg-allocation-02
Reworded the first bullet in Section 2 to remove "government".
B.5. Differences between draft-ietf-dnsext-dnssec-alg-allocation-02 and
draft-ietf-dnsext-dnssec-alg-allocation-03
Changed "SHOULD" to "should" in section 2.
In section 4, changed the range of "resevered" codes from "123
through 250" to "123 through 251".
Added to the IANA Considerations: "The registry should note that this
reservation is made in [[ THIS RFC ]]] so that when most of the
unreserved values are taken, the future IANA and users will have an
easy pointer to where the reservation originated and its purpose."
Author's Address Author's Address
Paul Hoffman Paul Hoffman
VPN Consortium VPN Consortium
Email: paul.hoffman@vpnc.org EMail: paul.hoffman@vpnc.org
 End of changes. 22 change blocks. 
110 lines changed or deleted 52 lines changed or added

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