Re: [alto] 'Link capacity' in scope?
Enrico Marocco <enrico.marocco@telecomitalia.it> Wed, 03 June 2009 15:49 UTC
Return-Path: <enrico.marocco@telecomitalia.it>
X-Original-To: alto@core3.amsl.com
Delivered-To: alto@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB7EE3A68FD for <alto@core3.amsl.com>; Wed, 3 Jun 2009 08:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level:
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 1iFjRBdE7Ei3 for <alto@core3.amsl.com>; Wed, 3 Jun 2009 08:49:49 -0700 (PDT)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by core3.amsl.com (Postfix) with ESMTP id 637123A6805 for <alto@ietf.org>; Wed, 3 Jun 2009 08:49:48 -0700 (PDT)
Received: from GRFHUB701BA020.griffon.local (10.188.101.111) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.1.340.0; Wed, 3 Jun 2009 17:49:46 +0200
Received: from [10.229.8.41] (10.229.8.41) by smtp.telecomitalia.it (10.188.101.114) with Microsoft SMTP Server (TLS) id 8.1.359.3; Wed, 3 Jun 2009 17:49:45 +0200
Message-ID: <4A269B9F.3030802@telecomitalia.it>
Date: Wed, 03 Jun 2009 17:49:51 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
To: Salman Abdul Baset <sa2086@columbia.edu>
References: <C6458CC8.2C43E%jon.peterson@neustar.biz><006601c9e2d2$29cefb90$5c0c7c0a@china.huawei.com><9FE69972-6D13-4BC0-92D5-FBE17FBF18C4@standardstrack.com> <alpine.SOC.1.00.0906021233120.26575@banana.cc.columbia.edu> <04CAD96D4C5A3D48B1919248A8FE0D54096FDEB9@xmb-sjc-215.amer.cisco.com> <alpine.SOC.1.00.0906021752230.20497@banana.cc.columbia.edu>
In-Reply-To: <alpine.SOC.1.00.0906021752230.20497@banana.cc.columbia.edu>
X-Enigmail-Version: 0.95.0
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha1"; boundary="------------ms090408050706000508020105"
Cc: alto <alto@ietf.org>
Subject: Re: [alto] 'Link capacity' in scope?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 15:49:49 -0000
Salman Abdul Baset wrote: > Nevertheless, applications greatly benefit when they can determine the > link speed without measurements, especially if they are running on > a machine which is connected to a WiFi router which in turn is > connected to a DSL/cable modem. Passing the purchased link speed is a > useful hint for p2p applications and for diagnostic purposes. > > My question to the chairs and to the authors of problem statement draft is > whether it is within the scope of ALTO to design a mechanism to pass the > link capacity, that ISP promised to the customer at the time of the > purchase of the plan, to the [A]DSL/high speed modem which passes it to > the devices upstream? The WG has been chartered to define a protocol to provide applications with information to perform better than random peer selection; honestly, I don't see how information about its own link capacity -- assuming it is feasible to determine it in a meaningful way without recurring to realtime measurements -- could help a peer in finding good peers to connect to. So I'd say it is out of scope, but I'd be glad to be proven wrong. OTOH, but as I understand it this is not what you're talking about, information about other peers' link capacity might fall within the scope of ALTO, as it could be useful in peer selection optimization. However, as Rich mentioned, there are many reasons why an ALTO server can't or may not want to pass it. -- Ciao, Enrico
- [alto] WGLC: draft-ietf-alto-problem-statement-01 Jon Peterson
- [alto] Comments to "draft-ietf-alto-problem-state… Linda Dunbar
- Re: [alto] Comments to "draft-ietf-alto-problem-s… Eric Burger
- Re: [alto] Comments to "draft-ietf-alto-problem-s… Linda Dunbar
- [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Ali C. Begen (abegen)
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Woundy, Richard
- Re: [alto] Comments to "draft-ietf-alto-problem-s… Eric Burger
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Randy Turner
- Re: [alto] Comments to "draft-ietf-alto-problem-s… Sebastian Kiesel
- Re: [alto] 'Link capacity' in scope? Sebastian Kiesel
- Re: [alto] Comments to "draft-ietf-alto-problem-s… Eric Burger
- Re: [alto] 'Link capacity' in scope? Enrico Marocco
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? John Leslie
- Re: [alto] 'Link capacity' in scope? Lars Eggert
- Re: [alto] 'Link capacity' in scope? Nicholas Weaver
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Nicholas Weaver
- Re: [alto] 'Link capacity' in scope? John Leslie
- Re: [alto] 'Link capacity' in scope? Enrico Marocco
- Re: [alto] 'Link capacity' in scope? Randy Turner
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Enrico Marocco
- Re: [alto] 'Link capacity' in scope? Woundy, Richard
- Re: [alto] 'Link capacity' in scope? Enrico Marocco
- Re: [alto] 'Link capacity' in scope? Woundy, Richard
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Enrico Marocco
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Enrico Marocco
- Re: [alto] 'Link capacity' in scope? Woundy, Richard
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Matthew Kaufman
- Re: [alto] 'Link capacity' in scope? John Leslie
- Re: [alto] 'Link capacity' in scope? Randy Turner
- Re: [alto] 'Link capacity' in scope? John Leslie
- Re: [alto] 'Link capacity' in scope? Randy Turner
- Re: [alto] 'Link capacity' in scope? Randy Turner
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Lars Eggert
- Re: [alto] 'Link capacity' in scope? Lars Eggert
- Re: [alto] 'Link capacity' in scope? Enrico Marocco
- Re: [alto] 'Link capacity' in scope? Enrico Marocco
- Re: [alto] 'Link capacity' in scope? Lars Eggert
- Re: [alto] 'Link capacity' in scope? John Leslie
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Jan Seedorf
- Re: [alto] 'Link capacity' in scope? Enrico Marocco
- Re: [alto] WGLC: draft-ietf-alto-problem-statemen… Y. Richard Yang
- Re: [alto] 'Link capacity' in scope? Salman Abdul Baset
- Re: [alto] 'Link capacity' in scope? Enrico Marocco
- Re: [alto] WGLC: draft-ietf-alto-problem-statemen… Jan Seedorf
- [alto] FW: WGLC: draft-ietf-alto-problem-statemen… Jan Seedorf
- [alto] Sharing ALTO information (Re: 'Link capaci… Salman Abdul Baset
- Re: [alto] Sharing ALTO information (Re: 'Link ca… Richard Alimi
- Re: [alto] Sharing ALTO information (Re: 'Link ca… Eric Burger