Re: [p2pi] Information in an ALTO protocol

Laird Popkin <laird@pando.com> Mon, 11 August 2008 15:11 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 94EAD3A6CFC; Mon, 11 Aug 2008 08:11:31 -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 F33273A6CE2 for <p2pi@core3.amsl.com>; Mon, 11 Aug 2008 08:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.115
X-Spam-Level:
X-Spam-Status: No, score=-10.115 tagged_above=-999 required=5 tests=[AWL=0.150, 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 sHqx9VJ+0yTT for <p2pi@core3.amsl.com>; Mon, 11 Aug 2008 08:11:29 -0700 (PDT)
Received: from dkny.pando.com (dkny.pando.com [67.99.55.163]) by core3.amsl.com (Postfix) with ESMTP id C17013A65A6 for <p2pi@ietf.org>; Mon, 11 Aug 2008 08:11:29 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by dkny.pando.com (Postfix) with ESMTP id DC663E10B22; Mon, 11 Aug 2008 11:11:28 -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 nt-2jPsoWBLc; Mon, 11 Aug 2008 11:11:20 -0400 (EDT)
Received: from dkny.pando.com (dkny.pando.com [10.10.60.11]) by dkny.pando.com (Postfix) with ESMTP id 52A91E10AF6; Mon, 11 Aug 2008 11:11:20 -0400 (EDT)
Date: Mon, 11 Aug 2008 11:11:20 -0400
From: Laird Popkin <laird@pando.com>
To: Lars Eggert <lars.eggert@nokia.com>
Message-ID: <735025520.120641218467480318.JavaMail.root@dkny.pando.com>
In-Reply-To: <E3361EDE-EDC6-4EF0-9249-B87B6C2D349C@nokia.com>
MIME-Version: 1.0
X-Originating-IP: [10.10.20.79]
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

There would certainly be value in differentiating between classes of users in terms of their nominal uplink capacity. For example, an ISP with a mix of DSL and FTTH customers would probably prefer that p2p data download from FTTH rather than DSL sources.

I agree that ALTO shouldn't try to know real-time consumption rates vs. capacity. That's (IMO) a question to ask something local to the user, not from a centralized service.

- Laird Popkin, CTO, Pando Networks
  mobile: 646/465-0570

----- Original Message -----
From: "Lars Eggert" <lars.eggert@nokia.com>
To: "ext Vinay Aggarwal" <vinay@net.t-labs.tu-berlin.de>
Cc: p2pi@ietf.org
Sent: Monday, August 11, 2008 11:00:47 AM (GMT-0500) America/New_York
Subject: Re: [p2pi] Information in an ALTO protocol

Hi,

On 2008-8-11, at 17:35, ext Vinay Aggarwal wrote:
> I think an estimate of "last-hop bandwidth" can be an interesting  
> metric
> of information for peer selection.
> It has been shown that selecting peers with high last-hop bandwidth  
> lead
> to improvements in download performance. And this is information  
> that is
> rather hard for peers to find out themselves. As far as I can see, it
> also satisfies all the bars set up by the ALTO service.

Uplink or downlink bandwidth?

Provisioned bandwidth (i.e., the nominal bandwidth a user is paying  
for) or the currently available fraction of it? The latter would be  
something that I doubt an ALTO box can have an accurate view of, since  
it changes on short timescales.

Could you share a reference to papers that show that that information  
is beneficial?

Thanks,
Lars
_______________________________________________
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