Re: Blue sheet harvest

Bill Manning <bmanning@ISI.EDU> Fri, 04 April 2008 03:53 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 81CA828C393; Thu, 3 Apr 2008 20:53:06 -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 4048C28C393; Thu, 3 Apr 2008 20:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 QC0fbFXeR7SS; Thu, 3 Apr 2008 20:53:04 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 7AC323A6DCA; Thu, 3 Apr 2008 20:53:04 -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 m343qVbV027972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Apr 2008 20:52:32 -0700 (PDT)
Received: (from bmanning@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id m343qVxk027971; Thu, 3 Apr 2008 20:52:31 -0700 (PDT)
Date: Thu, 03 Apr 2008 20:52:31 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: "Scott O. Bradner" <sob@harvard.edu>
Subject: Re: Blue sheet harvest
Message-ID: <20080404035231.GA23412@boreas.isi.edu>
References: <20080404001012.31E33843A22@newdev.eecs.harvard.edu>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20080404001012.31E33843A22@newdev.eecs.harvard.edu>
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: wgchairs@ietf.org, 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 process you describe has happend in recent memory at more than
one IETF.  it started w/ folsk scanning the pages of the early bound
copies of IETFF proceedings.

--bill


On Thu, Apr 03, 2008 at 08:10:12PM -0400, Scott O. Bradner wrote:
> 
> 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

-- 
--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