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

Yoav Nir <ynir@checkpoint.com> Sun, 14 November 2010 21:29 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 52BCF3A6C41 for <ietf@core3.amsl.com>; Sun, 14 Nov 2010 13:29:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 t7YjzJKkO04M for <ietf@core3.amsl.com>; Sun, 14 Nov 2010 13:29:25 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id E4A473A6B39 for <ietf@ietf.org>; Sun, 14 Nov 2010 13:29:24 -0800 (PST)
X-CheckPoint: {4CE051E4-0-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id oAELTwnX017471; Sun, 14 Nov 2010 23:29:58 +0200
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sun, 14 Nov 2010 23:29:58 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Sun, 14 Nov 2010 23:29:58 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: SM <sm@resistor.net>
Date: Sun, 14 Nov 2010 23:29:57 +0200
Subject: Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets
Thread-Topic: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets
Thread-Index: AcuEQxZfHrPo7y+KQ+mHrq5kefwgOw==
Message-ID: <EFE88DBE-767E-4019-B21D-7F98F07FD852@checkpoint.com>
References: <C902F371.23A288%jordi.palet@consulintel.es> <2C6CC15A-EFCC-4E0B-B4A7-A1C4BD48416B@checkpoint.com> <1289563433.5333.21.camel@shane-asus-laptop> <6.2.5.6.2.20101113221018.0ba26388@resistor.net> <0A4F6C7C-0564-4C20-9360-7B2A505825BB@checkpoint.com> <6.2.5.6.2.20101114083951.0b4f0858@resistor.net>
In-Reply-To: <6.2.5.6.2.20101114083951.0b4f0858@resistor.net>
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: 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: Sun, 14 Nov 2010 21:29:26 -0000

On Nov 14, 2010, at 10:50 PM, SM wrote:

>> enough, because the corruption that we're trying to solve would 
>> require collaboration between the IETF chair and the IAOC. I would 
>> say that the risk is low enough that privacy trumps transparency.
> 
> As you used the term "corruption", I'll go with it. The corruption 
> can be solved by charging everyone, including NOC and hosts, for 
> tickets.

I don't think charging hosts would matter that much. They'd just pay more in tickets and less in sponsorships. But as far as NOC and volunteers are concerned, they definitely deserve the tickets. If we had to hire network people with that skill level for a week, we'd have to pay a lot more than $650. 

>  It is likely that such a solution will increase meeting 
> costs and decrease sponsorship revenue.  

I'd say very likely. 

> The price of the ticket may 
> have to be increased.  This looks more like the law of unintended 
> consequences instead of corruption.

Whenever you give anyone power, there's a risk of corruption. You can never eliminate this risk, but you can reduce it. Reducing the risk costs. It costs money, privacy and time. The same supervision can also reduce waste (such as giving comp tickets to people who don't deserve them). With just a single discretionary comp ticket (or even if it were 10), the waste reduction is a moot point. There's no point in adding any more supervision. And as for corruption, I believe the current safeguards are more than enough to put our minds at ease.