The purpose of blue sheets [Re: Blue sheet harvest]

Pekka Savola <pekkas@netcore.fi> Sat, 05 April 2008 10:56 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 4B99C3A69C9; Sat, 5 Apr 2008 03:56:13 -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 658523A69C9; Sat, 5 Apr 2008 03:56:12 -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 c+YvwAxNz2ad; Sat, 5 Apr 2008 03:56:11 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 26A8F3A6C41; Sat, 5 Apr 2008 03:55:00 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id m35At0GH022805; Sat, 5 Apr 2008 13:55:00 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id m35AsxQg022802; Sat, 5 Apr 2008 13:54:59 +0300
Date: Sat, 5 Apr 2008 13:54:59 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: "Scott O. Bradner" <sob@harvard.edu>
Subject: The purpose of blue sheets [Re: Blue sheet harvest]
In-Reply-To: <20080404185513.B032B847806@newdev.eecs.harvard.edu>
Message-ID: <alpine.LRH.1.10.0804051330210.22135@netcore.fi>
References: <20080404185513.B032B847806@newdev.eecs.harvard.edu>
User-Agent: Alpine 1.10 (LRH 962 2008-03-14)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV 0.92.1/6607/Sat Apr 5 03:53:45 2008 on otso.netcore.fi
X-Virus-Status: Clean
Cc: wgchairs@ietf.org, ietf@ietf.org, bmanning@ISI.EDU
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

Has the purpose and the expectations of the blue sheets been 
established somewhere?

So far I've seen (or sen folks justifying) the following use cases:

1) gauging the number of people in the room (for room size allocations
    for the next meeting)
2) identifying later on whether someone sat in the audience (for IPR
    purposes, not clear to what benefit exactly)
3) identifying previously-unknown people who spoke up in the mike
    and said their name but you weren't sure if you got it right
    (for the minutes). (i.e. identifying who made a Contribution in
    IPR rules sense)
4) identifying a person like 3) who has never posted on the mailing
    list and contacting him/her about the comment (otherwise you
    wouldn't know the email address)
5) contacting participants later on about future activities in the
    area (e.g. BOF list creation).
6) WG chair giving extra advice that if you mark an "X" beside your
    email address, s/he will subscribe you to the mailing list.

1) does not require email addresses, and possibly not even blue 
sheets.  This seems like the typical reason given by the WG chairs for 
the blue sheets ("if you don't sign, we won't get a room next 
time.."). I'll observe that 2) appears to be useless because whether 
or not a name exists is no proof one way or the other.  The critical 
thing here is whether someone made a Contribution (in the IPR sense) 
at the meeting.  So, it's likely necessary to be able to identify 
everyone that speaks up in the mike, but whether or not the blue 
sheets is the right tool to do that is debatable.  3) and 4) seem like 
useful goals, but yet again, this seems an issue of identifying the 
person speaking up in the mike, not who sat in the room.  5) only 
seems necessary with BOFs etc that have not been managed properly (a 
mailing list needs to be set up in advance in any case; if persons are 
not signed up on appropriate lists, mass-mailing them (isn't that 
spamming?) doesn't seem to be a very useful excercise).  I don't know 
how useful 6) is in practise; anyone should be clueful enough to sign 
up on the mailing list herself.

Some more below,

On Fri, 4 Apr 2008, Scott O. Bradner wrote:
>> and signing the sheet is strictly voluntary to date
>
> well, there are no guards with guns watching but someone who
> decides to not sign is not being honest about their participation

I've personally used somewhat looser definition.  I don't bother to 
sign those blue sheets that circulate in WG rooms where I just go (for 
the lack of better place) to read my email and get a bit of idea 
what's going on.  I don't intend to say anything on the mike, I have 
no interest in participating in that WG otherwise and I don't think I 
should be counted when it gets decided what room size is appropriate 
for the WG in the next IETF.  How exactly is it wrong not to sign the 
blue sheet in this case?

Another category is "after WG meeting X ends, go to the room used by 
WG meeting Y to see what's going on there".  At that point, blue 
sheets have already circulated and it seems too much of a bother to 
sign anything anymore.  In this case, you might even say something in 
the mike; whether your name exists on the blue sheet or not doesn't 
guarantee whether you were present or not, and I don't see it 
practical to change the procedures to be any stricter.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf