Cryptographic Message Syntax (CMS) Key Package Receipt and Error Content Types
RFC 7191
Document | Type |
RFC - Proposed Standard
(April 2014; No errata)
Was draft-housley-ct-keypackage-receipt-n-error (individual in sec area)
|
|
---|---|---|---|
Author | Russ Housley | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | Carl Wallace | ||
Shepherd write-up | Show (last changed 2013-10-30) | ||
IESG | IESG state | RFC 7191 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Stephen Farrell | ||
Send notices to | (None) | ||
IANA | IANA review state | IANA OK - No Actions Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) R. Housley Request for Comments: 7191 Vigil Security Category: Standards Track April 2014 ISSN: 2070-1721 Cryptographic Message Syntax (CMS) Key Package Receipt and Error Content Types Abstract This document defines the syntax for two Cryptographic Message Syntax (CMS) content types: one for key package receipts and another for key package errors. The key package receipt content type is used to confirm receipt of an identified key package or collection of key packages. The key package error content type is used to indicate an error occurred during the processing of a key package. CMS can be used to digitally sign, digest, authenticate, or encrypt these content types. 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/rfc7191. Copyright Notice Copyright (c) 2014 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. Housley Standards Track [Page 1] RFC 7191 Key Package Receipts and Errors April 2014 Table of Contents 1. Introduction ....................................................2 1.1. Requirements Terminology ...................................2 1.2. ASN.1 Syntax Notation ......................................2 1.3. Processing Key Package Receipt Requests ....................3 1.4. Processing Key Packages with Errors ........................3 2. SIR Entity Name .................................................3 3. Key Package Identifier and Receipt Request Attribute ............4 4. Key Package Receipt CMS Content Type ............................6 5. Key Package Error CMS Content Type ..............................8 6. Protecting the KeyPackageReceipt and KeyPackageError ...........17 7. Using the application/cms Media Type ...........................17 8. IANA Considerations ............................................17 9. Security Considerations ........................................17 10. Acknowledgements ..............................................18 11. References ....................................................18 11.1. Normative References .....................................18 11.2. Informative References ...................................20 Appendix A. ASN.1 Module ..........................................21 1. Introduction This document defines the syntax for two Cryptographic Message Syntax (CMS) [RFC5652] content types: one for key package receipts and another for key package errors. The key package receipt content type is used to confirm receipt of an identified key package or collection of key packages. The key package error content type is used to indicate an error occurred during the processing of a key package. CMS can be used to digitally sign, digest, authenticate, or encrypt these content types. 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 content types defined herein use ASN.1 ([X.680], [X.681], [X.682], and [X.683]). The CONTENT-TYPE definition was updated to the 2008 version of ASN.1 by [RFC6268]; however, none of the new 2008 ASN.1 tokens are used in this specification, which allows compilers that only support the 2002 version of ASN.1 to compile the module in Appendix A. Housley Standards Track [Page 2] RFC 7191 Key Package Receipts and Errors April 2014 1.3. Processing Key Package Receipt RequestsShow full document text