Re: Future Handling of Blue Sheets

Michael StJohns <mstjohns@comcast.net> Mon, 23 April 2012 17:13 UTC

Return-Path: <mstjohns@comcast.net>
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 C663421F8636 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2012 10:13:07 -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 T2B5+JqNvbCk for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2012 10:13:07 -0700 (PDT)
Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by ietfa.amsl.com (Postfix) with ESMTP id 2FA7E21F8705 for <ietf@ietf.org>; Mon, 23 Apr 2012 10:13:07 -0700 (PDT)
Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta14.emeryville.ca.mail.comcast.net with comcast id 1TPs1j0031Y3wxoAEVD6K6; Mon, 23 Apr 2012 17:13:06 +0000
Received: from Mike-PC3.comcast.net ([68.83.222.237]) by omta15.emeryville.ca.mail.comcast.net with comcast id 1VD51j00257vnMg8bVD5GY; Mon, 23 Apr 2012 17:13:06 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 23 Apr 2012 13:13:02 -0400
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Future Handling of Blue Sheets
In-Reply-To: <4F9581D3.2020605@gmail.com>
References: <2AC114D8-E97B-47A0-B7E0-9EF016DCB09F@ietf.org> <DCC302FAA9FE5F4BBA4DCAD465693779173ED21640@PRVPEXVS03.corp.twcable.com> <ACDB7FE7-5C75-49C4-904D-8542AC05C66E@sobco.com> <4F9581D3.2020605@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20120423171307.2FA7E21F8705@ietfa.amsl.com>
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 17:13:07 -0000

At 12:22 PM 4/23/2012, Melinda Shore wrote:
>On 4/23/12 6:58 AM, Scott O Bradner wrote:
>>see rfc 2418 - they are to keep a record as who is taking part in a WG's activities
>>keeping track of attendees is a basic part of any standards development organization's process
>
>The tension here appears to be between transparency of process and an
>individual right to privacy.  I think that the IETF has a considerable
>stake in the former, not just because of the frequency with which some
>little pisher or other threatens to sue over what they perceive to be
>trust/collusion issues, but because openness is an IETF institutional
>value.  I think it should continue to be.  I understand the privacy
>issues (although I won't necessary lump them as an instance of revealing
>PII) but tend to think that the information being revealed is pretty
>sparse and the privacy concerns here probably aren't substantial enough
>to counterbalance the organizational interest in keeping processes as
>open as possible.
>
>Melinda


And to put a further point on it - the last sentence of the "NOTE WELL" notice (http://www.ietf.org/about/note-well.html) that applies to each and every IETF meeting and working group session and IETF activity is very clear that written, audio and video records can and will be kept.  A person attending an IETF meeting has no reasonable expectation of privacy for those things we define as "IETF activities".

So if someone demands "privacy", the price is non-participation in the IETF.

Mike