Re: Blue Sheet Change Proposal

Henning Schulzrinne <hgs@cs.columbia.edu> Fri, 04 April 2008 15:39 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 7B10228C52A; Fri, 4 Apr 2008 08:39:26 -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 ABFF428C4C2; Fri, 4 Apr 2008 08:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level:
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
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 Ehk5f5TIQk1x; Fri, 4 Apr 2008 08:39:13 -0700 (PDT)
Received: from serrano.cc.columbia.edu (serrano.cc.columbia.edu [128.59.29.6]) by core3.amsl.com (Postfix) with ESMTP id 40DC228C3A0; Fri, 4 Apr 2008 08:35:08 -0700 (PDT)
Received: from ice.cs.columbia.edu (ice.cs.columbia.edu [128.59.18.177]) (user=hgs10 mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id m34FZCwg016933 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 4 Apr 2008 11:35:12 -0400 (EDT)
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Mr Kim Sanders <Mr.Kim.Sanders@shaw.ca>
In-Reply-To: <002c01c89664$c9f260a0$6600a8c0@D693GRB1>
Subject: Re: Blue Sheet Change Proposal
X-Priority: 3
References: <47F56545.4020603@isoc.org> <C652E6EF-0E8E-4770-BE30-251A3562C412@NLnetLabs.nl> <E7CB49418CF43269B3D9FD5D@Uranus.local> <002c01c89664$c9f260a0$6600a8c0@D693GRB1>
Message-Id: <E9D7E03F-3C98-4BF1-AFC6-8DD60D6E3806@cs.columbia.edu>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 4 Apr 2008 11:35:12 -0400
X-Mailer: Apple Mail (2.919.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.63 on 128.59.29.6
Cc: Working Group Chairs <wgchairs@ietf.org>, Barry Leiba <leiba@watson.ibm.com>, IETF Discussion <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-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

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