Re: Blue Sheet Change Proposal

John C Klensin <john-ietf@jck.com> Fri, 04 April 2008 20:51 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 4DD543A6FAF; Fri, 4 Apr 2008 13:51:51 -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 74CF53A6DDD; Fri, 4 Apr 2008 13:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.93
X-Spam-Level:
X-Spam-Status: No, score=-1.93 tagged_above=-999 required=5 tests=[AWL=0.669, 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 tEuiet5QxazG; Fri, 4 Apr 2008 13:51:44 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id D311A3A6DE3; Fri, 4 Apr 2008 13:50:06 -0700 (PDT)
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1JhsrR-000LsE-6T; Fri, 04 Apr 2008 16:50:09 -0400
Date: Fri, 04 Apr 2008 16:50:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Olaf Kolkman <olaf@NLnetLabs.nl>, Ray Pelletier <rpelletier@isoc.org>
Subject: Re: Blue Sheet Change Proposal
Message-ID: <A03AB4719FF1DD88C122621A@p3.JCK.COM>
In-Reply-To: <C652E6EF-0E8E-4770-BE30-251A3562C412@NLnetLabs.nl>
References: <47F56545.4020603@isoc.org> <C652E6EF-0E8E-4770-BE30-251A3562C412@NLnetLabs.nl>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: Working Group Chairs <wgchairs@ietf.org>, 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


--On Friday, 04 April, 2008 08:26 +0200 Olaf Kolkman
<olaf@NLnetLabs.nl> wrote:

> There may be reasons to contact participants after a meeting,
> being able to tie the name to an e-mail might be of value. If
> folk think the spam concern is important (not me) the
> engineering approach is a layer of indirection: print a
> registration ID on the badges, and have folk fill in that I-D
> on the blue sheet, together with their names off course.

Or distribute sheets of bar-coded sticky labels in the
registration packet and let people either fill in a name and
number or affix a sticker.  The latter might also improve the
speed at which the things went around the room and would ensure
that neither email nor names could be captured by anyone other
than the secretariat.

But these sorts of methods are worth the trouble only if we are
convinced that there is a problem.   If  there is not, we are
wasting a tremendous amount of time discussing solutions to it.

    john



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