idnits 2.17.1 draft-kaliski-pkcs8-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 260. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 271. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 278. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 284. 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 : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 141: '... attributes [0] IMPLICIT Attributes OPTIONAL }...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 16, 2008) is 5853 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Missing reference section? '0' on line 141 looks like a reference Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Burt Kaliski, EMC 2 Internet Draft April 16, 2008 3 Intended Status: Informational 4 Expires: October 16, 2008 6 PKCS #8: Private-Key Information Syntax Standard 7 Version 1.2 8 draft-kaliski-pkcs8-00.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 This Internet-Draft will expire on October 16, 2008. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2008). 39 Abstract 41 This document represents a republication of PKCS #8 v1.2 from RSA 42 Laboratories' Public Key Cryptography Standard (PKCS) series. Change 43 control is transferred to the IETF. The body of this document, 44 except for the security considerations section, is taken directly 45 from the PKCS #8 v1.2 specification. 47 This document describes a syntax for private-key information. 49 Syntax Version 1.2 51 Table of Contents 53 1. Introduction...................................................2 54 2. References.....................................................2 55 3. Definitions....................................................3 56 4. Symbols and Abbreviations......................................3 57 5. General Overview...............................................3 58 6. Private Key Information Syntax.................................3 59 7. Encrypted private-key information syntax.......................4 60 8. IANA Considerations............................................5 62 1. Introduction 64 This standard describes a syntax for private-key information. 65 Private-key information includes a private key for some public-key 66 algorithm and a set of attributes. The standard also describes a 67 syntax for encrypted private keys. A password-based encryption 68 algorithm (e.g., one of those described in PKCS #5) could be used to 69 encrypt the private-key information. 71 The intention of including a set of attributes is to provide a simple 72 way for a user to establish trust in information such as a 73 distinguished name or a top-level certification authority's public 74 key. While such trust could also be established with a digital 75 signature, encryption with a secret key known only to the user is 76 just as effective and possibly easier to implement. A non-exhaustive 77 list of attributes is given in PKCS #9. 79 2. References 81 PKCS #1 RSA Laboratories. PKCS #1: RSA Encryption Standard. Version 82 1.5, November 1993. 84 PKCS #5 RSA Laboratories. PKCS #5: Password-Based Encryption 85 Standard. Version 1.5, November 1993. 87 PKCS #9 RSA Laboratories. PKCS #9: Selected Attribute Types. Version 88 1.1, November 1993. 90 X.208 CCITT. Recommendation X.208: Specification of Abstract Syntax 91 Notation One (ASN.1). 1988. 93 X.209 CCITT. Recommendation X.209: Specification of Basic Encoding 94 Rules for Abstract Syntax Notation One (ASN.1). 1988. 96 X.501 CCITT. Recommendation X.501: The Directory - Models. 1988. 98 Syntax Version 1.2 100 X.509 CCITT. Recommendation X.509: The Directory - Authentication 101 Framework. 1988. 103 3. Definitions 105 For the purposes of this standard, the following definitions apply. 107 AlgorithmIdentifier: A type that identifies an algorithm (by 108 object identifier) and any associated parameters. This type is 109 defined in X.509. 111 ASN.1: Abstract Syntax Notation One, as defined in X.208. 113 Attribute: A type that contains an attribute type (specified by 114 object identifier) and one or more attribute values. This type is 115 defined in X.501. 117 BER: Basic Encoding Rules, as defined in X.209. 119 4. Symbols and Abbreviations 121 No symbols or abbreviations are defined in this standard. 123 5. General Overview 125 The next two sections specify private-key information syntax and 126 encrypted private-key information syntax. 128 This standard exports two types: PrivateKeyInfo (Section 6) and 129 EncryptedPrivateKeyInfo (Section 7). 131 6. Private Key Information Syntax 133 This section gives the syntax for private-key information. 135 Private-key information shall have ASN.1 type PrivateKeyInfo: 137 PrivateKeyInfo ::= SEQUENCE { 138 version Version, 139 privateKeyAlgorithm PrivateKeyAlgorithmIdentifier, 140 privateKey PrivateKey, 141 attributes [0] IMPLICIT Attributes OPTIONAL } 143 Version ::= INTEGER 145 PrivateKeyAlgorithmIdentifier ::= AlgorithmIdentifier 146 Syntax Version 1.2 148 PrivateKey ::= OCTET STRING 150 Attributes ::= SET OF Attribute 152 The fields of type PrivateKeyInfo have the following meanings: 154 version is the syntax version number, for compatibility with 155 future revisions of this standard. It shall be 0 for this version 156 of the standard. 158 privateKeyAlgorithm identifies the private-key algorithm. One 159 example of a private-key algorithm is PKCS #1's rsaEncryption. 161 privateKey is an octet string whose contents are the value of the 162 private key. The interpretation of the contents is defined in the 163 registration of the private -key algorithm. For an RSA private 164 key, for example, the contents are a BER encoding of a value of 165 type RSAPrivateKey. 167 attributes is a set of attributes. These are the extended 168 information that is encrypted along with the private-key 169 information. 171 7. Encrypted private-key information syntax 173 This section gives the syntax for encrypted private-key information. 175 Encrypted private-key information shall have ASN.1 type 176 EncryptedPrivateKeyInfo: 178 EncryptedPrivateKeyInfo ::= SEQUENCE { 179 encryptionAlgorithm EncryptionAlgorithmIdentifier, 180 encryptedData EncryptedData } 182 EncryptionAlgorithmIdentifier ::= AlgorithmIdentifier 184 EncryptedData ::= OCTET STRING 186 The fields of type EncryptedPrivateKeyInfo have the following 187 meanings: 189 encryptionAlgorithm identifies the algorithm under which the 190 private-key information is encrypted. Two examples are PKCS #5's 191 pbeWithMD2AndDES-CBC and pbeWithMD5AndDES-CBC. 193 encryptedData is the result of encrypting the private-key 194 information. 196 Syntax Version 1.2 198 The encryption process involves the following two steps: 200 1. The private-key information is BER encoded, yielding an octet 201 string. 203 2. The result of step 1 is encrypted with the secret key to give 204 an octet string, the result of the encryption process. 206 8. Security Considerations 208 Protection of the private-key information is vital to public-key 209 cryptography. Disclosure of the private-key material to another 210 entity can lead to masquerades. The encryption algorithm used in the 211 encryption process must be as 'strong' as the key it is protecting. 213 9. IANA Considerations 215 None. Please remove this section prior to publication as an RFC. 217 Revision History 219 Version 1.0 221 Version 1.0 was distributed to participants in RSA Data Security, 222 Inc.'s Public-Key Cryptography Standards meetings in February and 223 March 1991. 225 Version 1.1 227 Version 1.1 is part of the June 3, 1991 initial public release of 228 PKCS. Version 1.1 was published as NIST/OSI Implementors' 229 Workshop document SEC-SIG-91-23. 231 Version 1.2 233 Version 1.2 incorporates several editorial changes, including 234 updates to the references and the addition of a revision history. 236 Author's Addresses 238 Burt Kaliski 240 174 Middlesex Turnpike 241 Bedford, MA 01730 243 kaliski_burt@emc.com 244 Syntax Version 1.2 246 Full Copyright Statement 248 Copyright (C) The IETF Trust (2008). 250 This document is subject to the rights, licenses and restrictions 251 contained in BCP 78, and except as set forth therein, the authors 252 retain all their rights. 254 This document and the information contained herein are provided on an 255 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 256 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 257 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 258 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 259 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 260 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 262 Intellectual Property 264 The IETF takes no position regarding the validity or scope of any 265 Intellectual Property Rights or other rights that might be claimed to 266 pertain to the implementation or use of the technology described in 267 this document or the extent to which any license under such rights 268 might or might not be available; nor does it represent that it has 269 made any independent effort to identify any such rights. Information 270 on the procedures with respect to rights in RFC documents can be 271 found in BCP 78 and BCP 79. 273 Copies of IPR disclosures made to the IETF Secretariat and any 274 assurances of licenses to be made available, or the result of an 275 attempt made to obtain a general license or permission for the use of 276 such proprietary rights by implementers or users of this 277 specification can be obtained from the IETF on-line IPR repository at 278 http://www.ietf.org/ipr. 280 The IETF invites any interested party to bring to its attention any 281 copyrights, patents or patent applications, or other proprietary 282 rights that may cover technology that may be required to implement 283 this standard. Please address the information to the IETF at ietf- 284 ipr@ietf.org. 286 Acknowledgment 288 Funding for the RFC Editor function is provided by the IETF 289 Administrative Support Activity (IASA).