RFC 6010: Cryptographic Message Syntax (CMS) Content Constraints Extension
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC6010
- Published
- September 2010
- Authors
- R. Housley; S. Ashmore; C. Wallace
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 38
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3779X.509 Extensions for IP Addresses and AS IdentifiersCurrent
June 2004
- RFC 8555Automatic Certificate Management Environment (ACME)Current
March 2019
- RFC 8659DNS Certification Authority Authorization (CAA) Resource RecordCurrent
November 2019
- RFC 9773ACME Renewal Information (ARI) ExtensionCurrent
June 2025
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
- RFC 5849The OAuth 1.0 ProtocolObsoleted
April 2010
- RFC 5779Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter ServerCurrent
February 2010
- RFC 5758Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSACurrent
January 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?