Re: Future Handling of Blue Sheets

IETF Chair <chair@ietf.org> Mon, 07 May 2012 15:02 UTC

Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1B921F85C4 for <ietf@ietfa.amsl.com>; Mon, 7 May 2012 08:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kRYoZSPlwux for <ietf@ietfa.amsl.com>; Mon, 7 May 2012 08:02:06 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id C44E321F861D for <ietf@ietf.org>; Mon, 7 May 2012 08:02:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 11B1A12C7DE; Mon, 7 May 2012 08:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fupR1z2LvkDg; Mon, 7 May 2012 08:01:59 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-140-3.washdc.fios.verizon.net [96.255.140.3]) by c8a.amsl.com (Postfix) with ESMTPSA id 8D80912C7D0; Mon, 7 May 2012 08:01:59 -0700 (PDT)
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: IETF Chair <chair@ietf.org>
In-Reply-To: <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com>
Date: Mon, 07 May 2012 11:02:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com>
To: David Morris <dwm@xpasc.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
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>
X-List-Received-Date: Mon, 07 May 2012 15:02:07 -0000

During the IESG discussion of this thread, we recognized the quality of the information on the blue sheets.  This point was made very clearly at the open mic discussion at the plenary and on the mail list.

Some people voiced agreement with your position, and others supported the posting of this information.  As I said in my earlier message, the consensus is quite rough.  By my review of the thread, which was made more difficult by the many off-topic postings, there is rough consensus for the inclusion of blue sheet information in the proceedings.

Russ


On May 6, 2012, at 10:04 PM, David Morris wrote:

> 
> I consider that there is a significant difference between the information 
> provided in the registered attendee list and the individual blue sheets:
> 
> a) to the extent that the information on the blue sheet is valid, it 
> provides an hour by hour log of location, the overall list of attendees at 
> most indicates an individual was present to pick up their badge at some
> point during the meeting.
> b) the validity of the list of registered attendees has a higher degree
> of probable validity because of the requirement for a significant payment
> and the processes required to process that payment.
> c) Individual blue sheets can suffer from any number of unintentional and
> intentional issues which limit their factual validity but not the mischief
> which can be caused by their easy online access.
> d) Scanning and publication imports a validity to the data which is not
> widely accepted by the community.
> 
> David Morris
> 
> On Sun, 6 May 2012, IETF Chair wrote:
> 
>> David:
>> 
>> The list of participants and their addresses are already part of the proceedings.  The incremental difference shows which participants signed in at each session.
>> 
>> Russ
>> 
>> 
>> 
>> On May 6, 2012, at 7:03 PM, David Morris wrote:
>> 
>>> 
>>> From my following of the topic, that concensus was really rough, in 
>>> particular the part about publishing the scans on-line. That represents
>>> a significant difference in ease access which I think required more than
>>> the very very rough concensus you seem to think you found.
>>> 
>>> On Sun, 6 May 2012, IETF Chair wrote:
>>> 
>>>> We have heard from many community participants, and consensus is quite rough on this topic.  The IESG discussed this thread and reached two conclusions:
>>>> 
>>>> (1) Rough consensus: an open and transparent standards process is more important to the IETF than privacy of blue sheet information.
>>>> 
>>>> (2) Rough consensus: inclusion of email addresses is a good way to distinguish participants with the same or similar names.
>>>> 
>>>> 
>>>> Based on these conclusions, the plan is to handle blue sheets as follows:
>>>> 
>>>> - Continue to collect email addresses on blue sheets;
>>>> 
>>>> - Scan the blue sheet and include the image in the proceedings for the WG session;
>>>> 
>>>> - Add indication to top of the blue sheet so people know it will be part of the proceedings; and
>>>> 
>>>> - Discard paper blue sheets after scanning.
>>>> 
>>>> 
>>>> On behalf of the IESG,
>>>> Russ
>>>> 
>>>> 
>>> 
>> 
>> 
>