IETF Logo Mail Archive

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

"Vijay K. Gurbani" <vkg@bell-labs.com> Mon, 30 June 2014 13:51 UTC

Return-Path: <vkg@bell-labs.com>
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 E89731A0351 for <alto@ietfa.amsl.com>; Mon, 30 Jun 2014 06:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5] 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 Fw1TSBekucYq for <alto@ietfa.amsl.com>; Mon, 30 Jun 2014 06:50:57 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A92A1A0344 for <alto@ietf.org>; Mon, 30 Jun 2014 06:50:55 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s5UDolOt023946 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 30 Jun 2014 08:50:47 -0500 (CDT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s5UDok73018822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 30 Jun 2014 08:50:47 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.169]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s5UDok0M017012; Mon, 30 Jun 2014 08:50:46 -0500 (CDT)
Message-ID: <53B16BD3.3070807@bell-labs.com>
Date: Mon, 30 Jun 2014 08:53:23 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Songhaibin (A)" <haibin.song@huawei.com>, "alto@ietf.org" <alto@ietf.org>
References: <655C07320163294895BBADA28372AF5D16593352@FR712WXCHMBA13.zeu.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F65115E6E@nkgeml501-mbs.china.huawei.com> <53ADA961.80206@bell-labs.com> <E33E01DFD5BEA24B9F3F18671078951F65117486@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F65117486@nkgeml501-mbs.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Archived-At: http://mailarchive.ietf.org/arch/msg/alto/hUbJE2G6g88R2H7TxtSQndbhyMU
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 13:51:01 -0000

On 06/28/2014 01:00 AM, Songhaibin (A) wrote:
>> Perhaps a midway could be to see if we can use the provisioned
>> bandwidth for a set of (anonymous) subscribers instead of singleton
>> subscribers. That way, the larger herd provides some modicum of
>> anonymity to an individual subscriber who is part of the herd.
>
> So just ranking a list of endpoints from the perspective of
> provisioned bandwidth will alleviate the privacy issue. I think it is
> possible to do it in this way.

Haibin: Yes, that is one potential way to alleviate the privacy issue
if a provisioned bandwidth is necessary for an ALTO service.  Reinaldo
has provided some input as well; my preference would be to start
thinking of such privacy issues right at the onset so we have a
reasonable idea of the pros and cons of any solution that the WG
comes up with.

Cheers,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

v2.23.0 | Report a Bug | By Email