RFC 5911: New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME | RFC Editor

Skip to content Primary navigationThe RFC SeriesFor AuthorsAbout UsHomeRFC 5911 View as: Plain Text, Compact HTML Info RFC 5911: New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIMEASN.1MIMES/MIMEX.509June 2010. P. Hoffman, J. SchaadInformationalSubscribe9 subscribed Add to Set Read aloud This RFC was updated, see RFC 6268.Internet Engineering Task Force (IETF) P. Hoffman Request for Comments: 5911 VPN Consortium Category: Informational J. Schaad ISSN: 2070-1721 Soaring Hawk Consulting June 2010 New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME Abstract The Cryptographic Message Syntax (CMS) format, and many associated formats, are expressed using ASN.1. The current ASN.1 modules conform to the 1988 version of ASN.1. This document updates those ASN.1 modules to conform to the 2002 version of ASN.1. There are no bits-on-the-wire changes to any of the formats; this is simply a change to the syntax. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. 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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see 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/rfc5911. Hoffman & Schaad Informational [Page 1] RFC 5911 New ASN.1 for CMS and S/MIME June 2010 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. 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Design Notes . . . . . . . . . . . . . . . . . . . . . . . 4 2. ASN.1 Module AlgorithmInformation . . . . . . . . . . . . . . 4 3. ASN.1 Module for RFC 3370 . . . . . . . . . . . . . . . . . . 14 4. ASN.1 Module for RFC 3565 . . . . . . . . . . . . . . . . . . 20 5. ASN.1 Module for RFC 3851 . . . . . . . . . . . . . . . . . . 22 6. ASN.1 Module for RFC 3852 . . . . . . . . . . . . . . . . . . 24 7. ASN.1 Module for RFC 4108 . . . . . . . . . . . . . . . . . . 34 8. ASN.1 Module for RFC 4998 . . . . . . . . . . . . . . . . . . 40 9. ASN.1 Module for RFC 5035 . . . . . . . . . . . . . . . . . . 41 10. ASN.1 Module for RFC 5083 . . . . . . . . . . . . . . . . . . 47 11. ASN.1 Module for RFC 5084 . . . . . . . . . . . . . . . . . . 48 12. ASN.1 Module for RFC 5275 . . . . . . . . . . . . . . . . . . 50 13. Security Considerations . . . . . . . . . . . . . . . . . . . 57 14. Normative References . . . . . . . . . . . . . . . . . . . . . 57 Hoffman & Schaad Informational [Page 2] RFC 5911 New ASN.1 for CMS and S/MIME June 2010 1. Introduction Some developers would like the IETF to use the latest version of ASN.1 in its standards. Most of the RFCs that relate to security protocols still use ASN.1 from the 1988 standard, which has been deprecated. This is particularly true for the standards that relate to PKIX, CMS, and S/MIME. This document updates the following RFCs to use ASN.1 modules that conform to the 2002 version of ASN.1 [ASN1-2002]. Note that not all the modules are updated; some are included to simply make the set complete. o RFC 3370, CMS Algorithms [RFC3370] o RFC 3565, Use of AES in CMS [RFC3565] o RFC 3851, S/MIME Version 3.1 Message Specification [RFC3851] o RFC 3852, CMS main [RFC3852] o RFC 4108, Using CMS to Protect Firmware Packages [RFC4108] o RFC 4998, Evidence Record Syntax (ERS) [RFC4998] o RFC 5035, Enhanced Security Services (ESS) [RFC5035] o RFC 5083, CMS Authenticated-Enveloped-Data Content Type [RFC5083] o RFC 5084, Using AES-CCM and AES-GCM Authenticated Encryption in CMS [RFC5084] o RFC 5275, CMS Symmetric Key Management and Distribution [RFC5275] Note that some of the modules in this document get some of their definitions from places different than the modules in the original RFCs. The idea is that these modules, when combined with the modules in [RFC5912] can stand on their own and do not need to import definitions from anywhere else. Also note that the ASN.1 modules in this document have references in their text comments that need to be looked up in original RFCs, and that some of those references may have already been superseded by later RFCs. The document also includes a module of common definitions called "AlgorithmInformation". These definitions are used here and in [RFC5912]. Hoffman & Schaad Informational [Page 3] RFC 5911 New ASN.1 for CMS and S/MIME June 2010 Note that some of the modules here import defini