Re: Future Handling of Blue Sheets

Thomas Nadeau <tnadeau@lucidvision.com> Mon, 23 April 2012 13:06 UTC

Return-Path: <tnadeau@lucidvision.com>
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 6DB6021F8628 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2012 06:06:59 -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.001, 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 6NY7mq444moZ for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2012 06:06:58 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id BAC9821F8625 for <ietf@ietf.org>; Mon, 23 Apr 2012 06:06:58 -0700 (PDT)
Received: from [192.168.1.94] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 365E120C684F; Mon, 23 Apr 2012 09:06:58 -0400 (EDT)
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset="us-ascii"
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <DF6814A1-B3D4-451F-9CAB-DCD6667204BC@juniper.net>
Date: Mon, 23 Apr 2012 06:06:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E644B65-0BDC-4D90-8370-B2E5443C3012@lucidvision.com>
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>
To: Kireeti Kompella <kireeti@juniper.net>
X-Mailer: Apple Mail (2.1257)
Cc: "ietf@ietf.org" <ietf@ietf.org>
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: Mon, 23 Apr 2012 13:06:59 -0000

	I agree with you. I've always been puzzled as to why anyone needs to know who specifically attended a meeting. What is that information used for later?  As far as I can, no one ever has gone back to associate email addresses with speakers at the mic, actual attendee lists or presentations or something.  Isn't the point just to gauge how full the room was so that we can book an appropriately sized room for the next meeting?  If that is the case, then just having the chairs take a rough estimate of how many people attended (or even just state a percentage of occupied seats) should suffice, right?

	--Tom



On Apr 23, 2012:1:13 AM, at 1:13 AM, Kireeti Kompella wrote:

> On Apr 23, 2012, at 0:05, "EXT - joelja@bogus.com" <joelja@bogus.com> wrote:
> 
> (quoting from RFC 2418)
> 
>> All working group sessions (including those held outside of the IETF
>> meetings) shall be reported by making minutes available.  These
>> minutes should include the agenda for the session, an account of the
>> discussion including any decisions made, and a list of attendees.
> 
> RFCs are not gospel. They can, and, in this instance, should, be changed: either remove that last item, or stately explicitly that there is no expectation of privacy at IETF meetings.  (I have a sinking feeling I know which way that will go.)
> 
> Why shouldn't getting the list of a meeting's attendees require a subpoena?  The cost argument is bogus; equally, there are those who think going to a judge for permission to wiretap is a waste of time and money.
> 
> Put the money you save on NOT installing RFID kit into a fund for handling subpoenas (only half joking). 
> 
> Kireeti
> 
> PS: Yoav, regarding your remarks on street surveillance, from the IETF Note Well:
> 
> "A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public."
> 
> A camera over meeting room doorways is next.