[smime] Fwd: RFC 6010 on Cryptographic Message Syntax (CMS) Content Constraints Extension
Paul Hoffman <paul.hoffman@vpnc.org> Fri, 17 September 2010 00:35 UTC
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: smime@core3.amsl.com
Delivered-To: smime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F66F3A6B40 for <smime@core3.amsl.com>; Thu, 16 Sep 2010 17:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.976
X-Spam-Level:
X-Spam-Status: No, score=-100.976 tagged_above=-999 required=5 tests=[AWL=0.470, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_93=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSL9DMne7rsF for <smime@core3.amsl.com>; Thu, 16 Sep 2010 17:35:28 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id D52C93A6BA4 for <smime@ietf.org>; Thu, 16 Sep 2010 17:35:26 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o8H0Zn4g082522 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <smime@ietf.org>; Thu, 16 Sep 2010 17:35:50 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624083fc8b86851757d@[10.20.30.158]>
Date: Thu, 16 Sep 2010 17:35:48 -0700
To: smime@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [smime] Fwd: RFC 6010 on Cryptographic Message Syntax (CMS) Content Constraints Extension
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 00:35:29 -0000
>X-Original-To: ietf-announce@core3.amsl.com >Delivered-To: ietf-announce@core3.amsl.com >X-Virus-Scanned: amavisd-new at amsl.com >X-Spam-Flag: NO >X-Spam-Score: -102.099 >X-Spam-Level: >X-Spam-Status: No, score=-102.099 tagged_above=-999 required=5 > tests=[AWL=-0.099, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, > NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] >To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org >Subject: RFC 6010 on Cryptographic Message Syntax (CMS) Content Constraints > Extension >From: rfc-editor@rfc-editor.org >Date: Thu, 16 Sep 2010 16:08:30 -0700 (PDT) >Cc: rfc-editor@rfc-editor.org >X-BeenThere: ietf-announce@ietf.org >X-Mailman-Version: 2.1.9 >List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org> >List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, > <mailto:ietf-announce-request@ietf.org?subject=unsubscribe> >List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce> >List-Post: <mailto:ietf-announce@ietf.org> >List-Help: <mailto:ietf-announce-request@ietf.org?subject=help> >List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, > <mailto:ietf-announce-request@ietf.org?subject=subscribe> >Sender: ietf-announce-bounces@ietf.org > > >A new Request for Comments is now available in online RFC libraries. > > > RFC 6010 > > Title: Cryptographic Message Syntax (CMS) Content > Constraints Extension > Author: R. Housley, S. Ashmore, > C. Wallace > Status: Standards Track > Stream: IETF > Date: September 2010 > Mailbox: housley@vigilsec.com, > srashmo@radium.ncsc.mil, > cwallace@cygnacom.com > Pages: 38 > Characters: 87495 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-housley-cms-content-constraints-extn-06.txt > > URL: http://www.rfc-editor.org/rfc/rfc6010.txt > >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] > >This is now a Proposed Standard Protocol. > >STANDARDS TRACK: This document specifies an Internet standards track >protocol for the Internet community,and requests discussion and suggestions >for improvements. Please refer to the current edition of the Internet >Official Protocol Standards (STD 1) for the standardization state and >status of this protocol. Distribution of this memo is unlimited. > >This announcement is sent to the IETF-Announce and rfc-dist lists. >To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > >For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. >For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > >Requests for special distribution should be addressed to either the >author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution. > > >The RFC Editor Team >Association Management Solutions, LLC
- [smime] Fwd: RFC 6010 on Cryptographic Message Sy… Paul Hoffman