forked from pintoniluca/miiogp
-
Notifications
You must be signed in to change notification settings - Fork 1
/
rfc5208.html
675 lines (420 loc) · 25.1 KB
/
rfc5208.html
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
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
<!DOCTYPE html>
<!-- saved from url=(0055)https://datatracker.ietf.org/doc/html/rfc5208#section-5 -->
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<title>
rfc5208
</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<style>
@media only screen
and (min-width: 992px)
and (max-width: 1199px) {
body { font-size: 14pt; }
div.content { width: 96ex; margin: 0 auto; }
}
@media only screen
and (min-width: 768px)
and (max-width: 991px) {
body { font-size: 14pt; }
div.content { width: 96ex; margin: 0 auto; }
}
@media only screen
and (min-width: 480px)
and (max-width: 767px) {
body { font-size: 11pt; }
div.content { width: 96ex; margin: 0 auto; }
}
@media only screen
and (max-width: 479px) {
body { font-size: 8pt; }
div.content { width: 96ex; margin: 0 auto; }
}
@media only screen
and (min-device-width : 375px)
and (max-device-width : 667px) {
body { font-size: 9.5pt; }
div.content { width: 96ex; margin: 0; }
}
@media only screen
and (min-device-width: 1200px) {
body { font-size: 10pt; margin: 0 4em; }
div.content { width: 96ex; margin: 0; }
}
h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6 {
font-weight: bold;
/* line-height: 0pt; */
display: inline;
white-space: pre;
font-family: monospace;
font-size: 1em;
font-weight: bold;
}
pre {
font-size: 1em;
margin-top: 0px;
margin-bottom: 0px;
}
.pre {
white-space: pre;
font-family: monospace;
}
.header{
font-weight: bold;
}
.newpage {
page-break-before: always;
}
.invisible {
text-decoration: none;
color: white;
}
@media print {
body {
margin-top: 5em;
font-family: monospace;
font-size: 10.5pt;
}
h1, h2, h3, h4, h5, h6 {
font-size: 1em;
}
a:link, a:visited {
color: inherit;
text-decoration: none;
}
.noprint {
display: none;
}
}
@media screen {
.grey, .grey a:link, .grey a:visited {
color: #777;
}
.meta-info {
background-color: #EEE;
}
.top {
border-top: 7px solid #EEE;
}
.pad {
padding-top: 7px;
line-height: 24px;
padding-bottom: 4px;
}
.bgwhite { background-color: white; }
.bgred { background-color: #F44; }
.bggrey { background-color: #666; }
.bgbrown { background-color: #840; }
.bgorange { background-color: #FA0; }
.bgyellow { background-color: #EE0; }
.bgmagenta{ background-color: #F4F; }
.bgblue { background-color: #66F; }
.bgcyan { background-color: #4DD; }
.bggreen { background-color: #4F4; }
.legend { font-size: 90%; }
.cplate { font-size: 70%; border: solid grey 1px; }
}
.bgwhite { background-color: white; }
.bgred { background-color: #F44; }
.bggrey { background-color: #666; }
.bgbrown { background-color: #840; }
.bgorange { background-color: #FA0; }
.bgyellow { background-color: #EE0; }
.bgmagenta{ background-color: #F4F; }
.bgblue { background-color: #66F; }
.bgcyan { background-color: #4DD; }
.bggreen { background-color: #4F4; }
.draftcontent { margin-top:0px !important;}
</style>
<!--[if lt IE 9]>
<script src="https://www.ietf.org/lib/dt/7.38.0/html5shiv/html5shiv.min.js"></script>
<script src="https://www.ietf.org/lib/dt/7.38.0/respond/dest/respond.min.js"></script>
<![endif]-->
<link rel="alternate" type="application/atom+xml" title="Document changes" href="https://datatracker.ietf.org/feed/document-changes/draft-kaliski-pkcs8/">
<meta name="description" content="Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification Version 1.2 (RFC )">
<script src="./rfc5208_files/d3.min.js.download"></script>
<script src="./rfc5208_files/jquery.min.js.download"></script>
<link rel="shortcut icon" href="https://www.ietf.org/lib/dt/7.38.0/ietf/images/ietf-icon-blue3.png">
<link rel="apple-touch-icon" href="https://www.ietf.org/lib/dt/7.38.0/ietf/images/apple-touch-icon.png">
</head>
<body style="padding-top: 0;">
<div class="content" id="content">
<!-- template: /a/www/ietf-datatracker/web/ietf/templates/doc/document_html.html -->
<div class="rfcmarkup">
<div class="noprint" style="height: 6px;">
<div onmouseover="this.style.cursor='pointer';" onclick="showLegend();" onmouseout="hideLegend()" style="height: 6px; min-height: 6px; width: 96ex; position: absolute; margin-top:0; " class="meta-info bgbrown" title="Click for colour legend."> </div>
<div id="legend" class="meta-info noprint pre legend" style="position:absolute; top: 4px; left: 4ex; visibility:hidden; background-color: white; padding: 4px 9px 5px 7px; border: solid #345 1px; " onmouseover="showLegend();" onmouseout="hideLegend();">
</div>
</div>
<div class="noprint">
<pre class="pre meta-info">[<a href="https://datatracker.ietf.org/" title="Document search and retrieval page">Search</a>] [<a href="https://www.rfc-editor.org/rfc/rfc5208.txt" title="Plaintext version of this document">txt</a>|<a href="https://www.rfc-editor.org/rfc/rfc5208.html" title="HTML version of this document, from XML2RFC">html</a>|<a href="https://www.rfc-editor.org/rfc/pdfrfc/rfc5208.txt.pdf" title="PDF version of this document">pdf</a>|<a href="https://www.rfc-editor.org/rfc/inline-errata/rfc5208.html">with errata</a>|<a href="https://datatracker.ietf.org/doc/rfc5208/bibtex" title="BibTex entry for this document">bibtex</a>] [<a href="https://datatracker.ietf.org/doc/rfc5208/" title="Datatracker information for this document">Tracker</a>] [<a href="https://datatracker.ietf.org/group/gen/" title="The working group handling this document">WG</a>] [<a href="mailto:draft-kaliski-pkcs8@ietf.org?subject=draft-kaliski-pkcs8" title="Send email to the document authors">Email</a>] [<a href="https://www.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-kaliski-pkcs8-00.txt" title="Run an idnits check of this document">Nits</a>]
From: <a href="https://datatracker.ietf.org/doc/html/draft-kaliski-pkcs8-00">draft-kaliski-pkcs8-00</a> Informational
Obsoleted by: <a href="https://datatracker.ietf.org/doc/html/rfc5958">5958</a> <a class="text-warning" href="https://www.rfc-editor.org/errata_search.php?rfc=5208&rec_status=0">Errata exist</a></pre>
</div>
<div class="draftcontent">
<pre>Network Working Group B. Kaliski
Request for Comments: 5208 EMC
Category: Informational May 2008
<span class="h1">Public-Key Cryptography Standards (PKCS) #8:</span>
<span class="h1">Private-Key Information Syntax Specification Version 1.2</span>
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
IESG Note
The IESG thanks RSA Laboratories for transferring change control to
the IETF. Enhancements to this specification that preserve backward
compatibility are expected in an upcoming IETF standards track
document.
Abstract
This document represents a republication of PKCS #8 v1.2 from RSA
Laboratories' Public Key Cryptography Standard (PKCS) series. Change
control is transferred to the IETF. The body of this document,
except for the security considerations section, is taken directly
from the PKCS #8 v1.2 specification.
This document describes a syntax for private-key information.
Table of Contents
<a href="https://datatracker.ietf.org/doc/html/rfc5208#section-1">1</a>. Introduction ....................................................<a href="https://datatracker.ietf.org/doc/html/rfc5208#page-2">2</a>
<a href="https://datatracker.ietf.org/doc/html/rfc5208#section-2">2</a>. Definitions .....................................................<a href="https://datatracker.ietf.org/doc/html/rfc5208#page-2">2</a>
<a href="https://datatracker.ietf.org/doc/html/rfc5208#section-3">3</a>. Symbols and Abbreviations .......................................<a href="https://datatracker.ietf.org/doc/html/rfc5208#page-2">2</a>
<a href="https://datatracker.ietf.org/doc/html/rfc5208#section-4">4</a>. General Overview ................................................<a href="https://datatracker.ietf.org/doc/html/rfc5208#page-2">2</a>
<a href="https://datatracker.ietf.org/doc/html/rfc5208#section-5">5</a>. Private-Key Information Syntax ..................................<a href="https://datatracker.ietf.org/doc/html/rfc5208#page-3">3</a>
<a href="https://datatracker.ietf.org/doc/html/rfc5208#section-6">6</a>. Encrypted Private-Key Information Syntax ........................<a href="https://datatracker.ietf.org/doc/html/rfc5208#page-4">4</a>
<a href="https://datatracker.ietf.org/doc/html/rfc5208#section-7">7</a>. Security Considerations .........................................<a href="https://datatracker.ietf.org/doc/html/rfc5208#page-4">4</a>
<a href="https://datatracker.ietf.org/doc/html/rfc5208#appendix-A">Appendix A</a>. ASN.1 Syntax ...........................................<a href="https://datatracker.ietf.org/doc/html/rfc5208#page-5">5</a>
Informative References .............................................<a href="https://datatracker.ietf.org/doc/html/rfc5208#page-6">6</a>
<span class="grey">Kaliski Informational [Page 1]</span></pre>
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-2"></span>
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc5208">RFC 5208</a> PKCS #8: Private-Key Information Syntax Standard May 2008</span>
<span class="h2"><a class="selflink" id="section-1" href="https://datatracker.ietf.org/doc/html/rfc5208#section-1">1</a>. Introduction</span>
This document describes a syntax for private-key information.
Private-key information includes a private key for some public-key
algorithm and a set of attributes. The document also describes a
syntax for encrypted private keys. A password-based encryption
algorithm (e.g., one of those described in [PKCS#5]) could be used to
encrypt the private-key information.
The intention of including a set of attributes is to provide a simple
way for a user to establish trust in information such as a
distinguished name or a top-level certification authority's public
key. While such trust could also be established with a digital
signature, encryption with a secret key known only to the user is
just as effective and possibly easier to implement. A non-exhaustive
list of attributes is given in [PKCS#9].
<span class="h2"><a class="selflink" id="section-2" href="https://datatracker.ietf.org/doc/html/rfc5208#section-2">2</a>. Definitions</span>
For the purposes of this document, the following definitions apply.
AlgorithmIdentifier: A type that identifies an algorithm (by
object identifier) and any associated parameters. This type is
defined in [<a href="https://datatracker.ietf.org/doc/html/rfc5208#ref-X.509">X.509</a>].
ASN.1: Abstract Syntax Notation One, as defined in [<a href="https://datatracker.ietf.org/doc/html/rfc5208#ref-X.208">X.208</a>].
Attribute: A type that contains an attribute type (specified by
object identifier) and one or more attribute values. This type is
defined in [<a href="https://datatracker.ietf.org/doc/html/rfc5208#ref-X.501">X.501</a>].
BER: Basic Encoding Rules, as defined in [<a href="https://datatracker.ietf.org/doc/html/rfc5208#ref-X.209">X.209</a>].
<span class="h2"><a class="selflink" id="section-3" href="https://datatracker.ietf.org/doc/html/rfc5208#section-3">3</a>. Symbols and Abbreviations</span>
No symbols or abbreviations are defined in this document.
<span class="h2"><a class="selflink" id="section-4" href="https://datatracker.ietf.org/doc/html/rfc5208#section-4">4</a>. General Overview</span>
The next two sections specify private-key information syntax and
encrypted private-key information syntax.
This document exports two types: PrivateKeyInfo (<a href="https://datatracker.ietf.org/doc/html/rfc5208#section-6">Section 6</a>) and
EncryptedPrivateKeyInfo (<a href="https://datatracker.ietf.org/doc/html/rfc5208#section-7">Section 7</a>).
<span class="grey">Kaliski Informational [Page 2]</span></pre>
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-3"></span>
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc5208">RFC 5208</a> PKCS #8: Private-Key Information Syntax Standard May 2008</span>
<span class="h2"><a class="selflink" id="section-5" href="https://datatracker.ietf.org/doc/html/rfc5208#section-5">5</a>. Private-Key Information Syntax</span>
This section gives the syntax for private-key information.
Private-key information shall have ASN.1 type PrivateKeyInfo:
PrivateKeyInfo ::= SEQUENCE {
version Version,
privateKeyAlgorithm PrivateKeyAlgorithmIdentifier,
privateKey PrivateKey,
attributes [0] IMPLICIT Attributes OPTIONAL }
Version ::= INTEGER
PrivateKeyAlgorithmIdentifier ::= AlgorithmIdentifier
PrivateKey ::= OCTET STRING
Attributes ::= SET OF Attribute
The fields of type PrivateKeyInfo have the following meanings:
version is the syntax version number, for compatibility with
future revisions of this document. It shall be 0 for this version
of the document.
privateKeyAlgorithm identifies the private-key algorithm. One
example of a private-key algorithm is PKCS #1's rsaEncryption
[PKCS#1].
privateKey is an octet string whose contents are the value of the
private key. The interpretation of the contents is defined in the
registration of the private-key algorithm. For an RSA private
key, for example, the contents are a BER encoding of a value of
type RSAPrivateKey.
attributes is a set of attributes. These are the extended
information that is encrypted along with the private-key
information.
<span class="grey">Kaliski Informational [Page 3]</span></pre>
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-4"></span>
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc5208">RFC 5208</a> PKCS #8: Private-Key Information Syntax Standard May 2008</span>
<span class="h2"><a class="selflink" id="section-6" href="https://datatracker.ietf.org/doc/html/rfc5208#section-6">6</a>. Encrypted Private-Key Information Syntax</span>
This section gives the syntax for encrypted private-key information.
Encrypted private-key information shall have ASN.1 type
EncryptedPrivateKeyInfo:
EncryptedPrivateKeyInfo ::= SEQUENCE {
encryptionAlgorithm EncryptionAlgorithmIdentifier,
encryptedData EncryptedData }
EncryptionAlgorithmIdentifier ::= AlgorithmIdentifier
EncryptedData ::= OCTET STRING
The fields of type EncryptedPrivateKeyInfo have the following
meanings:
encryptionAlgorithm identifies the algorithm under which the
private-key information is encrypted. Two examples are PKCS #5's
pbeWithMD2AndDES-CBC and pbeWithMD5AndDES-CBC [PKCS#5].
encryptedData is the result of encrypting the private-key
information.
The encryption process involves the following two steps:
1. The private-key information is BER encoded, yielding an octet
string.
2. The result of step 1 is encrypted with the secret key to give
an octet string, the result of the encryption process.
<span class="h2"><a class="selflink" id="section-7" href="https://datatracker.ietf.org/doc/html/rfc5208#section-7">7</a>. Security Considerations</span>
Protection of the private-key information is vital to public-key
cryptography. Disclosure of the private-key material to another
entity can lead to masquerades. The encryption algorithm used in the
encryption process must be as 'strong' as the key it is protecting.
<span class="grey">Kaliski Informational [Page 4]</span></pre>
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-5"></span>
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc5208">RFC 5208</a> PKCS #8: Private-Key Information Syntax Standard May 2008</span>
<span class="h2"><a class="selflink" id="appendix-A" href="https://datatracker.ietf.org/doc/html/rfc5208#appendix-A">Appendix A</a>. ASN.1 Syntax</span>
PKCS-8 {iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-8(8)
modules(1) pkcs-8(1)}
-- $Revision: 1.5 $
-- This module has been checked for conformance with the ASN.1
-- standard by the OSS ASN.1 Tools
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
-- EXPORTS All --
-- All types and values defined in this module is exported for use in
-- other ASN.1 modules.
IMPORTS
informationFramework
FROM UsefulDefinitions {joint-iso-itu-t(2) ds(5) module(1)
usefulDefinitions(0) 3}
Attribute
FROM InformationFramework informationFramework
AlgorithmIdentifier, ALGORITHM-IDENTIFIER
FROM PKCS-5 {iso(1) member-body(2) us(840) rsadsi(113549)
pkcs(1) pkcs-5(5) modules(16) pkcs-5(1)};
-- Private-key information syntax
PrivateKeyInfo ::= SEQUENCE {
version Version,
privateKeyAlgorithm AlgorithmIdentifier {{PrivateKeyAlgorithms}},
privateKey PrivateKey,
attributes [0] Attributes OPTIONAL }
Version ::= INTEGER {v1(0)} (v1,...)
PrivateKey ::= OCTET STRING
Attributes ::= SET OF Attribute
<span class="grey">Kaliski Informational [Page 5]</span></pre>
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-6"></span>
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc5208">RFC 5208</a> PKCS #8: Private-Key Information Syntax Standard May 2008</span>
-- Encrypted private-key information syntax
EncryptedPrivateKeyInfo ::= SEQUENCE {
encryptionAlgorithm AlgorithmIdentifier {{KeyEncryptionAlgorithms}},
encryptedData EncryptedData
}
EncryptedData ::= OCTET STRING
PrivateKeyAlgorithms ALGORITHM-IDENTIFIER ::= {
... -- For local profiles
}
KeyEncryptionAlgorithms ALGORITHM-IDENTIFIER ::= {
... -- For local profiles
}
END
Informative References
[PKCS#1] RSA Laboratories. PKCS #1: RSA Encryption Standard. Version
1.5, November 1993.
[PKCS#5] RSA Laboratories. PKCS #5: Password-Based Encryption
Standard. Version 1.5, November 1993.
[PKCS#9] RSA Laboratories. PKCS #9: Selected Attribute Types.
Version 1.1, November 1993.
[<a id="ref-X.208">X.208</a>] CCITT. Recommendation X.208: Specification of Abstract
Syntax Notation One (ASN.1). 1988.
[<a id="ref-X.209">X.209</a>] CCITT. Recommendation X.209: Specification of Basic
Encoding Rules for Abstract Syntax Notation One (ASN.1).
1988.
[<a id="ref-X.501">X.501</a>] CCITT. Recommendation X.501: The Directory - Models. 1988.
[<a id="ref-X.509">X.509</a>] CCITT. Recommendation X.509: The Directory - Authentication
Framework. 1988.
<span class="grey">Kaliski Informational [Page 6]</span></pre>
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-7"></span>
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc5208">RFC 5208</a> PKCS #8: Private-Key Information Syntax Standard May 2008</span>
Author's Addresses
Burt Kaliski
EMC Corporation
176 South Street
Hopkinton, MA 01748
USA
EMail: kaliski_burt@emc.com
<span class="grey">Kaliski Informational [Page 7]</span></pre>
<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-8"></span>
<span class="grey"><a href="https://datatracker.ietf.org/doc/html/rfc5208">RFC 5208</a> PKCS #8: Private-Key Information Syntax Standard May 2008</span>
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://datatracker.ietf.org/doc/html/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://datatracker.ietf.org/doc/html/bcp78">BCP 78</a> and <a href="https://datatracker.ietf.org/doc/html/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Kaliski Informational [Page 8]
</pre>
</div>
</div>
</div>
<script>$(".visible-nojs").removeClass("visible-nojs");</script>
<script>$(".hidden-nojs").removeClass("hidden-nojs");</script>
<script type="text/javascript"><!--
var legend_html = "Colour legend:<br /> \
<table> \
<tr><td>Unknown:</td> <td><span class='cplate bgwhite'> </span></td></tr> \
<tr><td>Draft:</td> <td><span class='cplate bgred'> </span></td></tr> \
<tr><td>Informational:</td> <td><span class='cplate bgorange'> </span></td></tr> \
<tr><td>Experimental:</td> <td><span class='cplate bgyellow'> </span></td></tr> \
<tr><td>Best Common Practice:</td> <td><span class='cplate bgmagenta'> </span></td></tr> \
<tr><td>Proposed Standard:</td> <td><span class='cplate bgblue'> </span></td></tr> \
<tr><td>Draft Standard (old designation):</td> <td><span class='cplate bgcyan'> </span></td></tr> \
<tr><td>Internet Standard:</td> <td><span class='cplate bggreen'> </span></td></tr> \
<tr><td>Historic:</td> <td><span class='cplate bggrey'> </span></td></tr> \
<tr><td>Obsolete:</td> <td><span class='cplate bgbrown'> </span></td></tr> \
</table>";
function showLegend() {
var elem = document.getElementById('legend');
elem.innerHTML = legend_html
elem.style.visibility='visible';
}
function hideLegend() {
var elem = document.getElementById('legend');
elem.style.visibility='hidden';
elem.innerHTML = "";
}
// -->
</script>
</body></html>