draft-schaad-curdle-oid-registry-00.txt   draft-schaad-curdle-oid-registry-01.txt 
Curdle J. Schaad Curdle J. Schaad
Internet-Draft August Cellars Internet-Draft August Cellars
Intended status: Informational R. Andrews Intended status: Informational R. Andrews
Expires: November 9, 2017 Symantec Website Security Expires: November 16, 2017 Symantec Website Security
May 8, 2017 May 15, 2017
Object Identifier Registry for the Curdle Working Group IANA Registration for Donated Symantec Website Security Object
draft-schaad-curdle-oid-registry-00 Identifier Range
draft-schaad-curdle-oid-registry-01
Abstract Abstract
When the Curdle Security Working Group was chartered, a range of When the Curdle Security Working Group was chartered, a range of
object identifiers was donated by Symantec Website Security for use object identifiers was donated by Symantec Website Security for the
by that working group. This document describes the range of purpose of registering the Edwards Elliptic Curve key agreement and
identifiers that were assigned in that donated range, transfers signature algorithms. This donated set of OIDs allowed for shorter
control of that range to IANA, and establishes IANA allocation values than would be possible using the existing S/MIME or PKIX arcs.
policies for any future assignments within that range. This document describes the range of identifiers that were assigned
in that donated range, transfers control of that range to IANA, and
establishes IANA allocation policies for any future assignments
within that range.
Contributing to this document Contributing to this document
The source for this draft is being maintained in GitHub. Suggested The source for this draft is being maintained in GitHub. Suggested
changes should be submitted as pull requests at <https://github.com/ changes should be submitted as pull requests at <https://github.com/
lamps-wg/smime>. Instructions are on that page as well. Editorial lamps-wg/smime>. Instructions are on that page as well. Editorial
changes can be managed in GitHub, but any substantial issues need to changes can be managed in GitHub, but any substantial issues need to
be discussed on the LAMPS mailing list. be discussed on the LAMPS mailing list.
Status of This Memo Status of This Memo
skipping to change at page 1, line 44 skipping to change at page 1, line 48
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 November 9, 2017. This Internet-Draft will expire on November 16, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 Simplified BSD License. described in the Simplified BSD License.
1. Introduction 1. Introduction
When the Curdle Security Working Group was chartered, a range of When the Curdle Security Working Group was chartered, a range of
object identifiers was donated by Symantec Website Security for use object identifiers was donated by Symantec Website Security for use
by that working group. These object identifiers are primarily used by that working group. The use of these object identifiers allowed
with Abstract Syntax Notation (ASN.1) [ASN.1]. The ASN.1 for the Edwards Ellitptic Curve key agreement [RFC7748] and signature
specifications continue to evolve, but object identifiers can be used [RFC8032] algorithms to be defined with encodings that are smaller
with any and all versions of ASN.1. than similar ones would be if assigned from the existing S/MIME or
PKIX arcs. These initial registrations from this arc were done while
The Curdle object identifier range is: developing [I-D.ietf-curdle-pkix]. After those registrations were
done, there were still some unused values that can be used for other
security groups, there were still some unused values.
{ iso (1) identified-organization (3) thawte (101) 100 } Object identifiers are primarily used with Abstract Syntax Notation
to (ASN.1) [ASN.1]. The ASN.1 specifications continue to evolve, but
{ iso (1) identified-organization (3) thawte (101) 127 } object identifiers can be used with any and all versions of ASN.1.
This document describes the object identifiers that were assigned in This document describes the object identifiers that were assigned in
that donated range, transfers control of the range to IANA, and that donated range, transfers control of the range to IANA, and
establishes IANA allocation policies for any future assignments establishes IANA allocation policies for any future assignments.
within that range.
The donated range from Symantec Website Security is:
first: { iso (1) identified-organization (3) thawte (101) 100 }
last: { iso (1) identified-organization (3) thawte (101) 127 }
2. IANA Considerations 2. IANA Considerations
IANA is asked to create one new registry table. IANA is asked to create one new registry table.
2.1. "SMI Security for Curdle" Registry 2.1. "SMI Security for Cryptographic Algorithms" Registry
Within the SMI-numbers registry, add an "SMI Security for Curdle" Within the SMI-numbers registry, add an "SMI Security for
table with the three columns: Cryptographic Algorithms" table with the three columns:
+---------+--------------------------------+------------------------+ +---------+-----------------------------+---------------------------+
| Decimal | Description | References | | Decimal | Description | References |
+---------+--------------------------------+------------------------+ +---------+-----------------------------+---------------------------+
| 100 | Reserved for future sub- | | | 100 | Reserved for child reg | |
| | registry | | | | | |
| | | | | 110 | id-X25519 | [I-D.ietf-curdle-pkix] |
| 110 | id-X25519 | [I-D.ietf-curdle-pkix] | | | | |
| | | | | 111 | id-X448 | [I-D.ietf-curdle-pkix] |
| 111 | id-X448 | [I-D.ietf-curdle-pkix] | | | | |
| | | | | 112 | id-EdDSA25519 | [I-D.ietf-curdle-pkix] |
| 112 | id-EdDSA25519 | [I-D.ietf-curdle-pkix] | | | | |
| | | | | 113 | id-EdDSA448 | [I-D.ietf-curdle-pkix] |
| 113 | id-EdDS448 | [I-D.ietf-curdle-pkix] | | | | |
| | | | | 114 | Reserved for id- | [I-D.ietf-curdle-pkix]-03 |
| 114 | id-EdDSA25519-ph | [I-D.ietf-curdle-pkix] | | | EdDSA25519-ph | |
| | | | | | | |
| 115 | id-EdDS448=ph | [I-D.ietf-curdle-pkix] | | 115 | Reserved for id-EdDSA448-ph | [I-D.ietf-curdle-pkix]-03 |
| | | | +---------+-----------------------------+---------------------------+
| 120 | Safecurves-pkix-0 | [I-D.ietf-curdle-pkix] |
+---------+--------------------------------+------------------------+
The column 'Decimal' is required to be a number between 100 and 127 The column 'Decimal' is required to be a number between 100 and 127
inclusive. inclusive.
The value of 100 has been reserved so that a new arc below that point
can be established in the future. (I.e. starting at 1.3.101.100.1)
If the new child registry is established, a name for this value is to
be assigned at that point. The experts can, at their discretion,
assign an algorithm OID instead.
Future updates to this table require both 'Specification Required' Future updates to this table require both 'Specification Required'
and 'Expert Review' as defiened in [RFC5226]. and 'Expert Review' as defineed in [RFC5226].
3. Security Considerations 3. Security Considerations
This document populates an IANA registry, and it raises no new This document populates an IANA registry, and it raises no new
security considerations. The protocols that specify these values security considerations. The protocols that specify these values
include the security considerations associated with their usage. include the security considerations associated with their usage.
4. References 4. References
4.1. Normative References 4.1. Normative References
[ASN.1] "Information Technology - Abstract Syntax Notation One [ASN.1] "Information Technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation. ITU-T (ASN.1): Specification of basic notation. ITU-T
Recommendation X.680 (2008)", ITU-T X.680, ISO/ Recommendation X.680 (2008)", ITU-T X.680, ISO/
IEC 8824-1:2008, November 2008. IEC 8824-1:2008, November 2008.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
skipping to change at page 4, line 13 skipping to change at page 4, line 24
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
4.2. Informational References 4.2. Informational References
[I-D.ietf-curdle-pkix] [I-D.ietf-curdle-pkix]
Josefsson, S. and J. Schaad, "Algorithm Identifiers for Josefsson, S. and J. Schaad, "Algorithm Identifiers for
Ed25519, Ed448, X25519 and X448 for use in the Internet Ed25519, Ed448, X25519 and X448 for use in the Internet
X.509 Public Key Infrastructure", draft-ietf-curdle- X.509 Public Key Infrastructure", draft-ietf-curdle-
pkix-04 (work in progress), March 2017. pkix-04 (work in progress), March 2017.
[RFC7748] Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves
for Security", RFC 7748, DOI 10.17487/RFC7748, January
2016, <http://www.rfc-editor.org/info/rfc7748>.
[RFC8032] Josefsson, S. and I. Liusvaara, "Edwards-Curve Digital
Signature Algorithm (EdDSA)", RFC 8032,
DOI 10.17487/RFC8032, January 2017,
<http://www.rfc-editor.org/info/rfc8032>.
Acknowledgments Acknowledgments
Our thanks go out to Symantec for donating the range of OIDs covered Our thanks go out to Symantec for donating the range of OIDs covered
in this document. in this document.
This document stole text heavily from a previous document doing This document stole text heavily from a previous document doing
similar thing by Russ Housely. Copying always makes things easier similar thing by Russ Housely. Copying always makes things easier
and less error prone. and less error prone.
Authors' Addresses Authors' Addresses
 End of changes. 14 change blocks. 
46 lines changed or deleted 68 lines changed or added

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