[plasma] FW: New Version Notification for draft-schaad-plasma-cms-00.txt
"Jim Schaad" <ietf@augustcellars.com> Mon, 12 March 2012 22:39 UTC
Return-Path: <ietf@augustcellars.com>
X-Original-To: plasma@ietfa.amsl.com
Delivered-To: plasma@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 348FE21E8111 for <plasma@ietfa.amsl.com>; Mon, 12 Mar 2012 15:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.413
X-Spam-Level:
X-Spam-Status: No, score=-3.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ytpspEdT6BwF for <plasma@ietfa.amsl.com>; Mon, 12 Mar 2012 15:39:49 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id A666F21E803C for <plasma@ietf.org>; Mon, 12 Mar 2012 15:39:49 -0700 (PDT)
Received: from Tobias (173-160-230-153-Washington.hfc.comcastbusiness.net [173.160.230.153]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 8E22B38F04 for <plasma@ietf.org>; Mon, 12 Mar 2012 15:39:49 -0700 (PDT)
From: Jim Schaad <ietf@augustcellars.com>
To: plasma@ietf.org
References: <20120309044708.16435.73362.idtracker@ietfa.amsl.com>
In-Reply-To: <20120309044708.16435.73362.idtracker@ietfa.amsl.com>
Date: Mon, 12 Mar 2012 15:39:02 -0700
Message-ID: <000601cd00a0$eccb5b90$c66212b0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEecYSML+s3+LOCCRryxsRcINKmiJfEXr2g
Content-Language: en-us
X-Mailman-Approved-At: Mon, 12 Mar 2012 15:48:34 -0700
Subject: [plasma] FW: New Version Notification for draft-schaad-plasma-cms-00.txt
X-BeenThere: plasma@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The PoLicy Augmented S/Mime \(plasma\) bof discussion list." <plasma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/plasma>, <mailto:plasma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/plasma>
List-Post: <mailto:plasma@ietf.org>
List-Help: <mailto:plasma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/plasma>, <mailto:plasma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2012 22:39:50 -0000
Updated version of this draft is now out. Please note the change of name. > -----Original Message----- > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > Sent: Thursday, March 08, 2012 8:47 PM > To: ietf@augustcellars.com > Subject: New Version Notification for draft-schaad-plasma-cms-00.txt > > A new version of I-D, draft-schaad-plasma-cms-00.txt has been successfully > submitted by Jim Schaad and posted to the IETF repository. > > Filename: draft-schaad-plasma-cms > Revision: 00 > Title: Plasma Service CMS Processing > Creation date: 2012-03-02 > WG ID: Individual Submission > Number of pages: 35 > > Abstract: > Secure Mime (S/MIME) defined a method of placing security labels on a > Cryptographic Message Syntax (CMS) object. These labels are placed > as part of the data signed and validated by the parties. This means > that the message content is visible to the recipient prior to the > label enforcement. In [EPS-WS-TRUST] a new model has been presented > where a third party is used as the enforcement point of the label. > This document provides the details needed to implement the new Plasma > model in the CMS infrastructure. > > Additional benefits of using the Plasma module include moving > responsibility of building lock boxes to the server and determining, > based on policy, who should be a message recipient. > > The document describes and details how the encryption process is > performed, defines a new lock box attribute to hold the information > needed to valid the label and to obtain the keys needed to decrypt > the message. The document does not cover the protocol between the > client and the Plasma policy enforcement server. > > > > > The IETF Secretariat