Re: Future Handling of Blue Sheets

John C Klensin <john@jck.com> Thu, 10 May 2012 07:09 UTC

Return-Path: <john@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 7BA2F21F85C6 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 00:09:20 -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 ji+VxKak+2rm for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 00:09:20 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DC0C721F85AF for <ietf@ietf.org>; Thu, 10 May 2012 00:09:19 -0700 (PDT)
Received: from localhost ([::1] helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1SSNPh-000MA1-Nj; Thu, 10 May 2012 03:03:49 -0400
Date: Thu, 10 May 2012 03:09:15 -0400
From: John C Klensin <john@jck.com>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>, ietf@ietf.org
Subject: Re: Future Handling of Blue Sheets
Message-ID: <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com>
In-Reply-To: <4FAB5ED8.7070004@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>
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
X-Mailman-Approved-At: Thu, 10 May 2012 09:34:55 -0700
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 07:09:20 -0000

(top post) 
Tobias,

Constructing and then attacking strawmen is not helpful.

As far as I know, no one has proposed making blue sheet
information --and hence precise location information for
identified individuals-- available to the public in real time
during the meetings.   As one of, I assume, many members of this
community who will not broadcast my travel plans to social
networks, etc., until after I return home, I would strenuously
object to any such thing but, again, as far as I know, no one
proposed it.

     john


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

> Dear Russ,
> 
> please forgive me for adding one more comment on that after
> you judged on rough consensus.
> 
> As you said this rough consensus is quite rough (if we may
> call it "rough consensus").
> I would like to point out two things:
> 1. the statement "(1) Rough consensus: an open and transparent
> standards process is more important to the IETF than privacy
> of blue sheet information." puts transparent process in
> competition with privacy. This is misleading, because there is
> no contradiction between an open and transparent process and
> privacy of personal information on this one. For example the
> availability of blue sheet information on request by an
> authenticated person does allow full transparency without
> broadcasting the personal location information. (e.g. see also
> Ted's proposal from yesterday)
> (Furthermore, if I would be devil's advocate, I would question
> this comparison even further, because it could be misread as
> stating that the current standards process as it is today
> (with blue sheets on request) is not open or transparent...)
> 
> 2. if consensus is so rough, we should also consider that the
> subject of the email discussion was maybe not clear enough
> about its impact to inform the audience of the consequences of
> the discussion and the consensus to be measured. We could
> equally have used a subject like this: "IETF wants to publish
> your specific locations / whereabouts (within 10m) on an
> 2-hourly basis during the day for each meeting and keep this
> information available published on the website indefinitely."
> It might have resulted in a different rough consensus.