Re: [alto] Potential privacy issue in draft-deng-alto-p2p-ext-01?

Sebastian Kiesel <ietf-alto@skiesel.de> Mon, 30 June 2014 14:36 UTC

Return-Path: <sebi@gw01.ehlo.wurstkaes.de>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C536B1A036B for <alto@ietfa.amsl.com>; Mon, 30 Jun 2014 07:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.499
X-Spam-Level:
X-Spam-Status: No, score=0.499 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V8t4_2gY3NUp for <alto@ietfa.amsl.com>; Mon, 30 Jun 2014 07:36:05 -0700 (PDT)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C346B1A036E for <alto@ietf.org>; Mon, 30 Jun 2014 07:36:04 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.80) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1X1cgT-0000eT-2V; Mon, 30 Jun 2014 16:35:53 +0200
Date: Mon, 30 Jun 2014 16:35:53 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Message-ID: <20140630143552.GB4608@gw01.ehlo.wurstkaes.de>
References: <655C07320163294895BBADA28372AF5D16593352@FR712WXCHMBA13.zeu.alcatel-lucent.com> <53ADA6E0.3030503@bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <53ADA6E0.3030503@bell-labs.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/alto/2BQUxFgf7sIVbvvc82OZplb5jf4
Cc: IETF ALTO <alto@ietf.org>
Subject: Re: [alto] Potential privacy issue in draft-deng-alto-p2p-ext-01?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jun 2014 14:36:07 -0000

On Fri, Jun 27, 2014 at 12:16:16PM -0500, Vijay K. Gurbani wrote:
> On 06/26/2014 04:58 AM, Scharf, Michael (Michael) wrote:
> >Haibin asked me to send the following comment from a private
> >discussion also to the list:
> >
> >Section 3.3 of draft-deng-alto-p2p-ext-01 suggest a new Endpoint
> >Property Type "network_access" for P2P peer selection. As far as I
> >recall, this type of ALTO guidance was discussed in the past quite a
> >bit, and there may have been privacy concerns. For instance,
> >draft-ietf-alto-deployments-09 Section 3.2.4. includes the following
> >statement:
> >
> >o  Performance metrics that raise privacy concerns.  For instance,
> >it has been questioned whether an ALTO service could publicly expose
> >the provisioned access bandwidth, e.g. of cable / DSL customers,
> >because this could enables identification of "premium" customers.
> >
> >That text was already in draft-ietf-alto-deployments before I started
> >to edit this document.
> >
> >For P2P use cases, I wonder whether that concern might (still) apply
> >to endpoint properties such as DSL vs. FTTH as currently suggested
> >draft-deng-alto-p2p-ext-01.
> 
> [As individual, of course.]
> 
> I suspect the type of network access (DSL, cable, FTTH, satellite) is
> probably okay.  Commercial companies often publicly tout the deployment
> of certain access technologies in neighbourhoods.

I know some neighborhoods where FTTH is available, but at very high
prices.  Consequently, many people there prefer to keep their existing
xDSL or cable based Internet service.  If we used ALTO to announce who
decided to pay the high price for FTTH, I would consider this as a
potential privacy concern, because this would be some kind of list of
households with better-than-average income and/or computer professionals
or enthusiasts living there.

Sebastian