Re: [apps-discuss] Webfinger discussion

John C Klensin <john-ietf@jck.com> Wed, 28 March 2012 09:42 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9502321F8928 for <apps-discuss@ietfa.amsl.com>; Wed, 28 Mar 2012 02:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.687
X-Spam-Level:
X-Spam-Status: No, score=-102.687 tagged_above=-999 required=5 tests=[AWL=-0.088, 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 TvJp5fBFvNQT for <apps-discuss@ietfa.amsl.com>; Wed, 28 Mar 2012 02:42:40 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 03ACC21F8921 for <apps-discuss@ietf.org>; Wed, 28 Mar 2012 02:42:39 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SCpK5-0008I9-Ab; Wed, 28 Mar 2012 05:37:45 -0400
Date: Wed, 28 Mar 2012 05:42:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: 'Andrew Sullivan' <ajs@anvilwalrusden.com>, apps-discuss@ietf.org
Message-ID: <924455E32E44385207331B9D@PST.JCK.COM>
In-Reply-To: <20120327193247.GA12201@mail.yitter.info>
References: <053201cd0b5d$c08c80f0$41a582d0$@packetizer.com> <20120326150556.GC3557@mail.yitter.info> <CAA1s49V0M7N1pLua+ORxGWmsrd_yAA_KQ0Piqjg8VuWJ5=G+Lg@mail.gmail.com> <20120327084709.GB11491@mail.yitter.info> <00ac01cd0c34$cfc96f10$6f5c4d30$@packetizer.com> <20120327193247.GA12201@mail.yitter.info>
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
Subject: Re: [apps-discuss] Webfinger discussion
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2012 09:42:40 -0000

--On Tuesday, March 27, 2012 15:32 -0400 'Andrew Sullivan'
<ajs@anvilwalrusden.com> wrote:

> On Tue, Mar 27, 2012 at 12:15:21PM -0400, Paul E. Jones wrote:
>> We'll add text along those lines to the next draft.  Any
>> other security considerations we should note?
> 
> I wish I had something more intelligent to say than, "Is
> anyone [else] worried about the aggregation of this
> information amd what it does to the security profile of the
> aggregated things?"  Note this isn't exactly the privacy
> issue, though there's that. 

Short answer: yes.

Slightly longer answer: While most of today's privacy
discussions correctly focus on such questions as "why do you
need to know that", "why should I tell you", and "if I do tell
you, what control do I have over your telling others", many of
the really hard questions lie in the observation that the more
dimensions of information I know about you (or about your
membership in various groups and categories) the more I identify
you and predict your behavior in statistically-interesting ways.
Now combining information associated with me@service1,
me@service2, and me@service3 doesn't inherently create any extra
risk unless you have (deliberately or accidentally) associated
different information with those identities s.t. the information
content in their union is significantly larger than the
information content in their intersection.   If that
relationship holds, you are exposed to a new family of
unintended disclosures, some of it based on statistical models
of the behavior of populations that share a large enough number
of attribute categories with you.

I have no idea how we go about sorting it out, but I agree that
we need to be clear about the possibility and risks.

   john