@misc{rfc6010,
    series =    {Request for Comments},
    number =    6010,
    howpublished =  {RFC 6010},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC6010},
    url =       {https://www.rfc-editor.org/info/rfc6010},
    author =    {Carl Wallace and Sam Ashmore and Russ Housley},
    title =     {{Cryptographic Message Syntax (CMS) Content Constraints Extension}},
    pagetotal = 38,
    year =      2010,
    month =     sep,
    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{]}},
}