Re: Future Handling of Blue Sheets

Yoav Nir <ynir@checkpoint.com> Thu, 10 May 2012 18:25 UTC

Return-Path: <ynir@checkpoint.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 7D01211E80D6 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.417
X-Spam-Level:
X-Spam-Status: No, score=-10.417 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 7E23h0KT8XIl for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:25:22 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8F21011E80C8 for <ietf@ietf.org>; Thu, 10 May 2012 11:25:20 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q4AIPH7G004856; Thu, 10 May 2012 21:25:17 +0300
X-CheckPoint: {4FAC1575-6-1B221DC2-2FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 10 May 2012 21:25:17 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Thu, 10 May 2012 21:25:15 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Melinda Shore <melinda.shore@gmail.com>
Date: Thu, 10 May 2012 21:25:14 +0300
Subject: Re: Future Handling of Blue Sheets
Thread-Topic: Future Handling of Blue Sheets
Thread-Index: Ac0u2j5TQNfB2By/RhCk8vNqIskh/g==
Message-ID: <660BE5FB-E81E-4094-990C-7840966F0E38@checkpoint.com>
References: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp> <4FABFE13.3020800@gmail.com>
In-Reply-To: <4FABFE13.3020800@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
X-KSE-Antivirus-Interceptor-Info: scan successful
X-KSE-Antivirus-Info: Clean
Cc: "ietf@ietf.org" <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: Thu, 10 May 2012 18:25:22 -0000

On May 10, 2012, at 8:42 PM, Melinda Shore wrote:

> On 5/10/12 9:32 AM, Martin Rex wrote:
>> There has never been a need to actively broadcast these massive amounts
>> of personally identifiable information (PII), and I haven't seen any
>> convincing rationale for doing it now.
> 
> To be honest, "I don't want to receive more spam" and "My boss might
> find out I skipped a session" are not reasons not to be open about
> who's participating in sessions, particularly as we drift towards a
> meetings/voting model.

Participating is one thing. Presence is another. Reporting that I spoke up against the hard-fail requirement at Websec is part of the openness. Reporting that I was at SCIM, where I never once approached the microphone is not.

>  I understand sensitivity about broadcasting
> travel plans but in general some of the arguments being offered for
> being a less open organization with a less open process are drifting
> into "The FBI implanted a radio transmitter in my teeth" territory,
> and it seems to me that making blue sheets available after meetings
> does not reveal much PII beyond what's already available on the mailing
> lists.

The FBI needn't bother. They can just read the blue sheets :-)

> There's a serious question here about tradeoffs between privacy and
> openness.  Openness is not just a core institutional value (although
> it is one - do not forget that), but it's also a defense against
> charges of collusion, which, unfortunately, we've been seeing.

And how does the existence of such a lame attempt to list attendees help in this?

Yoav