Do Not Track -- was Re: Privacy, Integrity, Security mailing-list invitation

Hannes Tschofenig <hannes.tschofenig@gmx.net> Thu, 17 March 2011 08:16 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADA693A6A66 for <ietf@core3.amsl.com>; Thu, 17 Mar 2011 01:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.099
X-Spam-Level:
X-Spam-Status: No, score=-104.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, GB_I_INVITATION=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAZRW5NG9bWA for <ietf@core3.amsl.com>; Thu, 17 Mar 2011 01:16:36 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 670093A6834 for <ietf@ietf.org>; Thu, 17 Mar 2011 01:16:36 -0700 (PDT)
Received: (qmail invoked by alias); 17 Mar 2011 08:18:02 -0000
Received: from unknown (EHLO [10.255.138.128]) [192.100.123.77] by mail.gmx.net (mp004) with SMTP; 17 Mar 2011 09:18:02 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19SHfZbYSJSUZLLZ0m2PxPPCU+c+gYTCGn7AZIQGZ kDBeeyQm76we9/
Subject: Do Not Track -- was Re: Privacy, Integrity, Security mailing-list invitation
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <AANLkTinR5sGDiznYNODRs749vqcaQMVi0PbPpq_gK7hi@mail.gmail.com>
Date: Thu, 17 Mar 2011 10:17:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <43BAC3CC-81B6-4AE6-9E46-8FB4B2845477@gmx.net>
References: <362AAF22-7F7A-4E21-A83B-26E84E39CD90@softarmor.com> <77312780-B2EF-4FF3-8E07-F9EDA3419739@gmx.net> <AANLkTinR5sGDiznYNODRs749vqcaQMVi0PbPpq_gK7hi@mail.gmail.com>
To: Paul Ferguson <fergdawgster@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 08:16:37 -0000

https://www.ietf.org/mailman/listinfo/ietf-privacy would be a good place to have Do Not Track discussions. 

Discussions were started there already on that list, see http://www.ietf.org/mail-archive/web/ietf-privacy/current/msg00004.html

Two IETF drafts on that topic are available: 
http://tools.ietf.org/html/draft-cooper-web-tracking-opt-outs-00
http://www.ietf.org/id/draft-mayer-do-not-track-00.txt

Ciao
Hannes

On Mar 17, 2011, at 10:10 AM, Paul Ferguson wrote:

> I suppose the inevitable question would be: Is this the appropriate
> venue for discussions surrounding the efforts to create a "Do Not
> Track" (mumble)?
> 
> - ferg
> 
> On Thu, Mar 17, 2011 at 1:06 AM, Hannes Tschofenig
> <hannes.tschofenig@gmx.net> wrote:
> 
>> Hi Dean,
>> 
>> since you asked:
>> 
>>> 1) What is different about this exercise from the ongoing privacy discussion on privacy@iab.org/ietf-privacy@ietf.org?
>> 
>> 
>> A) privacy@iab.org
>> 
>> The privacy@iab.org was a mailing list created for the IAB privacy workshop:
>> http://www.iab.org/about/workshops/privacy/
>> 
>> It was used by the workshop organizers only.  It will be deleted soon.
>> 
>> B) ietf-privacy@ietf.org
>> 
>> This mailing list has been set up to discuss issues related to privacy that cut across multiple groups and areas.
>> 
>> The initial goal of this discussion is to investigate privacy and related identity management terminology. A secondary goal is to explore the opportunity to develop "Privacy Consideration" guidelines similar to the "Guidelines for Writing RFC Text on Security Considerations" [RFC3552] used in the security area.
>> 
>> To subscribe go to: https://www.ietf.org/mailman/listinfo/ietf-privacy
>> 
>> C) privacydir@ietf.org
>> 
>> There is a privacy directorate created as a result of last year's privacy workshop.
>> Membership (like the security area directorate): per-invitation only.
>> 
>> Ciao
>> Hannes
>> 
>> PS: It would be nice to get review comments on the privacy terminology, the privacy considerations, and policy considerations document:
>> http://tools.ietf.org/html/draft-hansen-privacy-terminology-02
>> http://tools.ietf.org/html/draft-morris-privacy-considerations-02
>> http://tools.ietf.org/html/draft-morris-policy-cons-00
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>> 
> 
> 
> 
> -- 
> "Fergie", a.k.a. Paul Ferguson
>  Engineering Architecture for the Internet
>  fergdawgster(at)gmail.com
>  ferg's tech blog: http://fergdawg.blogspot.com/