Re: [p2pi] Information in an ALTO protocol
"Griffiths, Chris" <Chris_Griffiths@Cable.Comcast.com> Thu, 11 September 2008 20:27 UTC
Return-Path: <p2pi-bounces@ietf.org>
X-Original-To: p2pi-archive@ietf.org
Delivered-To: ietfarch-p2pi-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B1403A68CE; Thu, 11 Sep 2008 13:27:31 -0700 (PDT)
X-Original-To: p2pi@core3.amsl.com
Delivered-To: p2pi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 127483A68CE for <p2pi@core3.amsl.com>; Thu, 11 Sep 2008 13:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level:
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TKCeu0JZvhbD for <p2pi@core3.amsl.com>; Thu, 11 Sep 2008 13:27:29 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 0849A3A68C0 for <p2pi@ietf.org>; Thu, 11 Sep 2008 13:27:28 -0700 (PDT)
Received: from ([10.52.116.31]) by pacdcimo01.cable.comcast.com with ESMTP id 5503620.13785266; Thu, 11 Sep 2008 16:27:05 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Sep 2008 16:27:05 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 11 Sep 2008 16:26:12 -0400
Message-ID: <BCC2697F27AE0A44951FCD9D7DE96FDC03215AB1@PACDCEXCMB06.cable.comcast.com>
In-Reply-To: <193249412.257931221161718300.JavaMail.root@dkny.pando.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [p2pi] Information in an ALTO protocol
Thread-Index: AckURfIARhQmJASKRmquaH6aSUyXGgABSjFg
References: <74CCBBDF76102846AFA7B29F3A98D3F60107C4DB@PACDCEXCMB06.cable.comcast.com> <193249412.257931221161718300.JavaMail.root@dkny.pando.com>
From: "Griffiths, Chris" <Chris_Griffiths@Cable.Comcast.com>
To: Laird Popkin <laird@pando.com>, "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
X-OriginalArrivalTime: 11 Sep 2008 20:27:05.0306 (UTC) FILETIME=[C17D63A0:01C9144C]
Cc: p2pi@ietf.org
Subject: Re: [p2pi] Information in an ALTO protocol
X-BeenThere: p2pi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: P2P Infrastructure Discussion <p2pi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2pi>
List-Post: <mailto:p2pi@ietf.org>
List-Help: <mailto:p2pi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
> Playing devil's advocate, while ALTO doesn't provide a mechanism for > ISP A to tell non-customers anything, but it is possible for the p2p > network as a whole to make decisions based on information provided by > ALTO. For example, if ISP A says that its users have bad uplink, and > ISP B says that its customers have great uplink, then the rest of the > internet will tend to download more from ISP B than A. While I don't disagree that this is possible, I would still expect ALTO to verify this data in some way, or have clients from ISP A also provide data to substantiate this. >I agree with the point about privacy. If ALTO tells a p2p client on my >computer that I have 15 Mbps down and 5 Mbps up, that client can report >it to the p2p network, etc. Of course, without ALTO the app can still >measure throughput and report that, and there are plenty of web sites >with such analysis. But arguably there's a difference between consumer- >collected performance data and ISP-provided provisioning data. I would expect that the amount of information (IE: provisioning data) would be adjustable based on the desire of the ISP to present needed data for the p2p network and/or client to make the determination on bandwidth speeds. It is also necessary that this information and user information stay private. >----- Original Message ----- >From: "Richard Woundy" <Richard_Woundy@cable.comcast.com> >To: "Reinaldo Penno" <rpenno@juniper.net>, "Laird Popkin" ><laird@pando.com> >Cc: p2pi@ietf.org >Sent: Thursday, September 11, 2008 2:52:06 PM (GMT-0500) >America/New_York >Subject: RE: [p2pi] Information in an ALTO protocol > >> I was wondering if he was assuming some kind inter-ALTO communication. > >I guess I was. And perhaps Laird's points address my ISP traffic >management concerns -- I'm willing to concede. > >Still worried about user privacy, though. > >-- Rich > >-----Original Message----- >From: p2pi-bounces@ietf.org [mailto:p2pi-bounces@ietf.org] On Behalf Of >Reinaldo Penno >Sent: Thursday, September 11, 2008 2:31 PM >To: Laird Popkin; Woundy, Richard >Cc: p2pi@ietf.org >Subject: Re: [p2pi] Information in an ALTO protocol > >That was going to be my observation to Rich's point as well. I was >wondering >if he was assuming some kind inter-ALTO communication. But even if >existed >it would not be Internet wide. > > >On 9/11/08 11:26 AM, "Laird Popkin" <laird@pando.com> wrote: > >> The other issue is that ALTO is anticipated to be used by ISPs to >provide >> guidance to their own users. ALTO can't provide guidance to customers >of other >> ISPs. So ISP A cannot tell the rest of the internet to pull data from >ISP B >> but not ISP A. > >_______________________________________________ >p2pi mailing list >p2pi@ietf.org >https://www.ietf.org/mailman/listinfo/p2pi >_______________________________________________ >p2pi mailing list >p2pi@ietf.org >https://www.ietf.org/mailman/listinfo/p2pi _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- [p2pi] Information in an ALTO protocol Enrico Marocco
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Vinay Aggarwal
- Re: [p2pi] Information in an ALTO protocol Lars Eggert
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol chsoft
- Re: [p2pi] Information in an ALTO protocol Vinay Aggarwal
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Nicholas Weaver
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Sebastian Kiesel
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Fabio Hecht
- Re: [p2pi] Information in an ALTO protocol Song Haibin
- Re: [p2pi] Information in an ALTO protocol Vijay K. Gurbani
- Re: [p2pi] Information in an ALTO protocol David R Oran
- Re: [p2pi] Information in an ALTO protocol Spencer Dawkins
- Re: [p2pi] Information in an ALTO protocol Lisa Dusseault
- Re: [p2pi] Information in an ALTO protocol David R Oran
- Re: [p2pi] Information in an ALTO protocol Lisa Dusseault
- Re: [p2pi] Information in an ALTO protocol David R Oran
- Re: [p2pi] Information in an ALTO protocol Reinaldo Penno
- Re: [p2pi] Information in an ALTO protocol Lisa Dusseault
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Reinaldo Penno
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Salman Abdul Baset
- Re: [p2pi] Information in an ALTO protocol Griffiths, Chris
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol stefano previdi
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol stefano previdi
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol stefano previdi
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Ye WANG
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Nicholas Weaver
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Nicholas Weaver
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Philip Levis
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Ye WANG
- Re: [p2pi] Information in an ALTO protocol The 8472
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Salman Abdul Baset