Re: Future Handling of Blue Sheets

Samuel Weiler <weiler@watson.org> Wed, 25 April 2012 14:44 UTC

Return-Path: <weiler@watson.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB41721F866D for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2012 07:44:00 -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=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6si-xc-tE-H for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2012 07:44:00 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id 2A54921F8669 for <ietf@ietf.org>; Wed, 25 Apr 2012 07:44:00 -0700 (PDT)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.4/8.14.4) with ESMTP id q3PEhqgi071518 for <ietf@ietf.org>; Wed, 25 Apr 2012 10:43:52 -0400 (EDT) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.4/8.14.4/Submit) with ESMTP id q3PEhqWF071513 for <ietf@ietf.org>; Wed, 25 Apr 2012 10:43:52 -0400 (EDT) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Wed, 25 Apr 2012 10:43:52 -0400
From: Samuel Weiler <weiler@watson.org>
To: ietf@ietf.org
Subject: Re: Future Handling of Blue Sheets
In-Reply-To: <alpine.LRH.2.01.1204240652570.9465@egate.xpasc.com>
Message-ID: <alpine.BSF.2.00.1204241924440.45427@fledge.watson.org>
References: <2AC114D8-E97B-47A0-B7E0-9EF016DCB09F@ietf.org> <4F94D01F.3070102@gondrom.org> <DDB8050A-7A04-4A0F-A364-0E3E511DCB43@vigilsec.com> <4F94E4AB.5080706@gondrom.org> <4F94EB97.3080906@bogus.com> <4F94EC7E.6040101@raszuk.net> <4F94F007.6060005@bogus.com> <35A52857-6545-4CF7-A8F0-48B10382445E@checkpoint.com> <4F94FF14.2070103@bogus.com> <DF6814A1-B3D4-451F-9CAB-DCD6667204BC@juniper.net> <4F95A7F2.7070500@dcrocker.net> <alpine.LRH.2.01.1204240652570.9465@egate.xpasc.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Wed, 25 Apr 2012 10:43:52 -0400 (EDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 25 Apr 2012 14:44:01 -0000

On Tue, 24 Apr 2012, David Morris wrote:

> The IETF meetings are actually not totally public. You must purchase a
> 'ticket' to attend. We would not allow someone to walk in off the street
> and photograph the functions, or even sit in a meeting and take notes.

Without commenting specifically about photographs, as MSJ pointed out, 
this is not true.  It may not be socially acceptable to crash working 
group meetings, but we do not use force to prevent it.  And as Scott 
Bradner pointed out on this list some time ago:

    Back when the IETF decided to charge for meetings ($100/meeting
    sometime in the early 1990s) Steve Coya said that the IETF would
    never check badges to block people from meetings.

The Beijing meeting was a notable exception.  There were guards 
looking for badges and at least one attendee's partner was restrained 
by the guards when she attempted to enter the meeting space to find 
her partner.  Even then, it the IETF was not the party doing the 
checking.  As the IAOC chair later explained:

    The IAOC was not aware that badge checking was going to happen
    prior to this meeting. It was implemented by the meeting host in
    conjunction with the hotel.

I imagine we would respond differently to something truly disruptive. 
Happily, we tend to be a civilized enough crowd that we don't need 
bouncers.

-- Sam