CurdleInternet Engineering Task Force (IETF) J. SchaadInternet-DraftRequest for Comments: 8411 August CellarsIntended status:Category: Informational R. AndrewsExpires: July 29, 2018ISSN: 2070-1721 DigiCert, Inc.January 25,June 2018 IANA Registration fornewthe Cryptographic Algorithm Object Identifier Rangedraft-schaad-curdle-oid-registry-03Abstract When the Curdle Security Working Group was chartered, a range of object identifiers was donated by DigiCert, Inc. for the purpose of registering the Edwards Elliptic Curve key agreement and signature algorithms. This donated set of OIDs allowed for shorter values than would be possible using the existing S/MIME or PKIX arcs. This document describes the donated rangeofand the identifiers that were assignedinfrom thatdonatedrange, transfers control of that range to IANA, and establishes IANA allocation policies for any future assignments within that range.Contributing to this document The source for this draft is being maintained in GitHub. Suggested changes should be submitted as pull requests at <https://github.com/ lamps-wg/smime>. Instructions are on that page as well. Editorial changes can be managed in GitHub, but any substantial issues need to be discussed on the LAMPS mailing list.Status of This Memo ThisInternet-Draftdocument issubmitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documentsnot an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF).Note that other groups may also distribute working documents as Internet-Drafts. The listIt represents the consensus ofcurrent Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draftthe IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documentsvalidapproved by the IESG are candidates fora maximumany level of Internet Standard; see Section 2 of RFC 7841. Information about the current status ofsix monthsthis document, any errata, and how to provide feedback on it may beupdated, replaced, or obsoleted by other documentsobtained atany time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on July 29, 2018.https://www.rfc-editor.org/info/rfc8411. Copyright Notice Copyright (c) 2018 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 Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . .3 2.1. "SMI Security for Cryptographic Algorithms" Registry . . 32 3. Security Considerations . . . . . . . . . . . . . . . . . . .43 4. References . . . . . . . . . . . . . . . . . . . . . . . . .43 4.1. Normative References . . . . . . . . . . . . . . . . . .43 4.2.InformationalInformative References . . . . . . . . . . . . . . . .4. 3 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .54 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . .54 1. Introduction When the Curdle Security Working Group was chartered, a range of object identifiers was donated to the working group by DigiCert, Inc.for use by that working group.The use of these object identifiers allowed for the EdwardsEllitpticElliptic Curve key agreement [RFC7748] and signature [RFC8032] algorithms to be defined with encodings that are smaller than similar ones would be if assigned from the existing S/MIME or PKIX arcs.TheseThe initial registrations from this arc weredonemade while developing[I-D.ietf-curdle-pkix].[RFC8410]. After those registrations weredone,made, there were still some unused values thatcancould be usedforby other security groups. Object identifiers are primarily used with Abstract Syntax Notation (ASN.1) [ASN.1]. The ASN.1 specifications continue to evolve, but object identifiers can be used with any and all versions of ASN.1. This document describes the object identifiers that were assigned in that donated range, transfers control of the range to IANA, and establishes IANA allocation policies for any future assignments. The donated range from DigiCert, Inc.is:is as follows: first: { iso (1) identified-organization (3) thawte (101) 100 } last: { iso (1) identified-organization (3) thawte (101) 127 } 2. IANA Considerations IANAis asked to create one new registry table. 2.1. "SMI Security for Cryptographic Algorithms" Registry Withinhas created theSMI-numbers registry, add an"SMI Security for Cryptographic Algorithms"table withregistry within the SMI-numbers registry. The new registry has threecolumns: +-----------+---------------------------+---------------------------+columns, as shown below. +------------+-------------------------------+-----------------+ | Decimal | Description | References |+-----------+---------------------------+---------------------------++------------+-------------------------------+-----------------+ |0 - 990-99 | Retained byDigicert | [I-D.ietf-curdle-pkix] | | |DigiCert | RFC 8411 | | 100 | Reserved for child reg || | | |RFC 8411 | | 110 | id-X25519 |[I-D.ietf-curdle-pkix] | | | |[RFC8410] | | 111 | id-X448 |[I-D.ietf-curdle-pkix] | | | |[RFC8410] | | 112 | id-EdDSA25519 |[I-D.ietf-curdle-pkix] | | | |[RFC8410] | | 113 | id-EdDSA448 |[I-D.ietf-curdle-pkix] | | | |[RFC8410] | | 114 | Reserved forid- | [I-D.ietf-curdle-pkix-03] | | | EdDSA25519-ph | | | |id-EdDSA25519-ph | [SAFE-X.509-03] | | 115 | Reserved forid- | [I-D.ietf-curdle-pkix-03] | | | EdDSA448-ph | | | |id-EdDSA448-ph | [SAFE-X.509-03] | | 128 and up | Retained byDigicert | [I-D.ietf-curdle-pkix] | | up |DigiCert | RFC 8411 |+-----------+---------------------------+---------------------------++------------+-------------------------------+-----------------+ Table 1: SMI Security for Cryptographic Algorithms The registration policy is "Specification Required" as defined in [RFC8126]. The column 'Decimal' is required to be a number between 100 and 127 inclusive. The value of 100 has been reserved so that a new arc below that point can be established in thefuture. (I.e.future (i.e., starting at1.3.101.100.1)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.The registry is to be created using the "Specification Required" policy as defined in [RFC8126].3. Security Considerations This document populates an IANA registry, and it raises no new security considerations. The protocols that specify these values include the security considerations associated with their usage. 4. References 4.1. Normative References [ASN.1] ITU-T, "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basicnotation.notation", ITU-T RecommendationX.680 (2008)", ITU-TX.680,ISO/ IEC 8824-1:2008, November 2008.ISO/IEC 8824-1, August 2015. 4.2.InformationalInformative References[I-D.ietf-curdle-pkix] Josefsson, S. and J. Schaad, "Algorithm Identifiers for Ed25519, Ed448, X25519 and X448 for use in the Internet X.509 Public Key Infrastructure", draft-ietf-curdle- pkix-07 (work in progress), November 2017. [I-D.ietf-curdle-pkix-03] Josefsson, S. and J. Schaad, "Algorithm Identifiers for Ed25519, Ed448, X25519 and X448 for use in the Internet X.509 Public Key Infrastructure", draft-ietf-curdle- pkix-07 (work in progress), November 2016.[RFC7748] Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves for Security", RFC 7748, DOI 10.17487/RFC7748, January 2016, <https://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, <https://www.rfc-editor.org/info/rfc8032>. [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, <https://www.rfc-editor.org/info/rfc8126>. [RFC8410] Josefsson, S. and J. Schaad, "Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure", RFC 8410, DOI 10.17487/RFC8410, June 2018. [SAFE-X.509-03] Josefsson, S. and J. Schaad, "Algorithm Identifiers for Ed25519, Ed448, X25519 and X448 for use in the Internet X.509 Public Key Infrastructure", Work in Progress, draft- ietf-curdle-pkix-03, November 2016. Acknowledgments Our thanks go out to DigiCert for donating the range of OIDs covered in this document. At the time of the donation, the root of the range was assigned to Symantec but hassensesince beentransferedtransferred to DigiCert. This document uses a lot of text from a similar document by Russ Housley. Copying always makes things easier and less error prone. Authors' Addresses Jim Schaad August Cellars Email: ietf@augustcellars.com Rick Andrews DigiCert, Inc. Email: rick.andrews@digicert.com