Re: [p2pi] Information in an ALTO protocol
Stanislav Shalunov <shalunov@shlang.com> Mon, 18 August 2008 04:31 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 E86C33A6AC0; Sun, 17 Aug 2008 21:31:30 -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 51FC73A6AC0 for <p2pi@core3.amsl.com>; Sun, 17 Aug 2008 21:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.053
X-Spam-Level:
X-Spam-Status: No, score=0.053 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_50=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 5hPucqKz42ck for <p2pi@core3.amsl.com>; Sun, 17 Aug 2008 21:31:29 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by core3.amsl.com (Postfix) with ESMTP id 633C23A6A70 for <p2pi@ietf.org>; Sun, 17 Aug 2008 21:31:29 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so2011072wfd.31 for <p2pi@ietf.org>; Sun, 17 Aug 2008 21:31:36 -0700 (PDT)
Received: by 10.142.49.4 with SMTP id w4mr1893022wfw.201.1219033895615; Sun, 17 Aug 2008 21:31:35 -0700 (PDT)
Received: from ?192.168.1.100? ( [67.188.243.194]) by mx.google.com with ESMTPS id 30sm3557560wfc.5.2008.08.17.21.31.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 17 Aug 2008 21:31:35 -0700 (PDT)
Message-Id: <050C2347-3540-44CB-BB25-8A9EA7CB314A@shlang.com>
From: Stanislav Shalunov <shalunov@shlang.com>
To: Sebastian Kiesel <sebastian.kiesel@nw.neclab.eu>
In-Reply-To: <20080814145914.GA6284@foo.nw.neclab.eu>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Sun, 17 Aug 2008 21:31:32 -0700
References: <489B498B.4040804@telecomitalia.it> <20080811143531.GA18911@net.t-labs.tu-berlin.de> <119D7BAE-4CBB-4BCE-BB3C-594FC6234AB6@shlang.com> <20080814145914.GA6284@foo.nw.neclab.eu>
X-Mailer: Apple Mail (2.926)
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
Live P2P video streaming is an interesting research problem, so far not solved. The business case has also not been proven, with different companies targeting very different uses, from UGC to TV distribution to screencasting. Improving the efficiency of an application that does not yet exist should probably not be in scope for ALTO. As a side note, I don't think the metric of lag is particularly interesting to optimize, and, therefore, I'll be happy to have our competitors use it. The two right metrics are in different units. But let's not go too far down the path of discussing an interesting research topic. -- Stas On Aug 14, 2008, at 7:59 AM, Sebastian Kiesel wrote: > Hi, > > "total transfer rate divided by total upload capacity" is a good > measure > of swarm efficiency if the application is file sharing. > > p2p live video streaming (an application which might gain much > relevance > till the time when a potential ALTO workgroup would deliver their > first > specifications) has differenent metrics: the system can only be stable > if the video stream's bitrate is lower than the average upload > capacity, > i.e., not all uplinks will be saturated by this application. > > The interesting metric is the lag, i.e., the delay of the video stream > between injection into the swarm and playout (measured individually > per > node or as average in the swarm). It can be reduced if nodes with > higher > upload capacity or shorter transport delay from the source are placed > closer to the source in the logical topology. The incentive for a user > to offer more upload capacity to the swarm is to get a smaller > individual lag. > > While p2p algorithms can converge to a "good" state, ALTO guidance > would > be very beneficial if it could speed up that process. This is very > relevant here as many users switch TV channels (streams) frequently. > > Any thoughts? > > Thanks, > Sebastian > > > On Mon, Aug 11, 2008 at 06:16:44PM -0700, Stanislav Shalunov wrote: >> This might be workable and interesting, but here are a few concerns: >> >> 1. For this to be useful, an ISP would need to provide an >> unobfuscated >> third-party service that will tell the world what service plan I >> bought. >> As a user, I'd have a bit of discomfort with it, but the ISP would >> probably >> be a lot more concerned about telling its competitors the fraction >> of its >> customers whom they upsold on a premium plan. I suspect this might >> be a >> real show-stopper. >> >> 2. Nominal provisioned bandwidth on DSL is only an upper bound for >> the >> actual negotiated bandwidth. The negotiation takes a few seconds >> after the >> modem starts and routinely results in lower-than-nominal rates for >> longer >> distances to CO. >> >> 3. While it's obvious that an individual peer will, in the current >> world, >> do better trading with fat-uplink partners, I'm skeptical of >> possibility of >> substantial increases in swarm throughput, which determines the >> average >> outcome. Consider the measure of swarm efficiency: total transfer >> rate >> divided by total upload capacity. I posit that swarm efficiency is >> usually >> quite high, and the only real slack is on super-fast peers in colos >> and >> such. Home connection uplinks are so narrow that it does not take >> much to >> saturate them. >> >> -- Stas > > > > > > -- > Sebastian Kiesel mailto:sebastian.kiesel@nw.neclab.eu > Network Research Division tel:+49-6221-4342-232 fax: > +49-6221-4342-155 > NEC Laboratories Europe Kurfuerstenanlage 36, 69115 Heidelberg, > Germany > -- > NEC Europe Limited Registered in England 2832014 > Registered Office NEC House, 1 Victoria Road, London W3 6BL -- Stanislav Shalunov _______________________________________________ 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