RE: IETF privacy policy - update

Yoav Nir <ynir@checkpoint.com> Thu, 08 July 2010 08:58 UTC

Return-Path: <ynir@checkpoint.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 1540D3A69F9 for <ietf@core3.amsl.com>; Thu, 8 Jul 2010 01:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level:
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.434, BAYES_00=-2.599]
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 6OzG5+mhRGP5 for <ietf@core3.amsl.com>; Thu, 8 Jul 2010 01:58:44 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id 1B9C83A688E for <ietf@ietf.org>; Thu, 8 Jul 2010 01:58:43 -0700 (PDT)
X-CheckPoint: {4C359FDD-0-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.12.10+Sun/8.12.10) with ESMTP id o688wfDq029487; Thu, 8 Jul 2010 11:58:41 +0300 (IDT)
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 8 Jul 2010 11:59:13 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: 'joel jaeggli' <joelja@bogus.com>, Ole Jacobsen <ole@cisco.com>
Date: Thu, 08 Jul 2010 11:59:12 +0300
Subject: RE: IETF privacy policy - update
Thread-Topic: IETF privacy policy - update
Thread-Index: AcseHWX/mvekO22CS6eXH/8RQ5S+ZwAXb8Sg
Message-ID: <006FEB08D9C6444AB014105C9AEB133FFE28C51DD8@il-ex01.ad.checkpoint.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> <Pine.GSO.4.63.1007071250260.20133@pita.cisco.com> <4C34F4BB.4040907@bogus.com>
In-Reply-To: <4C34F4BB.4040907@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, Sam Hartman <hartmans-ietf@mit.edu>, IETF-Discussion list <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 08:58:45 -0000

On July 08, 2010 12:42 AM joel jaeggli wrote:

> On 2010-07-07 12:53, Ole Jacobsen wrote:
>>
>> 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.
>
> the fact that you signed up for the meeting is publicly available so 
> that we don't sell mailing lists to spammers seems sort of irrelevant.

This is the way things are *now*. Discussion of a privacy statement may lead to changes, such as keeping the attendee list confidential, and destroying it on the Monday following the meeting.

I personally don't care if the whole world knows I've been to an IETF meeting, but the decision to publish the list on the website has privacy consequences. Without a privacy policy, it's hard to say whether that is acceptable or not.