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

Trevor Freeman <trevorf@exchange.microsoft.com> Tue, 20 August 2013 21:20 UTC

From: Trevor Freeman <trevorf@exchange.microsoft.com>
To: "plasma@ietf.org" <plasma@ietf.org>
Thread-Topic: New Version Notification for draft-freeman-plasma-requirements-07.txt
Thread-Index: AQHOnej9KaRtVIkCJ0uSO2IdN/3WQ5memWYw
Date: Tue, 20 Aug 2013 21:18:55 +0000
Message-ID: <f970bb604c444233a2da52f606e37be1@DFM-TK5MBX15-05.exchange.corp.microsoft.com>
References: <20130820210444.6582.32152.idtracker@ietfa.amsl.com>
In-Reply-To: <20130820210444.6582.32152.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [plasma] FW: New Version Notification for draft-freeman-plasma-requirements-07.txt
Precedence: list

FYI, a new requirements draft was just posted. This has the updates requested by the document shepherd. 

Final stretch now. 

Trevor

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Tuesday, August 20, 2013 2:05 PM
To: Patrick Patterson; Jim Schaad; Trevor Freeman
Subject: New Version Notification for draft-freeman-plasma-requirements-07.txt

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

Filename:	 draft-freeman-plasma-requirements
Revision:	 07
Title:		 Requirements for Message Access Control
Creation date:	 2013-08-20
Group:		 Individual Submission
Number of pages: 60
URL:             http://www.ietf.org/internet-drafts/draft-freeman-plasma-requirements-07.txt
Status:          http://datatracker.ietf.org/doc/draft-freeman-plasma-requirements
Htmlized:        http://tools.ietf.org/html/draft-freeman-plasma-requirements-07
Diff:            http://www.ietf.org/rfcdiff?url2=draft-freeman-plasma-requirements-07

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 for email 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, which is considered to
   be inadequate for robust access control 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 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 thereby simplifying 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.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

[plasma] FW: New Version Notification for draft-f… Trevor Freeman