Re: IETF privacy policy - update

Melinda Shore <shore@arsc.edu> Thu, 08 July 2010 19:15 UTC

Return-Path: <shore@arsc.edu>
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 84AE23A6B4F for <ietf@core3.amsl.com>; Thu, 8 Jul 2010 12:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 1zmhO2J92RBJ for <ietf@core3.amsl.com>; Thu, 8 Jul 2010 12:14:58 -0700 (PDT)
Received: from arsc.edu (mail1.arsc.edu [IPv6:2001:480:150:75::229]) by core3.amsl.com (Postfix) with ESMTP id 458E83A68AC for <ietf@ietf.org>; Thu, 8 Jul 2010 12:14:57 -0700 (PDT)
Received: from viking-e0.arsc.edu (viking-e0.arsc.edu [IPv6:2001:480:150:75:223:32ff:feda:4a52]) by arsc.edu (20090828.ARSC) with ESMTP id o68JEw6c011829; Thu, 8 Jul 2010 11:14:58 -0800 (AKDT)
Subject: Re: IETF privacy policy - update
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Melinda Shore <shore@arsc.edu>
In-Reply-To: <AANLkTil6c3toAAkHJ814LPV82uVs8wv_1WKPigBCoJBY@mail.gmail.com>
Date: Thu, 08 Jul 2010 11:14:55 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <00E561BD-949B-427A-ADAF-44D21D1E7481@arsc.edu>
References: <9C72FA78-C9C2-4719-9BFD-112ABEFA7117@cdt.org> <56522CF0-088B-4027-AF45-A6075A7EA666@muada.com> <51D591B3-1954-47A6-A40A-7DCE6DDD5CF0@cdt.org> <A68985E3-A34B-47AB-A6A2-E6718E505652@muada.com> <B75D4F49-2361-4706-A24A-D5E7026EE58D@cdt.org> <573C3FFA-B8CA-4B71-9128-07863DF1CF2B@muada.com> <tsl630r6pj1.fsf@mit.edu> <Pine.GSO.4.63.1007071250260.20133@pita.cisco.com> <4C34F4BB.4040907@bogus.com> <006FEB08D9C6444AB014105C9AEB133FFE28C51DD8@il-ex01.ad.checkpoint.com> <20100708151534.GC63066@shinkuro.com> <25062F4E-3CE7-4EBD-A5BF-4CE26A0E9079@americafree.tv> <AANLkTil6c3toAAkHJ814LPV82uVs8wv_1WKPigBCoJBY@mail.gmail.com>
To: jean-michel bernier de portzamparc <jmabdp@gmail.com>
X-Mailer: Apple Mail (2.1081)
X-CanIt-Geo: No geolocation information available for 2001:480:150:75:223:32ff:feda:4a52
X-CanItPRO-Stream: default
X-Canit-Stats-ID: Bayes signature not available
X-Scanned-By: CanIt (www . roaringpenguin . com) on IPv6:2001:480:150:75::167
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, 08 Jul 2010 19:15:00 -0000

On Jul 8, 2010, at 11:05 AM, jean-michel bernier de portzamparc wrote:
> However, from our own JEDI's (so-labelled "Jefsey's disciples") experience I would suggest some kind of "ietf privacy netiquette". It could be equivalen to architectural quotes like "dumb network", "end to end", "protocol on the wire", "rough consensus", etc. 

I'm not sure I'd want to go the good-soundbite-but-low-
compliance route.  Either writing it up and making it
explicit or dropping it completely and never again
speaking of it seem like better options and likely
to lead to fewer problems in the future.

Melinda