Asymmetric Key Packages
RFC 5958
Document | Type |
RFC - Proposed Standard
(August 2010; Errata)
Obsoletes RFC 5208
Was draft-turner-asymmetrickeyformat (individual in sec area)
|
|
---|---|---|---|
Author | Sean Turner | ||
Last updated | 2020-01-21 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5958 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Tim Polk | ||
Send notices to | fluffy@cisco.com, cwallace@cygnacom.com |
Internet Engineering Task Force (IETF) S. Turner Request for Comments: 5958 IECA Obsoletes: 5208 August 2010 Category: Standards Track ISSN: 2070-1721 Asymmetric Key Packages Abstract This document defines the syntax for private-key information and a content type for it. Private-key information includes a private key for a specified public-key algorithm and a set of attributes. The Cryptographic Message Syntax (CMS), as defined in RFC 5652, can be used to digitally sign, digest, authenticate, or encrypt the asymmetric key format content type. This document obsoletes RFC 5208. 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 Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5958. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) 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. Turner Standards Track [Page 1] RFC 5958 Asymmetric Key Packages August 2010 This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. 1. Introduction This document defines the syntax for private-key information and a Cryptographic Message Syntax (CMS) [RFC5652] content type for it. Private-key information includes a private key for a specified public-key algorithm and a set of attributes. The CMS can be used to digitally sign, digest, authenticate, or encrypt the asymmetric key format content type. This document obsoletes PKCS #8 v1.2 [RFC5208]. 1.1. Requirements Terminology 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 [RFC2119]. 1.2. ASN.1 Syntax Notation The key package is defined using ASN.1 [X.680], [X.681], [X.682], and [X.683]. 1.3. Summary of Updates to RFC 5208 The following summarizes the updates to [RFC5208]: - Changed the name "PrivateKeyInfo" to "OneAsymmetricKey". This reflects the addition of the publicKey field to allow both parts of the asymmetric key to be conveyed separately. Not all algorithms will use both fields; however, the publicKey field was added for completeness. - Defined Asymmetric Key Package CMS content type. - Removed redundant IMPLICIT from attributes. - Added publicKey to OneAsymmetricKey and updated the version number. Turner Standards Track [Page 2] RFC 5958 Asymmetric Key Packages August 2010 - Added that PKCS #9 attributes may be supported. - Added discussion of compatibility with other private-key formats. - Added requirements for encoding rule set. - Changed imports from PKCS #5 to [RFC5912] and [RFC5911]. - Replaced ALGORITHM-IDENTIFIER with ALGORITHM from [RFC5912]. - Registers application/pkcs8 media type and .p8 file extension. 2. Asymmetric Key Package CMS Content Type The asymmetric key package CMS content type is used to transfer one or more plaintext asymmetric keys from one party to another. An asymmetric key package MAY be encapsulated in one or more CMSShow full document text