Re: Blue Sheet Change Proposal

Bill Manning <bmanning@ISI.EDU> Fri, 04 April 2008 21:33 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 372313A68D3; Fri, 4 Apr 2008 14:33:48 -0700 (PDT)
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 02A873A6854; Fri, 4 Apr 2008 14:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level:
X-Spam-Status: No, score=-3.799 tagged_above=-999 required=5 tests=[AWL=0.800, BAYES_00=-2.599, GB_I_LETTER=-2]
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 R5WlLazogad9; Fri, 4 Apr 2008 14:33:46 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 302393A676A; Fri, 4 Apr 2008 14:33:46 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m34LVxS2022924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 4 Apr 2008 14:32:00 -0700 (PDT)
Received: (from bmanning@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id m34LVxMP022923; Fri, 4 Apr 2008 14:31:59 -0700 (PDT)
Date: Fri, 4 Apr 2008 14:31:59 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: David Conrad <drc@virtualized.org>
Subject: Re: Blue Sheet Change Proposal
Message-ID: <20080404213159.GC9968@boreas.isi.edu>
References: <47F56545.4020603@isoc.org> <C652E6EF-0E8E-4770-BE30-251A3562C412@NLnetLabs.nl> <E7CB49418CF43269B3D9FD5D@Uranus.local> <002c01c89664$c9f260a0$6600a8c0@D693GRB1> <E9D7E03F-3C98-4BF1-AFC6-8DD60D6E3806@cs.columbia.edu> <20080404211133.GA9968@boreas.isi.edu> <3A05DE8F-A23B-41C3-9B97-708A47BDA8BC@virtualized.org>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <3A05DE8F-A23B-41C3-9B97-708A47BDA8BC@virtualized.org>
User-Agent: Mutt/1.4.2.2i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Discussion <ietf@ietf.org>, Bill Manning <bmanning@ISI.EDU>
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-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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

 i was just giving an amen to Hennings note that participant
 identification in other venues has taken on a different 
 form than "blue-sheets"...
 I don't see a problem to be solved - as long as folks realise
 that attendance/participation in the IETF is not bound by 
 a scrawl on a sheet of paper.

--bill


On Fri, Apr 04, 2008 at 02:18:27PM -0700, David Conrad wrote:
> I'm sorry.  What problem are we trying to solve again?
> 
> I thought we were talking about simply removing email addresses from  
> the blue sheets, but it seems we're talking about something entirely  
> different.
> 
> Thanks,
> -drc
> 
> On Apr 4, 2008, at 2:11 PM, Bill Manning wrote:
> >
> >WIDE camps have done the RFID thing for several years now.
> >
> >--bill
> >
> >
> >On Fri, Apr 04, 2008 at 11:35:12AM -0400, Henning Schulzrinne wrote:
> >>The registration database for each IETF meeting already contains  
> >>email
> >>addresses of all attendees, presumably a superset of the blue-sheet
> >>signers.
> >>
> >>More technologically-advanced conferences and trade-shows use RFID or
> >>(a few years ago) mag stripes to avoid deciphering handwriting. The
> >>per-card cost is modest and since there are a lot of repeat  
> >>attendees,
> >>we all just need our IETF "frequent flyer card". We used something
> >>like that for speaker identification at the microphone at ACM
> >>Multimedia 2004; the microphone had a BlueTooth-enabled RFID reader
> >>that transmitted the code to a data gathering host, which then
> >>displayed name and affiliation on a screen. The range of the card was
> >>a few inches.
> >>
> >>Henning
> >>
> >>On Apr 4, 2008, at 11:01 AM, Mr Kim Sanders wrote:
> >>
> >>>- If there were a database with everyone on file .
> >>>- If each person were assigned a permanent identity code .
> >>>- If block l(i.e. disconnected) letters were required .
> >>>- If persons designated as having legible handwriting wrote
> >>>everything but
> >>>the signature .
> >>>
> >>>/Kim
> >>
> >>_______________________________________________
> >>IETF mailing list
> >>IETF@ietf.org
> >>https://www.ietf.org/mailman/listinfo/ietf
> >
> >-- 
> >--bill
> >
> >Opinions expressed may not even be mine by the time you read them, and
> >certainly don't reflect those of any other entity (legal or  
> >otherwise).
> >
> >_______________________________________________
> >IETF mailing list
> >IETF@ietf.org
> >https://www.ietf.org/mailman/listinfo/ietf
> >

-- 
--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf