Re: [p2pi] Information in an ALTO protocol
"Ye WANG" <wangye.thu@gmail.com> Mon, 15 September 2008 14:09 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 B61093A69E1; Mon, 15 Sep 2008 07:09:50 -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 16B7B3A69E1 for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 07:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level:
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001]
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 cOxPUgm6m8FG for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 07:09:48 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by core3.amsl.com (Postfix) with ESMTP id 5B9EE3A68F1 for <p2pi@ietf.org>; Mon, 15 Sep 2008 07:09:48 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so670430ywj.49 for <p2pi@ietf.org>; Mon, 15 Sep 2008 07:09:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=hcMxyuPz2Fvz+xa4qG21Zp2VkqJtOk48xw9CIXBkR/Y=; b=HYhPm/GGaGpnJwpSuYusU+dz0AyUQwz1IgUY0OEm/xaAboG7sBWckD7AMO8k5FzxLd 0d93AM96k2/lVHtkzXA/OU1tesTL1QqPNZQH0r7Kd8twQV9woPhW7LdzjTOHpN5qSB3e xccl/Pvr27QemdaFLWc91o4DmZ+tZwlWqLYhM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=F+B0RkrJqbjn4rqnTfoIJoMzOKc3ZkAHE0r5Mw8zAtAz0oefciDL5ypkW/a1+gBfuE lPycn+Lbm8qR1zObV9Xu/QtO7sWdeUlJqz6l0r0m2teh866wqb8DCFKv1iDQq0RcUpPD 4hOXk/Q0yYbBDtSQi8rpElf1WgqEND2rBFqeg=
Received: by 10.142.162.5 with SMTP id k5mr2703037wfe.145.1221487797805; Mon, 15 Sep 2008 07:09:57 -0700 (PDT)
Received: by 10.142.153.2 with HTTP; Mon, 15 Sep 2008 07:09:57 -0700 (PDT)
Message-ID: <2574b1d30809150709n38627b43va5a4e04fa5ec85df@mail.gmail.com>
Date: Mon, 15 Sep 2008 10:09:57 -0400
From: Ye WANG <wangye.thu@gmail.com>
To: p2pi@ietf.org
In-Reply-To: <48cac5ba.14b48c0a.2f5d.ffffc26f@mx.google.com>
MIME-Version: 1.0
References: <48cac5ba.14b48c0a.2f5d.ffffc26f@mx.google.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: multipart/mixed; boundary="===============0018833338=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
On Fri, Sep 12, 2008 at 3:40 PM, Stanislav Shalunov <shalunov@shlang.com>wrote: > Let us put the privacy considertaions aside for a minute. > > I'm actually not even sure how one would use uplink sizes if they were > available, particularly only for some peers. > > The underlying assumption of many messages seems to be that P2P clients > will prefer to connect to higher-uplink peers. While this would help you if > you're the only one doing it, it would hurt everyone if done universally. [Ye (Yale)] We have seen many studies on video streaming applications that prefer higher-uplink-bandwidth peers. I certainly agree with you that the system may somehow get 'blocked' if all clients naively select the highest-uplink peer to be parents. How to efficiently use all upload capacity, especially those higher-uplink peers, is still an interesting problem. > > > The only use I can think of right now that doesn't have obvious adverse > consequences is to prefer peers with uplinks of about the same size as > yours. While this shouldn't reduce average download rate, I'm also not sure > what purpose it would serve. It would make the response to increases in > uplink capacity more linear, but of course it's sublinear by design. > [Ye (Yale)] Analysis based on a fluid model of P2P file sharing system indicates that bandwidth matching can help improve average file download rate. The bandwidth matching can be roughly described like: a peer with download capacity R downloads from the peer whose upload capacity R (=downloader download rate). Thus, for file sharing applications, like Pando, BitTorrent, etc., the uplink/downlink bandwidth information can be useful in system optimization. In the recent P4P field test, we estimated these numbers before using them to compute peering selection weights. Estimation based on measurement is dynamic and less accurate, while direct numbers from ALTO servers may be generally static and more accurate. > > Can someone fill me in on how a P2P app would use provisioned uplink > numbers? > > Thanks, -- Stas > > -----Original Message----- > From: "Laird Popkin" <laird@pando.com> > To: "Salman Abdul Baset" <sa2086@columbia.edu> > Cc: p2pi@ietf.org; "Richard Woundy" <Richard_Woundy@cable.comcast.com> > Sent: 9/11/08 1:28 PM > Subject: Re: [p2pi] Information in an ALTO protocol > > (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 perha > _______________________________________________ > 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