Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX)
RFC 6268
Document | Type |
RFC - Informational
(July 2011; No errata)
Updates RFC 5911
Was draft-turner-additional-new-asn (individual in sec area)
|
|
---|---|---|---|
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6268 (Informational) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Stephen Farrell | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) J. Schaad Request for Comments: 6268 Soaring Hawk Consulting Updates: 5911 S. Turner Category: Informational IECA, Inc. ISSN: 2070-1721 July 2011 Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX) 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 some auxiliary ASN.1 modules to conform to the 2008 version of ASN.1; the 1988 ASN.1 modules remain the normative version. 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/rfc6268. Copyright Notice Copyright (c) 2011 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 Schaad & Turner Informational [Page 1] RFC 6268 Additional New ASN.1 Modules July 2011 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. ASN.1 Updates (2002 to 2008) . . . . . . . . . . . . . . . 4 1.2. Requirements Terminology . . . . . . . . . . . . . . . . . 4 2. ASN.1 Module RFC 3274 . . . . . . . . . . . . . . . . . . . . 5 3. ASN.1 Module RFC 3779 . . . . . . . . . . . . . . . . . . . . 7 4. ASN.1 Module RFC 6019 . . . . . . . . . . . . . . . . . . . . 10 5. ASN.1 Module RFC 4073 . . . . . . . . . . . . . . . . . . . . 11 6. ASN.1 Module RFC 4231 . . . . . . . . . . . . . . . . . . . . 12 7. ASN.1 Module RFC 4334 . . . . . . . . . . . . . . . . . . . . 15 8. ASN.1 Module RFC 5083 . . . . . . . . . . . . . . . . . . . . 16 9. ASN.1 Module RFC 5652 . . . . . . . . . . . . . . . . . . . . 18 10. ASN.1 Module RFC 5752 . . . . . . . . . . . . . . . . . . . . 29 11. Module Identifiers in ASN.1 . . . . . . . . . . . . . . . . . 30 12. Security Considerations . . . . . . . . . . . . . . . . . . . 32 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32 13.1. Normative References . . . . . . . . . . . . . . . . . . . 32 13.2. Informative References . . . . . . . . . . . . . . . . . . 33 Schaad & Turner Informational [Page 2] RFC 6268 Additional New ASN.1 Modules July 2011 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 Secure/Multipurpose Internet Mail Extensions (S/MIME).Show full document text