-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathdraft-schaad-curdle-oid-registry.xml
187 lines (162 loc) · 8.37 KB
/
draft-schaad-curdle-oid-registry.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
<?xml version='1.0' encoding='US-ASCII'?>
<!DOCTYPE rfc SYSTEM "../xml2rc-1.36/rfc2629.dtd" [
<!ENTITY RFC7748 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7748.xml">
<!ENTITY RFC8032 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8032.xml">
<!ENTITY RFC8126 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8126.xml">
<!ENTITY CURDLE SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-curdle-pkix.xml">
]>
<?rfc symrefs="yes"?>
<?rfc sortrefs='yes'?>
<?rfc toc='yes'?>
<rfc docName="draft-schaad-curdle-oid-registry-03" category="info">
<front>
<title abbrev="OID Registry">IANA Registration for new Cryptographic Algorithm Object Identifier Range</title>
<author fullname="Jim Schaad" initials="J." surname="Schaad">
<organization>August Cellars</organization>
<address>
<email>[email protected]</email>
</address>
</author>
<author fullname="Rick Andrews" initials="R." surname="Andrews">
<organization>DigiCert, Inc.</organization>
<address>
<email>[email protected]</email>
</address>
</author>
<date/>
<area>Security Area</area>
<workgroup>Curdle</workgroup>
<abstract>
<t>
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 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.
</t>
</abstract>
<note title="Contributing to this document">
<!-- RFC EDITOR - Please remove this note before publishing -->
<t>
The source for this draft is being maintained in GitHub.
Suggested changes should be submitted as pull requests at <eref target="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.
</t>
</note>
</front>
<middle>
<section title="Introduction">
<t>
When the Curdle Security Working Group was chartered, a range of object identifiers was donated by DigiCert, Inc. for use by that working group.
The use of these object identifiers allowed for the Edwards Ellitptic Curve key agreement <xref target="RFC7748"/> and signature <xref target="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.
These initial registrations from this arc were done while developing <xref target="I-D.ietf-curdle-pkix"/>.
After those registrations were done, there were still some unused values that can be used for other security groups.
</t>
<t>
Object identifiers are primarily used with Abstract Syntax Notation (ASN.1) <xref target="ASN.1"/>.
The ASN.1 specifications continue to evolve, but object identifiers can be used with any and all versions of ASN.1.
</t>
<t>
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.
</t>
<t>
The donated range from DigiCert, Inc. is:
<figure>
<artwork>
first: { iso (1) identified-organization (3) thawte (101) 100 }
last: { iso (1) identified-organization (3) thawte (101) 127 }
</artwork>
</figure>
</t>
</section>
<section title="IANA Considerations">
<t>
IANA is asked to create one new registry table.
</t>
<section title='"SMI Security for Cryptographic Algorithms" Registry'>
<t>
Within the SMI-numbers registry, add an "SMI Security for Cryptographic Algorithms" table with the three columns:
</t>
<!-- FOR IANA - Please place on the SMI Numbers page under the SMI Security Codes section -->
<texttable>
<ttcol>Decimal</ttcol><ttcol>Description</ttcol><ttcol>References</ttcol>
<c>0 - 99</c><c>Retained by Digicert</c><c><xref target="I-D.ietf-curdle-pkix"/></c>
<c>100</c><c>Reserved for child reg</c><c/>
<c>110</c><c>id-X25519</c><c><xref target="I-D.ietf-curdle-pkix"/></c>
<c>111</c><c>id-X448</c><c><xref target="I-D.ietf-curdle-pkix"/></c>
<c>112</c><c>id-EdDSA25519</c><c><xref target="I-D.ietf-curdle-pkix"/></c>
<c>113</c><c>id-EdDSA448</c><c><xref target="I-D.ietf-curdle-pkix"/></c>
<!-- rfc-editor The next two items are in -03 of the draft and not in the final version, please adjust the reference accordingly. -->
<c>114</c><c>Reserved for id-EdDSA25519-ph</c><c><xref target="I-D.ietf-curdle-pkix-03"/></c>
<c>115</c><c>Reserved for id-EdDSA448-ph</c><c><xref target="I-D.ietf-curdle-pkix-03"/></c>
<c>128 and up</c><c>Retained by Digicert</c><c><xref target="I-D.ietf-curdle-pkix"/></c>
</texttable>
<t>
The column 'Decimal' is required to be a number between 100 and 127 inclusive.
</t>
<t>
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.
</t>
<t>
The registry is to be created using the "Specification Required" policy as defined in <xref target="RFC8126"/>.
</t>
</section>
</section>
<section title="Security Considerations">
<t>
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.
</t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="ASN.1">
<front>
<title>Information Technology - Abstract Syntax
Notation One (ASN.1): Specification of basic notation.
ITU-T Recommendation X.680 (2008)
</title>
<author/>
<date month="November" year="2008"/>
</front>
<seriesInfo name="ITU-T" value="X.680"/>
<seriesInfo name="ISO/IEC" value="8824-1:2008"/>
</reference>
</references>
<references title="Informational References">
&RFC7748;
&RFC8032;
&RFC8126;
&CURDLE;
<reference anchor='I-D.ietf-curdle-pkix-03'>
<front>
<title>Algorithm Identifiers for Ed25519, Ed448, X25519 and X448 for use in the Internet X.509 Public Key Infrastructure</title>
<author initials='S' surname='Josefsson' fullname='Simon Josefsson'>
<organization />
</author>
<author initials='J' surname='Schaad' fullname='Jim Schaad'>
<organization />
</author>
<date month='November' day='23' year='2016' />
<abstract><t>This document specifies algorithm identifiers and ASN.1 encoding formats for Elliptic Curve constructs using the curve25519 and curve448 curves. The signature algorithms covered are Ed25519 and Ed448. The key agreement algorithm covered are X25519 and X448. The encoding for Public Key, Private Key and EdDSA digital signature structures is provided.</t></abstract>
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-curdle-pkix-07' />
<format type='TXT'
target='http://www.ietf.org/internet-drafts/draft-ietf-curdle-pkix-07.txt' />
</reference>
</references>
<section title="Acknowledgments" numbered="no">
<t>
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 has sense been transfered DigiCert.
</t>
<t>
This document uses a lot of text from a similar document by Russ Housley.
Copying always makes things easier and less error prone.
</t>
</section>
</back>
</rfc>