Re: Future Handling of Blue Sheets

Joel jaeggli <joelja@bogus.com> Sat, 16 June 2012 03:50 UTC

Return-Path: <joelja@bogus.com>
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 9179011E808C; Fri, 15 Jun 2012 20:50:27 -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 BqxYUQ0oPolB; Fri, 15 Jun 2012 20:50:27 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A87EB11E8089; Fri, 15 Jun 2012 20:50:26 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q5G3oOTf058237 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 16 Jun 2012 03:50:24 GMT (envelope-from joelja@bogus.com)
Message-ID: <4FDC0280.8060505@bogus.com>
Date: Fri, 15 Jun 2012 20:50:24 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: edj.etc@gmail.com
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> <D21AF73E-AC26-4ED7-9A85-2F4B6246E238@ietf.org> <F9874821-601D-4655-AB91-C648AC10E49D@standardstrack.com> <616737881-1339796556-cardhu_decombobulator_blackberry.rim.net-133583724-@b2.c2.bise6.blackberry>
In-Reply-To: <616737881-1339796556-cardhu_decombobulator_blackberry.rim.net-133583724-@b2.c2.bise6.blackberry>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 16 Jun 2012 03:50:25 +0000 (UTC)
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, ietf-bounces@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: Sat, 16 Jun 2012 03:50:27 -0000

On 6/15/12 14:42 , edj.etc@gmail.com wrote:
> I presume it is the same data that people input into the "Organization" field when they register for the meeting.

I do change mine based on what capacity I'm attending a particular
meeting in. That goes for email address on existing blue sheets as well...

The nice people who send me a check every two weeks don't generally fund
my attendance.

> Regards,
> 
> Ed  J.
> 
> -----Original Message-----
> From: Eric Burger <eburger-l@standardstrack.com>
> Sender: ietf-bounces@ietf.org
> Date: Fri, 15 Jun 2012 17:37:50 
> To: IETF Chair<chair@ietf.org>
> Cc: IETF<ietf@ietf.org>
> Subject: Re: Future Handling of Blue Sheets
> 
> Do we have guidelines as to what is an "organization affiliation"?
> 
> On Jun 14, 2012, at 5:26 PM, IETF Chair wrote:
> 
>> Two things have occurred since the message below as sent to the IETF mail list.  First, we got a lawyer in Europe to do some investigation, and the inclusion of the email address on the blue sheet will lead to trouble with the European privacy laws.  Second, Ted Hardie suggested that we could require a password to access the scanned blue sheet.
>>
>> Based on the European privacy law information, the use of email will result in a major burden.  If the email address is used, then we must provide a way for people to ask for their email address to be remove at any time in the future, even if we got prior approval to include it.  Therefore, I suggest that we collect organization affiliation to discriminate between multiple people with the same name instead of email address.
>>
>> Based on Ted's suggestion, I checked with the Secretariat about using a datatracker login to download the scanned blue sheet.  This is fairly easy to do, once the community tracking tools are deployed.  However, with the removal of the email addresses from the blue sheets, it is unclear that there is any further need for password protection of these images.  Therefore, I suggest that we proceed without password protection for the blue sheet images.
>>
>> Here is a summary of the suggested way forward:
>>
>> - Stop collecting email addresses on blue sheets;
>>
>> - Collect organization affiliation to discriminate between multiple people with the same name;
>>
>> - Scan the blue sheets and include the images 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.
>>
>> Russ
>>
>>
>> On May 6, 2012, at 12:46 PM, 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
>>>
>>
> 
>