Re: Blue Sheet Change Proposal

Olaf Kolkman <olaf@NLnetLabs.nl> Fri, 04 April 2008 06:27 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 90E0828C1B8; Thu, 3 Apr 2008 23:27:01 -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 C025E28C102; Thu, 3 Apr 2008 23:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.253
X-Spam-Level:
X-Spam-Status: No, score=-2.253 tagged_above=-999 required=5 tests=[AWL=0.346, 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 9aiU62VEsmU5; Thu, 3 Apr 2008 23:26:59 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by core3.amsl.com (Postfix) with ESMTP id AFFF828C1B8; Thu, 3 Apr 2008 23:26:58 -0700 (PDT)
Received: from Miffy.lan (a82-95-132-144.adsl.xs4all.nl [82.95.132.144]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.2/8.14.2) with ESMTP id m346Qx3N096344 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 4 Apr 2008 08:27:00 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
Message-Id: <C652E6EF-0E8E-4770-BE30-251A3562C412@NLnetLabs.nl>
From: Olaf Kolkman <olaf@NLnetLabs.nl>
To: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <47F56545.4020603@isoc.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: Blue Sheet Change Proposal
Date: Fri, 04 Apr 2008 08:26:59 +0200
References: <47F56545.4020603@isoc.org>
X-Pgp-Agent: GPGMail d52 (v52, Leopard)
X-Mailer: Apple Mail (2.919.2)
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (open.nlnetlabs.nl [213.154.224.1]); Fri, 04 Apr 2008 08:27:00 +0200 (CEST)
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: multipart/mixed; boundary="===============1343946579=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Apr 4, 2008, at 1:16 AM, Ray Pelletier wrote:
> All,
>
> We are considering changing the meeting Blue Sheet by eliminating the
> need to enter an email address to avoid spam concerns.
>
> Is there any good reason to retain that info bit?
>
> Ray

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.

--Olaf



-------------
Due to a mishap my right hand is in cast and I can only type short  
messages using my left hand. Apologies for the snappy tone that may be  
caused by that.

Olaf Kolkman
olaf@NLnetLabs.nl




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