Re: IETF privacy policy - update

Ole Jacobsen <ole@cisco.com> Wed, 07 July 2010 19:55 UTC

Return-Path: <ole@cisco.com>
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 BE9C23A697D for <ietf@core3.amsl.com>; Wed, 7 Jul 2010 12:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.166
X-Spam-Level:
X-Spam-Status: No, score=-10.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 EjJE82Nhxp+3 for <ietf@core3.amsl.com>; Wed, 7 Jul 2010 12:55:40 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 5D4873A6979 for <ietf@ietf.org>; Wed, 7 Jul 2010 12:55:39 -0700 (PDT)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPt3NEyrR7Hu/2dsb2JhbACgF3GleIF9CwGYXYJSglIEg3iERYkm
X-IronPort-AV: E=Sophos;i="4.53,554,1272844800"; d="scan'208";a="229680155"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 07 Jul 2010 19:55:41 +0000
Received: from pita.cisco.com (pita.cisco.com [171.71.177.199]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o67JtfuQ013334; Wed, 7 Jul 2010 19:55:41 GMT
Date: Wed, 07 Jul 2010 12:53:28 -0700
From: Ole Jacobsen <ole@cisco.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: IETF privacy policy - update
In-Reply-To: <tsl630r6pj1.fsf@mit.edu>
Message-ID: <Pine.GSO.4.63.1007071250260.20133@pita.cisco.com>
References: <7022DEA1-7FC0-4D77-88CE-FA3788720B43@cdt.org> <8FBEA0C7-9B80-4860-AFAE-FB5A19E660EF@muada.com> <4C33A406.1090801@bogus.com> <BBDFC939-2109-41BB-B4E1-BE2CEE43B8CA@muada.com> <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>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
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: Wed, 07 Jul 2010 19:55:40 -0000

Sam,

I view this more or less as "standard boilerplate", something you find 
in a lot of "online places". I think it is reasonable to expect that 
if you register for a meeting your personal info (e-mail address 
mostly) won't be sold/used/harvested by someone for purposes other 
than what you think you signed up for. It's probably useful for us to 
have such a statement.

Ole

On Wed, 7 Jul 2010, Sam Hartman wrote:
> 
> Generally when I look for an idea of whether work is a good idea I look
> for a clear statement of benefit.  I'll admit that I don't find privacy
> policies so valuable that I think everyone should have one.  So, I'll
> ask how will or work be improved or what problem are we running into
> that a privacy policy will solve?  If that cannot clearly we be
> answered, we should not engage in this activity.