Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets

Shane Kerr <shane@isc.org> Fri, 12 November 2010 12:03 UTC

Return-Path: <shane@isc.org>
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 9A7E13A69D7; Fri, 12 Nov 2010 04:03:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.15
X-Spam-Level:
X-Spam-Status: No, score=-2.15 tagged_above=-999 required=5 tests=[AWL=0.450, 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 ob5W3wtYeJAN; Fri, 12 Nov 2010 04:03:36 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by core3.amsl.com (Postfix) with ESMTP id B7C6B3A69D0; Fri, 12 Nov 2010 04:03:36 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 252B65F983B; Fri, 12 Nov 2010 12:03:59 +0000 (UTC) (envelope-from shane@isc.org)
Received: from [IPv6:2001:610:719:1:221:5dff:fe1e:113a] (unknown [IPv6:2001:610:719:1:221:5dff:fe1e:113a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by farside.isc.org (Postfix) with ESMTP id 312E4E6030; Fri, 12 Nov 2010 12:03:56 +0000 (UTC) (envelope-from shane@isc.org)
Subject: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets
From: Shane Kerr <shane@isc.org>
To: Yoav Nir <ynir@checkpoint.com>
In-Reply-To: <2C6CC15A-EFCC-4E0B-B4A7-A1C4BD48416B@checkpoint.com>
References: <C902F371.23A288%jordi.palet@consulintel.es> <2C6CC15A-EFCC-4E0B-B4A7-A1C4BD48416B@checkpoint.com>
Content-Type: text/plain; charset="UTF-8"
Organization: ISC
Date: Fri, 12 Nov 2010 13:03:53 +0100
Message-ID: <1289563433.5333.21.camel@shane-asus-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3
Content-Transfer-Encoding: 7bit
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, 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: Fri, 12 Nov 2010 12:03:37 -0000

Yoav,

On Fri, 2010-11-12 at 11:08 +0200, Yoav Nir wrote:
> On Nov 12, 2010, at 7:36 AM, JORDI PALET MARTINEZ wrote:
>
> > I don't agree. If there is people "essential" to the meeting but can't pay,
> > as we all pay for that, we have the right to know.
> 
> I disagree with that. There is a privacy issue here. If x can't pay
> his way, and needs a comp ticket, it's enough that the IETF chair
> knows about this. It's not our right to know of their financial
> situation.

While I don't agree that we have a "right" to know who is getting free
access to IETF meetings, I do agree with Jordi that it seems like a
reasonable thing to make public.

Sometimes transparency trumps privacy. This is especially true when
money is changing hands (or not changing hands, in this case).

For example, in some elections if you want to be a candidate you must
publish part of you your finances (for example, your tax records). This
is to prevent corruption. Some people refuse to do this, and so may not
run for office.

It is sometimes possible to create systems to meet the needs of privacy
and oversight - for example a closed review board - but I think just
publishing a list of who gets free access to each IETF is probably good
a good idea.

Cheers,

--
Shane