Re: IETF privacy policy - update

joel jaeggli <joelja@bogus.com> Thu, 08 July 2010 06:30 UTC

Return-Path: <joelja@bogus.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 D5B443A6898 for <ietf@core3.amsl.com>; Wed, 7 Jul 2010 23:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 vdNJzTseKOxn for <ietf@core3.amsl.com>; Wed, 7 Jul 2010 23:30:28 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id D818A3A6818 for <ietf@ietf.org>; Wed, 7 Jul 2010 23:30:26 -0700 (PDT)
Received: from [172.16.192.186] (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o686UGPO082028 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 8 Jul 2010 06:30:21 GMT (envelope-from joelja@bogus.com)
Message-ID: <4C355DE5.5010103@bogus.com>
Date: Wed, 07 Jul 2010 22:11:01 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: IETF privacy policy - update
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> <p06240828c85a8b88005c@[10.20.30.158]>
In-Reply-To: <p06240828c85a8b88005c@[10.20.30.158]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Thu, 08 Jul 2010 06:30:23 +0000 (UTC)
Cc: 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 06:30:32 -0000

On 2010-07-07 12:59, Paul Hoffman wrote:
>
> Do some people not come to IETF meetings because of the current null
> privacy policy?

Do some people not come because attendance is a matter of public record?

> Do they say less than they would have if we had a
> typical non-null policy?

do people not speak or participate, due to the note well, audio 
recording in the meeting rooms or the mailing list policy?

> If either of those two are answered yes,
> would those people contribute better knowing that the IETF had a
> policy but no real way to enforce it other than by apologizing when
> it failed to follow the policy?

practices that result in the retention of pii information seem by in 
large fairly well documented as part of the ietf process (consider 
nomcom for example).

to the extent that there are gaps they appear to be associated with 
secretarial tasks not with the ietf activity itself which by in large 
favors transparency through publication.

> If having a privacy policy, even one where there was no real
> enforcement mechanism, was free, nearly everyone would want it. Given
> that getting such a policy is not free, and will cause cycles to be
> lost from other IETF work, is the tradeoff worth it? At this point, I
> would say "no", but mostly because I don't know of anyone who
> contributes less due to the current null policy.
>
> --Paul Hoffman, Director --VPN Consortium
> _______________________________________________ Ietf mailing list
> Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
>