Re: [media-types] review requested: draft-turner-application-cms-media-type

[Sean Turner <[e-mail]>]

In case I'm just supposed to sending the template:

spt

------

Type name: application

Subtype name: cms

Required parameters: None.

Optional parameters:

   encapsulatedContent=y; where y is one or more CMS ECT
   (Encapsulating Content Types); multiple values are encapsulated in
   quotes and separated by a folding-whitespace comma folding-
   whitespace.  ECT values are based on content types found in
   [RFC3274], [RFC4073], [RFC5083], [RFC5652], and [RFC6032].  This
   list can later be extended see Section 3.
              authData
              compressedData
              contentCollection
              contentInfo
              contentWithAttrs
              authEnvelopedData
              encryptedKeyPkg
              digestData
              encryptedData
              envelopedData
              signedData

   innerContent=x; where x is one or more CMS ICT (Inner Content
   Types); multiple values encapsulated in quotes and are separated by
   a folding-whitespace comma folding-whitespace.  ICT values are
   based on content types found in [RFC4108], [RFC5914], [RFC5958],
   [RFC6031], and [ID.housley-keypackage-receipt-n-error].  This list
    can later be extended see Section 3.
              firmwarePackage
              firmwareLoadReceipt
              firmwareLoadError
              aKeyPackage
              sKeyPackage
              trustAnchorList
              keyPackageReceipt
              keyPackageError

   id-data [RFC5652] MUST NOT be used if it is the only inner content
   listed and the data is MIME content;  when id-data is used to
   encapsulate MIME, the media type application/pkcs7-mime media type
   defined in [RFC5751] SHOULD be used.

   The optional parameters are case-sensitive.

Encoding considerations:

   Binary.

   [RFC5652] requires that the outer most encapsulation be
   ContentInfo.

Security considerations:

   See [RFC3370], [RFC5652], [RFC5753], and [RFC5754] for id-
   signedData, id-envelopedData, id-digestData, id-encryptedData, id-
   ct-authData; see [RFC5958], [RFC5959], and [RFC6162] for id-ct-KP-
   aKeyPackage; see [RFC6031] and [RFC6160] for id-ct-KP- sKeyPackage;
   see [RFC6032], [RFC6033], and [RFC6161] for id-ct-KP-
   encryptedKeyPkg; see [RFC5914] for id-ct-trustAnchorList; see
   [RFC3274] for id-compressedData; see [RFC5083] and [RFC5084] for
   id-ct-authEnvelopedData; see [RFC4073] for id-ct-contentCollection
   and id-ct-contentWithAttrs; see [RFC4108] for id-ct-
   firmwarePackage, id-ct-firmwareLoadReceipt, id-ct-
   firmwareLoadError; see [ID.housley-keypackage-receipt-n-error] for
   id-ct-KP-keyPackageReceipt and id-ct-KP-keyPackageError.

Interoperability considerations:

   See [RFC3274], [RFC4073], [RFC4108], [RFC5083], [RFC5652],
   [RFC5914], [RFC5958], [RFC6031], [RFC6032], and [ID.housley-
   keypackage-receipt-n-error].

   In all cases, CMS content types are encapsulated within ContentInfo
   structures [RFC5652]; that is the outer most enveloping structure
   is ContentInfo.

   When processing a SignedData around any of the inner content type
   the [RFC5652] validation rules MUST be used.  The PKCS #7 [RFC2315]
   validation rules MUST NOT be used.

Published specification: This specification.

Applications which use this media type:

   Applications that support CMS (Cryptographic Message Syntax)
   content types.

Additional information:

   Magic number(s): None
   File extension(s): .cms
   Macintosh File Type Code(s):

Person & email address to contact for further information:

   Sean Turner <[e-mail]>

Restrictions on usage: none

Author: Sean Turner <[e-mail]>

Intended usage: COMMON

Change controller: The IESG <[e-mail]>

On 6/3/13 1:13 PM, Sean Turner wrote:
> I'd like to request an expert review for the application/cms media type
> registration found in:
> http://tools.ietf.org/html/draft-turner-application-cms-media-type
>
> Thanks,
>
> spt