Re: [p2pi] Information in an ALTO protocol
Laird Popkin <laird@pando.com> Thu, 11 September 2008 20:28 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 64CDD28C2A4; Thu, 11 Sep 2008 13:28:02 -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 C82F028C287 for <p2pi@core3.amsl.com>; Thu, 11 Sep 2008 13:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.004
X-Spam-Level:
X-Spam-Status: No, score=-10.004 tagged_above=-999 required=5 tests=[AWL=0.261, BAYES_00=-2.599, HABEAS_ACCREDITED_COI=-8, IP_NOT_FRIENDLY=0.334]
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 DNi-3GcsoY8v for <p2pi@core3.amsl.com>; Thu, 11 Sep 2008 13:28:00 -0700 (PDT)
Received: from dkny.pando.com (dkny.pando.com [67.99.55.163]) by core3.amsl.com (Postfix) with ESMTP id B40C228C25C for <p2pi@ietf.org>; Thu, 11 Sep 2008 13:28:00 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by dkny.pando.com (Postfix) with ESMTP id 9DB95E10D16; Thu, 11 Sep 2008 16:28:07 -0400 (EDT)
X-Virus-Scanned: amavisd-new at
Received: from dkny.pando.com ([127.0.0.1]) by localhost (dkny.pando.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GBmS3L0kBt-Z; Thu, 11 Sep 2008 16:28:00 -0400 (EDT)
Received: from dkny.pando.com (dkny.pando.com [10.10.60.11]) by dkny.pando.com (Postfix) with ESMTP id 60899E10D12; Thu, 11 Sep 2008 16:28:00 -0400 (EDT)
Date: Thu, 11 Sep 2008 16:28:00 -0400
From: Laird Popkin <laird@pando.com>
To: Salman Abdul Baset <sa2086@columbia.edu>
Message-ID: <284285064.257961221164880361.JavaMail.root@dkny.pando.com>
In-Reply-To: <alpine.SOC.1.00.0809111538300.3375@banana.cc.columbia.edu>
MIME-Version: 1.0
X-Originating-IP: [71.187.59.213]
Cc: p2pi@ietf.org, Richard Woundy <Richard_Woundy@cable.comcast.com>
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
(1) If an ISP configures their ALTO server to tell applications that the users' uplink is less than it really is, I think that could have two effects. For users inside the ISP, it would tend to suppress internal traffic and cause peers to download from external peers, which is probably bad for the ISP. And it might tend to cause peers from outside the ISP to shift traffic elsewhere to some degree, which would reduce uplink utilization, which would be an incentive to 'aim low'. How these two factors would balance out would depend on the ISP's infrastructure. (2) I don't believe that the p2p network would have to decide that the ISP's ALTO server was 'lying'. P2P networks all currently measure observed throughput between peers and use that to make decisions. If they add ALTO provisioning information, I would expect that they would treat observed throughput as being more true than the ALTO guidance. So without having to make a decision about 'ALTO lying' the p2p network would tend to take advantage of good ALTO guidance (because ALTO guidance and p2p performance optimization reinforce each other) and would tend to cancel out bad ALTO guidance (because the p2p performance optimization would end up overruling the ALTO guidance). - Laird Popkin, CTO, Pando Networks mobile: 646/465-0570 ----- Original Message ----- From: "Salman Abdul Baset" <sa2086@columbia.edu> To: "Laird Popkin" <laird@pando.com> Cc: "Richard Woundy" <Richard_Woundy@cable.comcast.com>, p2pi@ietf.org Sent: Thursday, September 11, 2008 3:46:10 PM (GMT-0500) America/New_York Subject: Re: [p2pi] Information in an ALTO protocol This raises at least two issues: > 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. (1) Do ISPs have an incentive to lie to their customers that their uplink is bad? This will be counter-balanced > in that if, in practice, ISP A has fine uplink, the p2p network will > figure that out and use those peers anyway, ignoring the misleading ALTO > guidance, because observed behavior has (IMO) more 'weight' than ALTO > guidance. (2) Do P2P applications must determine if an ISP ALTO server is lying? Note, that misconfiguration can also be a cause of ALTO server providing misleading information. -s > > ----- 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