[ietf-privacy] Fwd: New Version Notification for draft-cooper-ietf-privacy-requirements-00.txt

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 20 September 2013 16:34 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2F4821F8E85 for <ietf-privacy@ietfa.amsl.com>; Fri, 20 Sep 2013 09:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.049
X-Spam-Level:
X-Spam-Status: No, score=-103.049 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 z9pzduemdEbj for <ietf-privacy@ietfa.amsl.com>; Fri, 20 Sep 2013 09:34:39 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1D42921F9A3D for <ietf-privacy@ietf.org>; Fri, 20 Sep 2013 09:34:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 5FBECBE50 for <ietf-privacy@ietf.org>; Fri, 20 Sep 2013 17:34:27 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PSIJbiOiOaWH for <ietf-privacy@ietf.org>; Fri, 20 Sep 2013 17:34:27 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id CA5C2BE79 for <ietf-privacy@ietf.org>; Fri, 20 Sep 2013 17:34:26 +0100 (IST)
Message-ID: <523C7912.1060206@cs.tcd.ie>
Date: Fri, 20 Sep 2013 17:34:26 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: "ietf-privacy@ietf.org" <ietf-privacy@ietf.org>
References: <20130920162352.23295.48024.idtracker@ietfa.amsl.com>
In-Reply-To: <20130920162352.23295.48024.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.2
X-Forwarded-Message-Id: <20130920162352.23295.48024.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [ietf-privacy] Fwd: New Version Notification for draft-cooper-ietf-privacy-requirements-00.txt
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-privacy>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Sep 2013 16:34:44 -0000

FYI. Comments welcome,

S.


-------- Original Message --------
Subject: New Version Notification for
draft-cooper-ietf-privacy-requirements-00.txt
Date: Fri, 20 Sep 2013 09:23:52 -0700
From: internet-drafts@ietf.org
To: Alissa Cooper <acooper@cdt.org>, Sean Turner <turners@ieca.com>,
Stephen Farrell <stephen.farrell@cs.tcd.ie>


A new version of I-D, draft-cooper-ietf-privacy-requirements-00.txt
has been successfully submitted by Alissa Cooper and posted to the
IETF repository.

Filename:	 draft-cooper-ietf-privacy-requirements
Revision:	 00
Title:		 Privacy Requirements for IETF Protocols
Creation date:	 2013-09-20
Group:		 Individual Submission
Number of pages: 11
URL:
http://www.ietf.org/internet-drafts/draft-cooper-ietf-privacy-requirements-00.txt
Status:
http://datatracker.ietf.org/doc/draft-cooper-ietf-privacy-requirements
Htmlized:
http://tools.ietf.org/html/draft-cooper-ietf-privacy-requirements-00


Abstract:
   It is the consensus of the IETF that IETF protocols be designed to
   avoid privacy violations to the extent possible.  This document
   establishes a number of protocol design choices as Best Current
   Practices for the purpose of avoiding such violations.





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