[plasma] FW: New Version Notification for draft-schaad-plasma-cms-03.txt

"Jim Schaad" <ietf@augustcellars.com> Sat, 12 January 2013 01:17 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: plasma@ietfa.amsl.com
Delivered-To: plasma@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B8AFD21F8645 for <plasma@ietfa.amsl.com>; Fri, 11 Jan 2013 17:17:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id oF2IEseJwUT1 for <plasma@ietfa.amsl.com>; Fri, 11 Jan 2013 17:17:48 -0800 (PST)
Received: from smtp3.pacifier.net (smtp3.pacifier.net []) by ietfa.amsl.com (Postfix) with ESMTP id 169C921F845A for <plasma@ietf.org>; Fri, 11 Jan 2013 17:17:48 -0800 (PST)
Received: from Philemon (mail.augustcellars.com []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id 01DFD38F29 for <plasma@ietf.org>; Fri, 11 Jan 2013 17:17:43 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <plasma@ietf.org>
References: <20130112011253.9137.16504.idtracker@ietfa.amsl.com>
In-Reply-To: <20130112011253.9137.16504.idtracker@ietfa.amsl.com>
Date: Fri, 11 Jan 2013 17:17:24 -0800
Message-ID: <016d01cdf062$94732dd0$bd598970$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGbFlqKpDcUe6GtkZ29ORwEpWolYZiqmFgA
Content-Language: en-us
Subject: [plasma] FW: New Version Notification for draft-schaad-plasma-cms-03.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: Sat, 12 Jan 2013 01:17:48 -0000

New document released.

Moderate amounts of changes I think.


> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Friday, January 11, 2013 5:13 PM
> To: ietf@augustcellars.com
> Subject: New Version Notification for draft-schaad-plasma-cms-03.txt
> A new version of I-D, draft-schaad-plasma-cms-03.txt has been successfully
> submitted by Jim Schaad and posted to the IETF repository.
> Filename:	 draft-schaad-plasma-cms
> Revision:	 03
> Title:		 Plasma Service Cryptographic Message Syntax (CMS)
> Processing
> Creation date:	 2013-01-11
> WG ID:		 Individual Submission
> Number of pages: 39
> URL:             http://www.ietf.org/internet-drafts/draft-schaad-plasma-cms-
> 03.txt
> Status:          http://datatracker.ietf.org/doc/draft-schaad-plasma-cms
> Htmlized:        http://tools.ietf.org/html/draft-schaad-plasma-cms-03
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-schaad-plasma-cms-03
> 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.  A new model for enforcement of policy using a
>    third party is described in RFC TBD
>    [I.D-draft-freeman-plasma-requirements].  This is the Policy
>    Augmented S/MIME (PLASMA) system.  This document provides the details
>    needed to implement the new Plasma model in the CMS infrastructure.
>    An additional benefit of using the Plasma module is that the server,
>    based on policy, manages who has access to the message and how the
>    keys are protected.
>    The document details how the client encryption and decryption
>    processes are performed, defines how to construct the CMS recipient
>    info structure, a new content to hold the data required for the
>    Plasma server to store the keys and policy information.  The document
>    does not cover the protocol between the client and the Plasma policy
>    enforcement server.  One example of the client/server protocol can be
>    found in RFC TBD [plasma-token].
> The IETF Secretariat