Re: What does a privacy policy mean?

Phillip Hallam-Baker <hallam@gmail.com> Mon, 26 July 2010 15:37 UTC

Return-Path: <hallam@gmail.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 176113A68F3 for <ietf@core3.amsl.com>; Mon, 26 Jul 2010 08:37:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.957
X-Spam-Level:
X-Spam-Status: No, score=-1.957 tagged_above=-999 required=5 tests=[AWL=0.642, 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 Y2KioWF6XgYl for <ietf@core3.amsl.com>; Mon, 26 Jul 2010 08:36:54 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 72D353A6B97 for <ietf@ietf.org>; Mon, 26 Jul 2010 08:36:43 -0700 (PDT)
Received: by gxk1 with SMTP id 1so1072173gxk.31 for <ietf@ietf.org>; Mon, 26 Jul 2010 08:36:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2Lja8O8DQ2GP1BsJUofr7ey2quA7ChoV5dHR1WEJWVo=; b=YfcCmGqWHfyDa5dNsVvv8azSemqTxslbduG3NC1iY8pKEL5rN0t9Yuwioo0y/EuSup OG1/NjSit1mQ8lZh24jsCZeJlx8v5Pkaj95I2PkK4AJI4D17PhkLUiio8WeqmIVGypgp RvmaG2VxiMbycgUEllfaFD19NzeOc6TaD2Vpk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TKtito+y3Cp0HnhIxdlXUd5lCio7jPWPlDC0/c/eQu+q4QLKjxllIUi1ChMYDYiR3w lIDHoQw2cjpe5w3O6vjS++VSAT24+fcfz+WlhY99iV9i1eAGHy7Y7EvyGqi4fRAQd8CV qW0HCGLP2w+zdHIir/DJrB2DZ8FA8Es5XJXFQ=
MIME-Version: 1.0
Received: by 10.100.232.7 with SMTP id e7mr1982474anh.133.1280158599610; Mon, 26 Jul 2010 08:36:39 -0700 (PDT)
Received: by 10.100.163.9 with HTTP; Mon, 26 Jul 2010 08:36:39 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1007242102340.1584@joyce.lan>
References: <20100721223355.1728.qmail@joyce.lan> <CF9D8943-5A46-4BCA-9A2A-27CBFFA04038@cisco.com> <alpine.BSF.2.00.1007241831100.1584@joyce.lan> <F55D8B96-1D35-414D-8CB9-D4DFC641C14C@cisco.com> <alpine.BSF.2.00.1007242102340.1584@joyce.lan>
Date: Mon, 26 Jul 2010 11:36:39 -0400
Message-ID: <AANLkTi=4jnd88EpqAbqnKt3nf1gKjdBieNmEtyEVeAMU@mail.gmail.com>
Subject: Re: What does a privacy policy mean?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "John R. Levine" <johnl@iecc.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 27 Jul 2010 23:38:07 -0700
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: Mon, 26 Jul 2010 15:37:05 -0000

I would prefer it if the IETF stopped publishing the phone numbers of
every IETF attendee for IETF 52, and quite possibly some other
meetings as well.

This would appear to me to be a privacy issue.


On Sat, Jul 24, 2010 at 9:37 PM, John R. Levine <johnl@iecc.com> wrote:
>> What I don't understand is the amount of arm wrestling that happens on
>> this list.
>
> You're certainly right, there's a culture of nitpicking.  In this case I
> think some of the issues are nitpicks, while some are significant.  The IETF
> is very peculiarly organized, which suggests that it would need a somewhat
> peculiar privacy policy.  Here are some questions that I think are not nits:
>
> Although the IETF per se has no legal existence, ISOC, the IETF Trust, and
> perhaps other things I haven't noticed do.  How should an IETF privacy
> policy relate to the ISOC's existing privacy policy?  Does the IETF Trust
> need a privacy policy?
>
> The IETF potentially collects PII in various ways, including publication of
> Internet Drafts and RFCs, messages on mailing lists, registration info for
> meetings, and activities in meetings.  Meeting activites include paper
> documents (meeting attendance sheets), electronic session presentation
> material, oral session material which is transmitted over the voice feeds,
> jabber chats, and random traffic sent over meeting networks.  Are there
> other forms of PII?  Should a privacy policy treat them all the same, or
> differently?
>
> Some people have argued that it should be possible to participate in some or
> all IETF processes while remaining partly or completely anonymous.  Is this
> a reasonable expectation?
>
> R's,
> John
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



-- 
Website: http://hallambaker.com/