idnits 2.17.1 draft-schaad-curdle-oid-registry-03.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 (January 25, 2018) is 2275 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-10) exists of draft-ietf-curdle-pkix-07 == Outdated reference: A later version (-10) exists of draft-ietf-curdle-pkix-07 -- Duplicate reference: draft-ietf-curdle-pkix, mentioned in 'I-D.ietf-curdle-pkix-03', was also mentioned in 'I-D.ietf-curdle-pkix'. Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Curdle J. Schaad 3 Internet-Draft August Cellars 4 Intended status: Informational R. Andrews 5 Expires: July 29, 2018 DigiCert, Inc. 6 January 25, 2018 8 IANA Registration for new Cryptographic Algorithm Object Identifier 9 Range 10 draft-schaad-curdle-oid-registry-03 12 Abstract 14 When the Curdle Security Working Group was chartered, a range of 15 object identifiers was donated by DigiCert, Inc. for the purpose of 16 registering the Edwards Elliptic Curve key agreement and signature 17 algorithms. This donated set of OIDs allowed for shorter values than 18 would be possible using the existing S/MIME or PKIX arcs. This 19 document describes the range of identifiers that were assigned in 20 that donated range, transfers control of that range to IANA, and 21 establishes IANA allocation policies for any future assignments 22 within that range. 24 Contributing to this document 26 The source for this draft is being maintained in GitHub. Suggested 27 changes should be submitted as pull requests at . Instructions are on that page as well. Editorial 29 changes can be managed in GitHub, but any substantial issues need to 30 be discussed on the LAMPS mailing list. 32 Status of This Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at https://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on July 29, 2018. 49 Copyright Notice 51 Copyright (c) 2018 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (https://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 67 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 68 2.1. "SMI Security for Cryptographic Algorithms" Registry . . 3 69 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 70 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 71 4.1. Normative References . . . . . . . . . . . . . . . . . . 4 72 4.2. Informational References . . . . . . . . . . . . . . . . 4 73 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 5 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 76 1. Introduction 78 When the Curdle Security Working Group was chartered, a range of 79 object identifiers was donated by DigiCert, Inc. for use by that 80 working group. The use of these object identifiers allowed for the 81 Edwards Ellitptic Curve key agreement [RFC7748] and signature 82 [RFC8032] algorithms to be defined with encodings that are smaller 83 than similar ones would be if assigned from the existing S/MIME or 84 PKIX arcs. These initial registrations from this arc were done while 85 developing [I-D.ietf-curdle-pkix]. After those registrations were 86 done, there were still some unused values that can be used for other 87 security groups. 89 Object identifiers are primarily used with Abstract Syntax Notation 90 (ASN.1) [ASN.1]. The ASN.1 specifications continue to evolve, but 91 object identifiers can be used with any and all versions of ASN.1. 93 This document describes the object identifiers that were assigned in 94 that donated range, transfers control of the range to IANA, and 95 establishes IANA allocation policies for any future assignments. 97 The donated range from DigiCert, Inc. is: 99 first: { iso (1) identified-organization (3) thawte (101) 100 } 100 last: { iso (1) identified-organization (3) thawte (101) 127 } 102 2. IANA Considerations 104 IANA is asked to create one new registry table. 106 2.1. "SMI Security for Cryptographic Algorithms" Registry 108 Within the SMI-numbers registry, add an "SMI Security for 109 Cryptographic Algorithms" table with the three columns: 111 +-----------+---------------------------+---------------------------+ 112 | Decimal | Description | References | 113 +-----------+---------------------------+---------------------------+ 114 | 0 - 99 | Retained by Digicert | [I-D.ietf-curdle-pkix] | 115 | | | | 116 | 100 | Reserved for child reg | | 117 | | | | 118 | 110 | id-X25519 | [I-D.ietf-curdle-pkix] | 119 | | | | 120 | 111 | id-X448 | [I-D.ietf-curdle-pkix] | 121 | | | | 122 | 112 | id-EdDSA25519 | [I-D.ietf-curdle-pkix] | 123 | | | | 124 | 113 | id-EdDSA448 | [I-D.ietf-curdle-pkix] | 125 | | | | 126 | 114 | Reserved for id- | [I-D.ietf-curdle-pkix-03] | 127 | | EdDSA25519-ph | | 128 | | | | 129 | 115 | Reserved for id- | [I-D.ietf-curdle-pkix-03] | 130 | | EdDSA448-ph | | 131 | | | | 132 | 128 and | Retained by Digicert | [I-D.ietf-curdle-pkix] | 133 | up | | | 134 +-----------+---------------------------+---------------------------+ 136 The column 'Decimal' is required to be a number between 100 and 127 137 inclusive. 139 The value of 100 has been reserved so that a new arc below that point 140 can be established in the future. (I.e. starting at 1.3.101.100.1) 141 If the new child registry is established, a name for this value is to 142 be assigned at that point. The experts can, at their discretion, 143 assign an algorithm OID instead. 145 The registry is to be created using the "Specification Required" 146 policy as defined in [RFC8126]. 148 3. Security Considerations 150 This document populates an IANA registry, and it raises no new 151 security considerations. The protocols that specify these values 152 include the security considerations associated with their usage. 154 4. References 156 4.1. Normative References 158 [ASN.1] "Information Technology - Abstract Syntax Notation One 159 (ASN.1): Specification of basic notation. ITU-T 160 Recommendation X.680 (2008)", ITU-T X.680, ISO/ 161 IEC 8824-1:2008, November 2008. 163 4.2. Informational References 165 [I-D.ietf-curdle-pkix] 166 Josefsson, S. and J. Schaad, "Algorithm Identifiers for 167 Ed25519, Ed448, X25519 and X448 for use in the Internet 168 X.509 Public Key Infrastructure", draft-ietf-curdle- 169 pkix-07 (work in progress), November 2017. 171 [I-D.ietf-curdle-pkix-03] 172 Josefsson, S. and J. Schaad, "Algorithm Identifiers for 173 Ed25519, Ed448, X25519 and X448 for use in the Internet 174 X.509 Public Key Infrastructure", draft-ietf-curdle- 175 pkix-07 (work in progress), November 2016. 177 [RFC7748] Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves 178 for Security", RFC 7748, DOI 10.17487/RFC7748, January 179 2016, . 181 [RFC8032] Josefsson, S. and I. Liusvaara, "Edwards-Curve Digital 182 Signature Algorithm (EdDSA)", RFC 8032, 183 DOI 10.17487/RFC8032, January 2017, 184 . 186 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 187 Writing an IANA Considerations Section in RFCs", BCP 26, 188 RFC 8126, DOI 10.17487/RFC8126, June 2017, 189 . 191 Acknowledgments 193 Our thanks go out to DigiCert for donating the range of OIDs covered 194 in this document. At the time of the donation, the root of the range 195 was assigned to Symantec but has sense been transfered DigiCert. 197 This document uses a lot of text from a similar document by Russ 198 Housley. Copying always makes things easier and less error prone. 200 Authors' Addresses 202 Jim Schaad 203 August Cellars 205 Email: ietf@augustcellars.com 207 Rick Andrews 208 DigiCert, Inc. 210 Email: rick.andrews@digicert.com