Re: [p2pi] Information in an ALTO protocol
Salman Abdul Baset <sa2086@columbia.edu> Thu, 11 September 2008 19:46 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 CAA6928C0EB; Thu, 11 Sep 2008 12:46:12 -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 6CBD43A67B0 for <p2pi@core3.amsl.com>; Thu, 11 Sep 2008 12:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 JXlOVRUvLIGa for <p2pi@core3.amsl.com>; Thu, 11 Sep 2008 12:46:08 -0700 (PDT)
Received: from serrano.cc.columbia.edu (serrano.cc.columbia.edu [128.59.29.6]) by core3.amsl.com (Postfix) with ESMTP id 89B823A6A40 for <p2pi@ietf.org>; Thu, 11 Sep 2008 12:46:08 -0700 (PDT)
Received: from banana.cc.columbia.edu (banana.cc.columbia.edu [128.59.29.54]) by serrano.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id m8BJkAsS019732; Thu, 11 Sep 2008 15:46:10 -0400 (EDT)
Received: from banana.cc.columbia.edu (localhost [127.0.0.1]) by banana.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id m8BJkAmW004417; Thu, 11 Sep 2008 15:46:10 -0400 (EDT)
Received: from localhost (sa2086@localhost) by banana.cc.columbia.edu (8.14.1/8.14.1/Submit) with ESMTP id m8BJkAKY004414; Thu, 11 Sep 2008 15:46:10 -0400 (EDT)
X-Authentication-Warning: banana.cc.columbia.edu: sa2086 owned process doing -bs
Date: Thu, 11 Sep 2008 15:46:10 -0400
From: Salman Abdul Baset <sa2086@columbia.edu>
To: Laird Popkin <laird@pando.com>
In-Reply-To: <193249412.257931221161718300.JavaMail.root@dkny.pando.com>
Message-ID: <alpine.SOC.1.00.0809111538300.3375@banana.cc.columbia.edu>
References: <193249412.257931221161718300.JavaMail.root@dkny.pando.com>
User-Agent: Alpine 1.00 (SOC 882 2007-12-20)
MIME-Version: 1.0
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.63 on 128.59.29.6
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
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