Re: Future Handling of Blue Sheets

Tim Chown <tjc@ecs.soton.ac.uk> Sat, 16 June 2012 10:53 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 9EF1321F8592; Sat, 16 Jun 2012 03:53:53 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eiZV4rQAiyGc; Sat, 16 Jun 2012 03:53:52 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 3061D21F858F; Sat, 16 Jun 2012 03:53:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q5GAre76020238; Sat, 16 Jun 2012 11:53:40 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q5GAre76020238
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1339844021; bh=npVrjUJ7V4sTK/90/VvBx4ti0hQ=; h=Subject:Mime-Version:From:In-Reply-To:Date:Cc:References:To; b=zx0n3GjsDapTSGgxiNtRzfeHwyJEIFEGN8ETv9T5nSk1mYEzz8uouo27d6krL7RqG wfJURCVjsUwmDps0/TkOV6Tv8x2WOcp8eElct1B4/aQFb1Kv+IXCF8FQ7Wh+engnG2 S5EwMzETTVs6CznBONUCs3Ryif6r2QzM0oiNBSrY=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id o5FBre0544129124Hx ret-id none; Sat, 16 Jun 2012 11:53:40 +0100
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q5GArZRt008462 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 16 Jun 2012 11:53:36 +0100
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <4FDC0280.8060505@bogus.com>
Date: Sat, 16 Jun 2012 11:53:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|71e7e6f840161bab9e911f1161b36a93o5FBre03tjc|ecs.soton.ac.uk|E01DF13C-F351-4F3E-B82E-DBFFDB252500@ecs.soton.ac.uk>
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> <4FDC0280.8060505@bogus.com> <E01DF13C-F351-4F3E-B82E-DBFFDB252500@ecs.soton.ac.uk>
To: Joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1278)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o5FBre054412912400; tid=o5FBre0544129124Hx; client=relay,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: q5GAre76020238
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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 10:53:53 -0000

If the purpose is simply differentiation of people with the same names, could we not ask people to enter the last four digits of their IETF registration number, which would presumably be unique, while being easy to remember?  The number could even be on your badge to always be easy to look up.

Unless there's some reason to keep registration numbers private?

That would also allow poorly handwritten names to more readily be checked/corrected by OCR when the sheets are scanned.

Tim

On 16 Jun 2012, at 04:50, Joel jaeggli wrote:

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