[plasma] FW: New Version Notification for draft-freeman-plasma-requirements-03.txt

Trevor Freeman <trevorf@exchange.microsoft.com> Thu, 23 August 2012 22:50 UTC

Return-Path: <trevorf@exchange.microsoft.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 A8E5921F8581 for <plasma@ietfa.amsl.com>; Thu, 23 Aug 2012 15:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.791
X-Spam-Level:
X-Spam-Status: No, score=-102.791 tagged_above=-999 required=5 tests=[AWL=-0.192, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NReJpkMkFzqe for <plasma@ietfa.amsl.com>; Thu, 23 Aug 2012 15:50:13 -0700 (PDT)
Received: from na01b.map.o365filtering.com (by1c-gls.o365filtering.com [64.4.22.105]) by ietfa.amsl.com (Postfix) with ESMTP id 099DD21F8510 for <plasma@ietf.org>; Thu, 23 Aug 2012 15:50:12 -0700 (PDT)
Received: from BLUSR01CA101.namsdf01.sdf.exchangelabs.com (10.255.124.146) by BLUSR01MB601.namsdf01.sdf.exchangelabs.com (10.255.124.166) with Microsoft SMTP Server (TLS) id 15.0.508.4; Thu, 23 Aug 2012 22:50:10 +0000
Received: from BY1FFOFD004.ffo.gbl (64.4.22.105) by BLUSR01CA101.outlook.com (10.255.124.146) with Microsoft SMTP Server (TLS) id 15.0.508.4 via Frontend Transport; Thu, 23 Aug 2012 22:50:10 +0000
Received: from hybrid.exchange.microsoft.com (131.107.1.27) by BY1FFOFD004.mail.o365filtering.com (10.1.16.61) with Microsoft SMTP Server (TLS) id 15.0.516.0 via Frontend Transport; Thu, 23 Aug 2012 22:50:10 +0000
Received: from df-h14-01.exchange.corp.microsoft.com (157.54.78.139) by DF-G14-02.exchange.corp.microsoft.com (157.54.87.56) with Microsoft SMTP Server (TLS) id 14.3.71.0; Thu, 23 Aug 2012 15:38:04 -0700
Received: from PIO-MLT-06.exchange.corp.microsoft.com (157.54.94.24) by DF-H14-01.exchange.corp.microsoft.com (157.54.78.139) with Microsoft SMTP Server (TLS) id 14.3.71.2; Thu, 23 Aug 2012 15:38:04 -0700
Received: from DF-M14-12.exchange.corp.microsoft.com ([fe80::7c94:4036:120:c95f]) by PIO-MLT-06.exchange.corp.microsoft.com ([fe80::d57f:521a:3ae6:c130%10]) with mapi id 14.03.0083.000; Thu, 23 Aug 2012 15:38:04 -0700
From: Trevor Freeman <trevorf@exchange.microsoft.com>
To: "plasma@ietf.org" <plasma@ietf.org>
Thread-Topic: New Version Notification for draft-freeman-plasma-requirements-03.txt
Thread-Index: AQHNgX/Wdp09laFQIUqlBGgiBjd4fZdn/L/g
Date: Thu, 23 Aug 2012 22:38:03 +0000
Message-ID: <E545B914D50B2A4B994F198378B1525D5B998D1B@DF-M14-12.exchange.corp.microsoft.com>
References: <20120823223639.741.90319.idtracker@ietfa.amsl.com>
In-Reply-To: <20120823223639.741.90319.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.102]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.1.27; IPV:NLI; EFV:FOP; SFV:NSPM; SFS:(377454001)(13464001)(377424002)(42186003)(33656001)(46102001)(16406001)(31966007); DIR:INB; LANG:en;
X-Forefront-PRVS: 0582641F53
X-OriginatorOrg: DuplicateDomain-6c178e33-aecb-4786-8220-9afceeddbaf3.exchange.microsoft.com
Subject: [plasma] FW: New Version Notification for draft-freeman-plasma-requirements-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: Thu, 23 Aug 2012 22:50:14 -0000

I have just published a new requirements draft.

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Thursday, August 23, 2012 3:37 PM
To: Trevor Freeman
Cc: ppatterson@carillon.ca; ietf@augustcellars.com
Subject: New Version Notification for draft-freeman-plasma-requirements-03.txt


A new version of I-D, draft-freeman-plasma-requirements-03.txt
has been successfully submitted by Trevor Freeman and posted to the IETF repository.

Filename:	 draft-freeman-plasma-requirements
Revision:	 03
Title:		 Requirements for Message Access Control
Creation date:	 2012-08-23
WG ID:		 Individual Submission
Number of pages: 59
URL:             http://www.ietf.org/internet-drafts/draft-freeman-plasma-requirements-03.txt
Status:          http://datatracker.ietf.org/doc/draft-freeman-plasma-requirements
Htmlized:        http://tools.ietf.org/html/draft-freeman-plasma-requirements-03
Diff:            http://www.ietf.org/rfcdiff?url2=draft-freeman-plasma-requirements-03

Abstract:
   There are many situations where organizations want to protect
   information with robust access control, either for implementation of
   intellectual property right protections, enforcement of contractual
   confidentiality agreements or because of legal regulations.  The
   Enhanced Security Services (ESS) for S/MIME defines an access control
   mechanism which is enforced by the recipient's client after
   decryption of the message. The ESS mechanism therefore is dependent
   on the correct access policy configuration of every recipient's
   client. This mechanism also provides full access to the data to all
   recipients prior to the access control check, this is considered to
   be inadequate due to the difficulty in demonstrating policy
   compliance.

   This document lays out the deficiencies of the current ESS security
   label, and presents requirements for a new model for doing/providing
   access control to messages where the access check is performed prior
   to message content decryption. This new model also does not require
   policy configuration on the client to simplify deployment and
   compliance verification.

   The proposed model additionally provides a method where non-X.509
   certificate credentials can be used for encryption/decryption of
   S/MIME messages.

                                                                                  


The IETF Secretariat