Re: Future Handling of Blue Sheets

Tobias Gondrom <tobias.gondrom@gondrom.org> Mon, 23 April 2012 05:48 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 D01F721F8597 for <ietf@ietfa.amsl.com>; Sun, 22 Apr 2012 22:48:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.159
X-Spam-Level:
X-Spam-Status: No, score=-96.159 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, RCVD_IN_SORBS_WEB=0.619, 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 n4pJ+EoHgQZn for <ietf@ietfa.amsl.com>; Sun, 22 Apr 2012 22:48:18 -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 D573B21F8581 for <ietf@ietf.org>; Sun, 22 Apr 2012 22:48:17 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gondrom.org; b=RdDseriY37nYU3tZ/W5nnbbbXpsYTLsId0iw/Dvzh2GSVITMBUOND6nM2kt/e690/J0PxgU4hDhJUtxYR4WArctxGD25sUnH8WV5CPr0JVzuV9wK+sLpHbblT2xnAaSh; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Received: (qmail 32171 invoked from network); 23 Apr 2012 07:48:15 +0200
Received: from unknown (HELO ?172.27.51.107?) (203.127.223.69) by www.gondrom.org with (DHE-RSA-AES256-SHA encrypted) SMTP; 23 Apr 2012 07:48:15 +0200
Message-ID: <4F94ED1C.7030605@gondrom.org>
Date: Mon, 23 Apr 2012 13:48:12 +0800
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: joelja@bogus.com
Subject: Re: Future Handling of Blue Sheets
References: <2AC114D8-E97B-47A0-B7E0-9EF016DCB09F@ietf.org> <4F94D01F.3070102@gondrom.org> <DDB8050A-7A04-4A0F-A364-0E3E511DCB43@vigilsec.com> <4F94E4AB.5080706@gondrom.org> <4F94EB97.3080906@bogus.com>
In-Reply-To: <4F94EB97.3080906@bogus.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: 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, 23 Apr 2012 05:48:18 -0000

On 23/04/12 13:41, Joel jaeggli wrote:
> On 4/22/12 22:12 , Tobias Gondrom wrote:
>> Hi Russ,
>>
>> thank you for the information.
>> In this case, my preference would be not to publish the blue sheets with
>> the proceedings.
>>
>> Reasoning:
>> The blue sheet data can at some point be used to determine movement
>> profiles of individual attendees at the meeting to a finer granularity
>> than today and therefore can be an issue for privacy (even though I
>> recognize that this is a public meeting). The fact that we "may reduce"
>> the amount of subpoenas is a viable reason, still personal data should
>> be handled as conservative as possible.
> What property of the blue sheet makes it personal data.

The fact that publishing them will allow to track in which location 
(i.e. meeting room) you are/were at a given point in time. Basically a 
person could track your movement over the time of the IETF week.