database logo graphic

RFC 6010

"Cryptographic Message Syntax (CMS) Content Constraints Extension", September 2010

Canonical URL:
http://www.rfc-editor.org/rfc/rfc6010.txt
This document is also available in this non-normative format: PDF.
Status:
PROPOSED STANDARD
Authors:
R. Housley
S. Ashmore
C. Wallace
Stream:
IETF
Source:
NON WORKING GROUP

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

This document specifies the syntax and semantics for the Cryptographic Message Syntax (CMS) content constraints extension. This extension is used to determine whether a public key is appropriate to use in the processing of a protected content. In particular, the CMS content constraints extension is one part of the authorization decision; it is used when validating a digital signature on a CMS SignedData content or validating a message authentication code (MAC) on a CMS AuthenticatedData content or CMS AuthEnvelopedData content. The signed or authenticated content type is identified by an ASN.1 object identifier, and this extension indicates the content types that the public key is authorized to validate. If the authorization check is successful, the CMS content constraints extension also provides default values for absent attributes. [STANDARDS-TRACK]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Go to the RFC Editor Homepage.