Cryptographic Message Syntax (CMS) Content Constraints Extension
RFC 6010

Document Type RFC - Proposed Standard (September 2010; Errata)
Was draft-housley-cms-content-constraints-extn (individual in sec area)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 6010 (Proposed Standard)
Telechat date
Responsible AD Tim Polk
Send notices to housley@vigilsec.com, cwallace@cygnacom.com, srashmo@radium.ncsc.mil, draft-housley-cms-content-constraints-extn@ietf.org, GBeier@cygnacom.com
Internet Engineering Task Force (IETF)                        R. Housley
Request for Comments: 6010                           Vigil Security, LLC
Category: Standards Track                                     S. Ashmore
ISSN: 2070-1721                                 National Security Agency
                                                              C. Wallace
                                                      Cygnacom Solutions
                                                          September 2010

    Cryptographic Message Syntax (CMS) Content Constraints Extension

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6010.

Housley, et al.              Standards Track                    [Page 1]
RFC 6010                 CMS Content Constraints          September 2010

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Housley, et al.              Standards Track                    [Page 2]
RFC 6010                 CMS Content Constraints          September 2010

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  CMS Data Structures  . . . . . . . . . . . . . . . . . . .  5
     1.2.  CMS Content Constraints Model  . . . . . . . . . . . . . . 10
     1.3.  Attribute Processing . . . . . . . . . . . . . . . . . . . 11
     1.4.  Abstract Syntax Notation . . . . . . . . . . . . . . . . . 13
     1.5.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . 13
   2.  CMS Content Constraints Extension  . . . . . . . . . . . . . . 13
   3.  Certification Path Processing  . . . . . . . . . . . . . . . . 16
     3.1.  Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     3.2.  Initialization . . . . . . . . . . . . . . . . . . . . . . 18
     3.3.  Basic Certificate Processing . . . . . . . . . . . . . . . 19
     3.4.  Preparation for Certificate i+1  . . . . . . . . . . . . . 20
     3.5.  Wrap-Up Procedure  . . . . . . . . . . . . . . . . . . . . 20
     3.6.  Outputs  . . . . . . . . . . . . . . . . . . . . . . . . . 21
Show full document text