RE: Blue Sheet Change Proposal

<john.loughney@nokia.com> Fri, 04 April 2008 00:12 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 C1DB828C710; Thu, 3 Apr 2008 17:12:03 -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 758DB28C1B6; Thu, 3 Apr 2008 17:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.81
X-Spam-Level:
X-Spam-Status: No, score=-3.81 tagged_above=-999 required=5 tests=[AWL=2.789, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 I7rWc0-jTu5b; Thu, 3 Apr 2008 17:12:01 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 3063D28C3E6; Thu, 3 Apr 2008 17:12:01 -0700 (PDT)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m340BvU3020420; Fri, 4 Apr 2008 03:11:58 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 4 Apr 2008 03:11:57 +0300
Received: from daebe104.NOE.Nokia.com ([10.241.36.13]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 3 Apr 2008 19:11:55 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: Blue Sheet Change Proposal
Date: Thu, 03 Apr 2008 19:11:54 -0500
Message-ID: <19EBBEC503C3B5469070E0A6674A533A0131EA9F@daebe104.NOE.Nokia.com>
In-Reply-To: <20080404001012.31E33843A22@newdev.eecs.harvard.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Blue Sheet Change Proposal
Thread-Index: AciV6EbPiCkOaFmSRcGyeZuSn2TshgAABl2g
References: <20080404001012.31E33843A22@newdev.eecs.harvard.edu>
From: john.loughney@nokia.com
To: sob@harvard.edu, ietf@ietf.org, wgchairs@ietf.org
X-OriginalArrivalTime: 04 Apr 2008 00:11:55.0766 (UTC) FILETIME=[7DEC7960:01C895E8]
X-Nokia-AV: Clean
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 thought it was for the same reasons that Scott suggested, to tell
who was in the room and the emails served the purpose for handling
consensus calls on the list, and ensuring any 'nasty' IPR supprises as
well.

John 

>-----Original Message-----
>From: wgchairs-bounces@ietf.org 
>[mailto:wgchairs-bounces@ietf.org] On Behalf Of ext Scott O. Bradner
>Sent: 04 April, 2008 03:10
>To: ietf@ietf.org; wgchairs@ietf.org
>Subject: Re: Blue Sheet Change Proposal
>
>
>Ole guessed
>> My understanding is that the blue sheet serves mainly as a record of 
>> "who was in the room" which I think is largely used to plan room 
>> capacities for the next meeting.
>
>the "blue sheets" are required as part of the basic openness 
>process in a standards organization - there is a need to know 
>"who is in the room" (see RFC 2418 section 3.1 for the actual
>requirement)
>
>the blue sheets become part of the formal record of the 
>standards process and can be retrieved if needed (e.g. in a 
>lawsuit) but are not generally made available 
>
>as pointed out by Mark Andrews - email addresses can be useful 
>in determining the actual identity of the person who scrawled 
>their name on the sheet - so it is an advantage to retain them
>
>I'm trying to understand how the blue sheets contribute in any 
>significant way to the spam problem - someone whould have to 
>be surreptitiously copying  them or quickly writing down the 
>email addresses - both could happen but do not seem to be all 
>that likely there are far more efficient ways to grab email addresses
>
>so, my question is "is this a problem that needs solving"?
>
>Scott
>
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf