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
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
|
<pre>Internet Engineering Task Force (IETF) G. Huston
Request for Comments: 7935 G. Michaelson, Ed.
Obsoletes: <a href="./rfc6485">6485</a> APNIC
Category: Standards Track August 2016
ISSN: 2070-1721
<span class="h1">The Profile for Algorithms and Key Sizes</span>
<span class="h1">for Use in the Resource Public Key Infrastructure</span>
Abstract
This document specifies the algorithms, algorithms' parameters,
asymmetric key formats, asymmetric key size, and signature format for
the Resource Public Key Infrastructure (RPKI) subscribers that
generate digital signatures on certificates, Certificate Revocation
Lists (CRLs), Cryptographic Message Syntax (CMS) signed objects and
certification requests as well as for the relying parties (RPs) that
verify these digital signatures.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(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 <a href="./rfc7841#section-2">Section 2 of
RFC 7841</a>.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7935">http://www.rfc-editor.org/info/rfc7935</a>.
<span class="grey">Huston & Michaelson Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7935">RFC 7935</a> RPKI Algorithm Profile August 2016</span>
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. Asymmetric Key Pair Formats . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Public Key Format . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.2">3.2</a>. Private Key Format . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4">4</a>. Signature Format . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-5">5</a>. Additional Requirements . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-7">7</a>. Changes Applied to <a href="./rfc6485">RFC 6485</a> . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<span class="grey">Huston & Michaelson Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7935">RFC 7935</a> RPKI Algorithm Profile August 2016</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document specifies:
* the digital signature algorithm and parameters;
* the hash algorithm and parameters;
* the public and private key formats; and,
* the signature format
used by Resource Public Key Infrastructure (RPKI) [<a href="./rfc6480" title=""An Infrastructure to Support Secure Internet Routing"">RFC6480</a>]
subscribers when they apply digital signatures to certificates and
Certificate Revocation Lists (CRLs) [<a href="./rfc5280" title=""Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC5280</a>], Cryptographic Message
Syntax (CMS) signed objects [<a href="./rfc5652" title=""Cryptographic Message Syntax (CMS)"">RFC5652</a>] (e.g., Route Origin
Authorizations (ROAs) [<a href="./rfc6482" title=""A Profile for Route Origin Authorizations (ROAs)"">RFC6482</a>] and manifests [<a href="./rfc6486" title=""Manifests for the Resource Public Key Infrastructure (RPKI)"">RFC6486</a>]), and
certification requests [<a href="./rfc2986" title=""PKCS #10: Certification Request Syntax Specification Version 1.7"">RFC2986</a>] [<a href="./rfc4211" title=""Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)"">RFC4211</a>]. Relying parties (RPs)
also use the algorithms defined in this document to verify RPKI
subscribers' digital signatures [<a href="./rfc6480" title=""An Infrastructure to Support Secure Internet Routing"">RFC6480</a>].
The RPKI profiles and specification documents that reference <a href="./rfc6485">RFC 6485</a>
now refer to this document; these documents include the RPKI
Certificate Policy (CP) [<a href="./rfc6484" title=""Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI)"">RFC6484</a>], the RPKI Certificate Profile
[<a href="./rfc6487" title=""A Profile for X.509 PKIX Resource Certificates"">RFC6487</a>], the RPKI Architecture [<a href="./rfc6480" title=""An Infrastructure to Support Secure Internet Routing"">RFC6480</a>], and the Signed Object
Template for the RPKI [<a href="./rfc6488" title=""Signed Object Template for the Resource Public Key Infrastructure (RPKI)"">RFC6488</a>]. Familiarity with these documents is
assumed.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Algorithms</span>
Two cryptographic algorithms are used in the RPKI:
* The signature algorithm used in certificates, CRLs, CMS signed
objects, and certification requests is RSA Public-Key
Cryptography Standards (PKCS) #1 Version 1.5 (sometimes
referred to as "RSASSA-PKCS1-v1_5") from <a href="./rfc3447#section-8.2">Section 8.2 of
[RFC3447]</a>.
<span class="grey">Huston & Michaelson Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7935">RFC 7935</a> RPKI Algorithm Profile August 2016</span>
* The hashing algorithm used in certificates, CRLs, CMS signed
objects and certification requests is SHA-256 [<a href="#ref-SHS" title=""FIPS Publication 180-3: Secure Hash Standard"">SHS</a>] (see note
below).
NOTE: The exception is the use of SHA-1 [<a href="#ref-SHS" title=""FIPS Publication 180-3: Secure Hash Standard"">SHS</a>] when CAs generate
authority and subject key identifiers [<a href="./rfc6487" title=""A Profile for X.509 PKIX Resource Certificates"">RFC6487</a>].
In certificates, CRLs, and certification requests the hashing and
digital signature algorithms are identified together, i.e., "RSA
PKCS #1 v1.5 with SHA-256" or more simply "RSA with SHA-256". The
Object Identifier (OID) sha256WithRSAEncryption from [<a href="./rfc4055" title=""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC4055</a>] MUST
be used in these products.
The OID is in the following locations:
In the certificate, the OID appears in the signature and
signatureAlgorithm fields [<a href="./rfc4055" title=""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC4055</a>].
In the CRL, the OID appears in the signatureAlgorithm field
[<a href="./rfc4055" title=""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC4055</a>].
In a certification request, the OID appears in the PKCS #10
signatureAlgorithm field [<a href="./rfc2986" title=""PKCS #10: Certification Request Syntax Specification Version 1.7"">RFC2986</a>], or in the Certificate Request
Message Format (CRMF) POPOSigningKey algorithmIdentifier field
[<a href="./rfc4211" title=""Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)"">RFC4211</a>].
In CMS SignedData, the hashing (message digest) and digital signature
algorithms are identified separately. The object identifier and
parameters for SHA-256 (as defined in [<a href="./rfc5754" title=""Using SHA2 Algorithms with Cryptographic Message Syntax"">RFC5754</a>]) MUST be used for the
SignedData digestAlgorithms field and the SignerInfo digestAlgorithm
field. The object identifier and parameters for rsaEncryption
[<a href="./rfc3370" title=""Cryptographic Message Syntax (CMS) Algorithms"">RFC3370</a>] MUST be used for the SignerInfo signatureAlgorithm field
when generating CMS SignedData objects. RPKI implementations MUST
accept either rsaEncryption or sha256WithRSAEncryption for the
SignerInfo signatureAlgorithm field when verifying CMS SignedData
objects (for compatibility with objects produced by implementations
conforming to [<a href="./rfc6485" title=""The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure (RPKI)"">RFC6485</a>]).
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Asymmetric Key Pair Formats</span>
The RSA key pairs used to compute the signatures MUST have a 2048-bit
modulus and a public exponent (e) of 65,537.
<span class="grey">Huston & Michaelson Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7935">RFC 7935</a> RPKI Algorithm Profile August 2016</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Public Key Format</span>
The subject's public key is included in subjectPublicKeyInfo
[<a href="./rfc5280" title=""Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC5280</a>]. It has two sub-fields: algorithm and subjectPublicKey.
The values for the structures and their sub-structures follow:
algorithm (which is an AlgorithmIdentifier type):
The object identifier for RSA PKCS #1 v1.5 with SHA-256 MUST be
used in the algorithm field, as specified in <a href="./rfc4055#section-5">Section 5 of
[RFC4055]</a>. The value for the associated parameters from that
clause MUST also be used for the parameters field.
subjectPublicKey:
RSAPublicKey MUST be used to encode the certificate's
subjectPublicKey field, as specified in [<a href="./rfc4055" title=""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC4055</a>].
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Private Key Format</span>
Local policy determines the private key format.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Signature Format</span>
The structure for the certificate's signature field is as specified
in <a href="./rfc4055#section-1.2">Section 1.2 of [RFC4055]</a>. The structure for the signature field
in the CMS SignedData's SignerInfos is as specified in [<a href="./rfc5652" title=""Cryptographic Message Syntax (CMS)"">RFC5652</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Additional Requirements</span>
It is anticipated that the RPKI will require the adoption of updated
key sizes and a different set of signature and hash algorithms over
time, in order to maintain an acceptable level of cryptographic
security to protect the integrity of signed products in the RPKI.
This profile should be replaced to specify such future requirements,
as and when appropriate.
The procedures to implement such a transition of key sizes and
algorithms are specified in [<a href="./rfc6916" title=""Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)"">RFC6916</a>].
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
The Security Considerations of [<a href="./rfc4055" title=""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC4055</a>], [<a href="./rfc5280" title=""Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC5280</a>], and [<a href="./rfc6487" title=""A Profile for X.509 PKIX Resource Certificates"">RFC6487</a>]
apply to certificates and CRLs. The Security Considerations of
[<a href="./rfc2986" title=""PKCS #10: Certification Request Syntax Specification Version 1.7"">RFC2986</a>], [<a href="./rfc4211" title=""Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)"">RFC4211</a>], and [<a href="./rfc6487" title=""A Profile for X.509 PKIX Resource Certificates"">RFC6487</a>] apply to certification requests.
The Security Considerations of [<a href="./rfc5754" title=""Using SHA2 Algorithms with Cryptographic Message Syntax"">RFC5754</a>] apply to CMS signed objects.
No new security threats are introduced as a result of this
specification.
<span class="grey">Huston & Michaelson Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7935">RFC 7935</a> RPKI Algorithm Profile August 2016</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Changes Applied to <a href="./rfc6485">RFC 6485</a></span>
This update includes a slight technical change to [<a href="./rfc6485" title=""The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure (RPKI)"">RFC6485</a>] that is
considered to be outside the limited scope of an erratum. The
document update process has included other errata and also corrected
a number of nits.
<a href="./rfc6485#section-2">Section 2 of [RFC6485]</a> specified sha256WithRSAEncryption as the OID
to use for the SignerInfo signatureAlgorithm field in CMS
SignedObjects. However, existing implementations use the
rsaEncryption OID for this field. (Support for rsaEncryption in
third-party cryptographic libraries is better than
sha256WithRSAEncryption, perhaps because [<a href="./rfc3370" title=""Cryptographic Message Syntax (CMS) Algorithms"">RFC3370</a>] says that support
for rsaEncryption is required, while support for OIDs that specify
both RSA and a digest algorithm is optional.)
Rather than force existing implementations to switch to
sha256WithRSAEncryption, this document was changed to follow existing
practice. This does not represent a cryptographic algorithm change,
just an identifier change. (Unlike certificates, CRLs, and
certification requests, CMS signed objects have a separate algorithm
identifier field for the hash (digest) algorithm, and that field is
already required to contain the id-sha256 OID per <a href="#section-2">Section 2</a>.)
To avoid compatibility problems, RPs are still required to accept
sha256WithRSAEncryption if encountered.
Other changes include:
* Minor wording and typo fixes.
* Corrections to references ([<a href="./rfc5652" title=""Cryptographic Message Syntax (CMS)"">RFC5652</a>] instead of [<a href="./rfc3370" title=""Cryptographic Message Syntax (CMS) Algorithms"">RFC3370</a>],
[<a href="./rfc3447" title=""Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1"">RFC3447</a>] instead of [<a href="./rfc4055" title=""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC4055</a>]).
* Additional citations included in the Introduction.
* Correction to the CRMF POPOSigningKey field that is mentioned
in <a href="#section-2">Section 2</a> (algorithmIdentifier instead of signature).
* Inclusion of certification requests in mentions of
certificates, CRLs, and CMS signed objects.
* Replacement of text in <a href="#section-5">Section 5</a> with a pointer to the
procedures specified in [<a href="./rfc6916" title=""Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)"">RFC6916</a>] (algorithm agility).
* Replacement of "signed object" with "CMS signed object"
everywhere.
<span class="grey">Huston & Michaelson Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7935">RFC 7935</a> RPKI Algorithm Profile August 2016</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC2986">RFC2986</a>] Nystrom, M. and B. Kaliski, "PKCS #10: Certification
Request Syntax Specification Version 1.7", <a href="./rfc2986">RFC 2986</a>,
DOI 10.17487/RFC2986, November 2000,
<<a href="http://www.rfc-editor.org/info/rfc2986">http://www.rfc-editor.org/info/rfc2986</a>>.
[<a id="ref-RFC3370">RFC3370</a>] Housley, R., "Cryptographic Message Syntax (CMS)
Algorithms", <a href="./rfc3370">RFC 3370</a>, DOI 10.17487/RFC3370, August 2002,
<<a href="http://www.rfc-editor.org/info/rfc3370">http://www.rfc-editor.org/info/rfc3370</a>>.
[<a id="ref-RFC3447">RFC3447</a>] Jonsson, J. and B. Kaliski, "Public-Key Cryptography
Standards (PKCS) #1: RSA Cryptography Specifications
Version 2.1", <a href="./rfc3447">RFC 3447</a>, DOI 10.17487/RFC3447, February
2003, <<a href="http://www.rfc-editor.org/info/rfc3447">http://www.rfc-editor.org/info/rfc3447</a>>.
[<a id="ref-RFC4055">RFC4055</a>] Schaad, J., Kaliski, B., and R. Housley, "Additional
Algorithms and Identifiers for RSA Cryptography for use in
the Internet X.509 Public Key Infrastructure Certificate
and Certificate Revocation List (CRL) Profile", <a href="./rfc4055">RFC 4055</a>,
DOI 10.17487/RFC4055, June 2005,
<<a href="http://www.rfc-editor.org/info/rfc4055">http://www.rfc-editor.org/info/rfc4055</a>>.
[<a id="ref-RFC4211">RFC4211</a>] Schaad, J., "Internet X.509 Public Key Infrastructure
Certificate Request Message Format (CRMF)", <a href="./rfc4211">RFC 4211</a>,
DOI 10.17487/RFC4211, September 2005,
<<a href="http://www.rfc-editor.org/info/rfc4211">http://www.rfc-editor.org/info/rfc4211</a>>.
[<a id="ref-RFC5280">RFC5280</a>] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", <a href="./rfc5280">RFC 5280</a>, DOI 10.17487/RFC5280, May 2008,
<<a href="http://www.rfc-editor.org/info/rfc5280">http://www.rfc-editor.org/info/rfc5280</a>>.
[<a id="ref-RFC5652">RFC5652</a>] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70,
<a href="./rfc5652">RFC 5652</a>, DOI 10.17487/RFC5652, September 2009,
<<a href="http://www.rfc-editor.org/info/rfc5652">http://www.rfc-editor.org/info/rfc5652</a>>.
[<a id="ref-RFC5754">RFC5754</a>] Turner, S., "Using SHA2 Algorithms with Cryptographic
Message Syntax", <a href="./rfc5754">RFC 5754</a>, DOI 10.17487/RFC5754, January
2010, <<a href="http://www.rfc-editor.org/info/rfc5754">http://www.rfc-editor.org/info/rfc5754</a>>.
<span class="grey">Huston & Michaelson Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7935">RFC 7935</a> RPKI Algorithm Profile August 2016</span>
[<a id="ref-RFC6480">RFC6480</a>] Lepinski, M. and S. Kent, "An Infrastructure to Support
Secure Internet Routing", <a href="./rfc6480">RFC 6480</a>, DOI 10.17487/RFC6480,
February 2012, <<a href="http://www.rfc-editor.org/info/rfc6480">http://www.rfc-editor.org/info/rfc6480</a>>.
[<a id="ref-RFC6484">RFC6484</a>] Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate
Policy (CP) for the Resource Public Key Infrastructure
(RPKI)", <a href="https://www.rfc-editor.org/bcp/bcp173">BCP 173</a>, <a href="./rfc6484">RFC 6484</a>, DOI 10.17487/RFC6484, February
2012, <<a href="http://www.rfc-editor.org/info/rfc6484">http://www.rfc-editor.org/info/rfc6484</a>>.
[<a id="ref-RFC6487">RFC6487</a>] Huston, G., Michaelson, G., and R. Loomans, "A Profile for
X.509 PKIX Resource Certificates", <a href="./rfc6487">RFC 6487</a>,
DOI 10.17487/RFC6487, February 2012,
<<a href="http://www.rfc-editor.org/info/rfc6487">http://www.rfc-editor.org/info/rfc6487</a>>.
[<a id="ref-RFC6488">RFC6488</a>] Lepinski, M., Chi, A., and S. Kent, "Signed Object
Template for the Resource Public Key Infrastructure
(RPKI)", <a href="./rfc6488">RFC 6488</a>, DOI 10.17487/RFC6488, February 2012,
<<a href="http://www.rfc-editor.org/info/rfc6488">http://www.rfc-editor.org/info/rfc6488</a>>.
[<a id="ref-SHS">SHS</a>] National Institute of Standards and Technology (NIST),
"FIPS Publication 180-3: Secure Hash Standard", FIPS
Publication 180-3, October 2008.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-RFC6482">RFC6482</a>] Lepinski, M., Kent, S., and D. Kong, "A Profile for Route
Origin Authorizations (ROAs)", <a href="./rfc6482">RFC 6482</a>,
DOI 10.17487/RFC6482, February 2012,
<<a href="http://www.rfc-editor.org/info/rfc6482">http://www.rfc-editor.org/info/rfc6482</a>>.
[<a id="ref-RFC6485">RFC6485</a>] Huston, G., "The Profile for Algorithms and Key Sizes for
Use in the Resource Public Key Infrastructure (RPKI)",
<a href="./rfc6485">RFC 6485</a>, DOI 10.17487/RFC6485, February 2012,
<<a href="http://www.rfc-editor.org/info/rfc6485">http://www.rfc-editor.org/info/rfc6485</a>>.
[<a id="ref-RFC6486">RFC6486</a>] Austein, R., Huston, G., Kent, S., and M. Lepinski,
"Manifests for the Resource Public Key Infrastructure
(RPKI)", <a href="./rfc6486">RFC 6486</a>, DOI 10.17487/RFC6486, February 2012,
<<a href="http://www.rfc-editor.org/info/rfc6486">http://www.rfc-editor.org/info/rfc6486</a>>.
[<a id="ref-RFC6916">RFC6916</a>] Gagliano, R., Kent, S., and S. Turner, "Algorithm Agility
Procedure for the Resource Public Key Infrastructure
(RPKI)", <a href="https://www.rfc-editor.org/bcp/bcp182">BCP 182</a>, <a href="./rfc6916">RFC 6916</a>, DOI 10.17487/RFC6916, April
2013, <<a href="http://www.rfc-editor.org/info/rfc6916">http://www.rfc-editor.org/info/rfc6916</a>>.
<span class="grey">Huston & Michaelson Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7935">RFC 7935</a> RPKI Algorithm Profile August 2016</span>
Acknowledgments
The authors acknowledge the reuse in this document of material
originally contained in working drafts of the RPKI Certificate Policy
[<a href="./rfc6484" title=""Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI)"">RFC6484</a>] and resource certificate profile [<a href="./rfc6487" title=""A Profile for X.509 PKIX Resource Certificates"">RFC6487</a>] documents. The
coauthors of these two documents -- namely, Stephen Kent, Derrick
Kong, Karen Seo, Ronald Watro, George Michaelson, and Robert Loomans
-- are acknowledged, with thanks. The constraint on key size noted
in this profile is the outcome of comments from Stephen Kent and
review comments from David Cooper. Sean Turner has provided
additional review input to this document.
Andrew Chi and David Mandelberg discovered the issue addressed in
this replacement of [<a href="./rfc6485" title=""The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure (RPKI)"">RFC6485</a>], and the changes in this updated
specification reflect the outcome of a discussion between Rob Austein
and Matt Lepinski on the SIDR Working group mailing list. Richard
Hansen contributed a significant number of suggestions that have been
incorporated into this document.
Authors' Addresses
Geoff Huston
APNIC
Email: gih@apnic.net
George Michaelson (editor)
APNIC
Email: ggm@apnic.net
Huston & Michaelson Standards Track [Page 9]
</pre>
|
