Re: Future Handling of Blue Sheets

Tobias Gondrom <tobias.gondrom@gondrom.org> Thu, 10 May 2012 06:23 UTC

Return-Path: <tobias.gondrom@gondrom.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 353EB21F85B8 for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 23:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.778
X-Spam-Level:
X-Spam-Status: No, score=-96.778 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, 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 h7U8SaXquDd5 for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 23:23:29 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (www.gondrom.org [83.169.7.107]) by ietfa.amsl.com (Postfix) with ESMTP id F180E21F851C for <ietf@ietf.org>; Wed, 9 May 2012 23:23:28 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gondrom.org; b=q559Md5fWRQuP3UMV4Ef9vkFhRxM1iGC8DAiHbN2yf7yf87vR6ilsL6EIjcKrOWvnGxtcd/KTl38WIzn4Ru+gsqps9dsJgsyaWSnQJtRIkyIj21uc+xHk3hU7IQzOFcj; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Received: (qmail 1401 invoked from network); 10 May 2012 08:23:25 +0200
Received: from n2028211917.imsbiz.com (HELO ?10.65.1.159?) (202.82.119.17) by www.gondrom.org with (DHE-RSA-AES256-SHA encrypted) SMTP; 10 May 2012 08:23:25 +0200
Message-ID: <4FAB5ED8.7070004@gondrom.org>
Date: Thu, 10 May 2012 14:23:20 +0800
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Future Handling of Blue Sheets
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> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org>
In-Reply-To: <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Thu, 10 May 2012 06:23:30 -0000

Dear Russ,

please forgive me for adding one more comment on that after you judged 
on rough consensus.

As you said this rough consensus is quite rough (if we may call it 
"rough consensus").
I would like to point out two things:
1. the statement "(1) Rough consensus: an open and transparent standards 
process is more important to the IETF than privacy of blue sheet 
information." puts transparent process in competition with privacy. This 
is misleading, because there is no contradiction between an open and 
transparent process and privacy of personal information on this one. For 
example the availability of blue sheet information on request by an 
authenticated person does allow full transparency without broadcasting 
the personal location information. (e.g. see also Ted's proposal from 
yesterday)
(Furthermore, if I would be devil's advocate, I would question this 
comparison even further, because it could be misread as stating that the 
current standards process as it is today (with blue sheets on request) 
is not open or transparent...)

2. if consensus is so rough, we should also consider that the subject of 
the email discussion was maybe not clear enough about its impact to 
inform the audience of the consequences of the discussion and the 
consensus to be measured. We could equally have used a subject like 
this: "IETF wants to publish your specific locations / whereabouts 
(within 10m) on an 2-hourly basis during the day for each meeting and 
keep this information available published on the website indefinitely." 
It might have resulted in a different rough consensus.

Just my 5cents.

Best regards, Tobias




On 07/05/12 23:02, IETF Chair wrote:
> 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
>>>>>
>>>>>
>>>