The application/cms media type

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-05-21
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force (IETF)                         S. Turner
Internet Draft                                                      IECA
Intended Status: Informational                                R. Housley
Expires: November 22, 2013                                Vigil Security
                                                               J. Schaad
                                                 Soaring Hawk Consulting
                                                            May 21, 2013

                     The application/cms media type


   This document registers the application/cms media types for use with
   the corresponding CMS (Cryptographic Message Syntax) content types.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2013 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
   ( 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, Housley, & Schaad  Exp. Nov 22, 2013                    [Page 1]
Internet-Draft               CMS Media Type                 May 21, 2013

1. Introduction

   CMS (Cryptographic Message Syntax) [RFC5652] associates a content
   type identifier (OID) with a content; CMS content types have been
   widely used to define contents that can be enveloped using other CMS
   content types and to define envoloping content types some of which
   provide security services.  CMS protecting content types, those that
   provide security services, include: id-signedData [RFC5652], id-
   envelopedData [RFC5652], id-digestData [RFC5652], id-encryptedData
   [RFC5652], id-ct-authData [RFC5652], id-ct-authEnvelopedData
   [RFC5083], and id-ct-KP-encryptedKeyPkg [RFC6032].  CMS non-
   protecting content types, those that provide no security services but
   encapsulate other CMS content types, include: id-ct-contentInfo
   [RFC5652], id-compressedData [RFC3274], id-ct-contentCollection
   [RFC4073], and id-ct-contentWithAttrs [RFC4073].  Then, there are the
   inner most content types that include: id-data [RFC5652], id-ct-KP-
   aKeyPackage [RFC5958], id-ct-KP-sKeyPackage [RFC6031], id-ct-
   firmwarePackage [RFC4108], id-ct-firmwareLoadReceipt [RFC4108], id-
   ct-firmwareLoadError [RFC4108], id-ct-trustAnchorList [RFC5914], id-
   ct-KP-keyPackageReceipt [ID.housley-keypackage-receipt-n-error], and
   id-ct-KP-keyPackageError [ID.housley-keypackage-receipt-n-error].

   To support conveying CMS content types, this document defines a media
   type and parameters that indicate the enveloping and embedded CMS
   content types.

   [RFC5751] registered the application/pkc7-mime media type.  That
   document defined five optional smime-type parameters.  The smime-type
   parameter originally conveyed details about the security applied
   (signed or enveloped) to the data content type, hence signed-data and
   enveloped-data, the name of the data, and was later expanded to also
   indicate that the message was compressed, compressed-data, and that
   the message is a certs-only message.  This document does not affect
   those registrations as this document places no requirements on S/MIME

   The registration done by the S/MIME documents was done assuming that
   there would be a mime wrapping layer around each of the different
   enveloping contents, thus there was no need to include more than one
   item in each smime-type.  This is no longer the case with some of the
   more advanced enveloping types.  Some protocols such as the CMC
   certification protocol [CMC] have defined additional S/MIME types. 
   New protocols that intend to wrap mime content should continue to
   define an smime-type string, however new protocols that intend to
Show full document text