< draft-turner-application-cms-media-type-07.txt   draft-turner-application-cms-media-type-08.txt >
Internet Engineering Task Force (IETF) S. Turner Internet Engineering Task Force (IETF) S. Turner
Internet Draft IECA Internet Draft IECA
Intended Status: Informational R. Housley Intended Status: Informational R. Housley
Expires: March 21, 2014 Vigil Security Expires: August 2, 2014 Vigil Security
J. Schaad J. Schaad
Soaring Hawk Consulting Soaring Hawk Consulting
September 17, 2013 January 29, 2014
The application/cms media type The application/cms media type
draft-turner-application-cms-media-type-07.txt draft-turner-application-cms-media-type-08.txt
Abstract Abstract
This document registers the application/cms media types for use with This document registers the application/cms media types for use with
the corresponding CMS (Cryptographic Message Syntax) content types. the corresponding CMS (Cryptographic Message Syntax) content types.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 27 skipping to change at page 4, line 27
tamp-apex-update tamp-apex-update
tamp-apex-update-confirm tamp-apex-update-confirm
tamp-community-update tamp-community-update
tamp-community-update-confirm tamp-community-update-confirm
tamp-sequence-adjust tamp-sequence-adjust
tamp-sequence-adjust-confirm tamp-sequence-adjust-confirm
tamp-error tamp-error
keyPackageReceipt keyPackageReceipt
keyPackageError 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. The optional parameters are case-sensitive.
Encoding considerations: Encoding considerations:
Binary. Binary.
[RFC5652] requires that the outer most encapsulation be [RFC5652] requires that the outer most encapsulation be
ContentInfo. ContentInfo.
Security considerations: Security considerations:
skipping to change at page 6, line 20 skipping to change at page 6, line 15
Interoperability considerations: Interoperability considerations:
See [RFC3274], [RFC4073], [RFC4108], [RFC5083], [RFC5652], See [RFC3274], [RFC4073], [RFC4108], [RFC5083], [RFC5652],
[RFC5914], [RFC5934], [RFC5958], [RFC6031], [RFC6032], and [RFC5914], [RFC5934], [RFC5958], [RFC6031], [RFC6032], and
[ID.housley-keypackage-receipt-n-error]. [ID.housley-keypackage-receipt-n-error].
In all cases, CMS content types are encapsulated within ContentInfo In all cases, CMS content types are encapsulated within ContentInfo
structures [RFC5652]; that is the outer most enveloping structure structures [RFC5652]; that is the outer most enveloping structure
is ContentInfo. is ContentInfo.
When processing a SignedData around any of the inner content type CMS [RFC5652] defines slightly different processing rules for
the [RFC5652] validation rules MUST be used. The PKCS #7 [RFC2315] SignedData than does PKCS #7 [RFC2315]. This media type employs
validation rules MUST NOT be used. the CMS processing rules.
The Content-Type header field of all application/cms objects SHOULD The Content-Type header field of all application/cms objects SHOULD
include the optional "encapsulatingContent" and "innerContent" include the optional "encapsulatingContent" and "innerContent"
parameters. parameters.
The Content-Disposition header field [RFC4021] can also be included The Content-Disposition header field [RFC4021] can also be included
along with Content-Type's optional name parameter. along with Content-Type's optional name parameter.
Published specification: This specification. Published specification: This specification.
 End of changes. 6 change blocks. 
12 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/