Re: Future Handling of Blue Sheets

John C Klensin <john-ietf@jck.com> Thu, 10 May 2012 08:35 UTC

Return-Path: <john-ietf@jck.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 338D121F85F0 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 01:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level:
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 bL1AbDQFVfCd for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 01:35:19 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A954621F85EE for <ietf@ietf.org>; Thu, 10 May 2012 01:35:19 -0700 (PDT)
Received: from localhost ([::1] helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SSOkz-000MTx-I5; Thu, 10 May 2012 04:29:53 -0400
Date: Thu, 10 May 2012 04:35:19 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
Subject: Re: Future Handling of Blue Sheets
Message-ID: <12F34D6725B91B95351EB144@JcK-HP8200.jck.com>
In-Reply-To: <4FAB7567.7070402@gondrom.org>
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> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org> <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com> <4FAB7567.7070402@gondrom.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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: Thu, 10 May 2012 08:35:20 -0000

--On Thursday, May 10, 2012 15:59 +0800 Tobias Gondrom
<tobias.gondrom@gondrom.org> wrote:

> John,
> 
> sorry, maybe I did not articulate myself precisely enough. I
> did not intend to say it would be published in real-time. What
> I wanted to communicate is that we would collect that data
> only during daytime and only with 2hours-granularity as it's
> only meeting attendance in which room you are (and publish it
> at any point in time later). However, we would keep it public
> indefinitely (in the proceedings).

Good.  My apologies for misunderstanding your intent.

> Like you, I am very cautious about broadcasting my travel
> plans. Plus, I am not only concerned about in advance and
> real-time, but also about broadcasting to the public places
> I've been in the past (or for that matter any personal
> information).

But it seems to me that takes us back to Russ's summary in that
it is normal, and arguably necessary, for a standards body to
record --and make available to those who are interested-- the
identities of those participating in meetings.

best regards,
   john