Re: [p2pi] Information in an ALTO protocol

Vinay Aggarwal <vinay@net.t-labs.tu-berlin.de> Mon, 11 August 2008 14:35 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 379273A6E6A; Mon, 11 Aug 2008 07:35:35 -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 4A6E53A6E67 for <p2pi@core3.amsl.com>; Mon, 11 Aug 2008 07:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.351
X-Spam-Level:
X-Spam-Status: No, score=0.351 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_DE=0.35]
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 3txZWk0vDN8P for <p2pi@core3.amsl.com>; Mon, 11 Aug 2008 07:35:32 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [130.149.220.252]) by core3.amsl.com (Postfix) with ESMTP id 11BE43A6E6B for <p2pi@ietf.org>; Mon, 11 Aug 2008 07:35:32 -0700 (PDT)
Received: from crow.net.t-labs.tu-berlin.de (crow.net.t-labs.tu-berlin.de [130.149.220.17]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTP id DE98D705D0C4; Mon, 11 Aug 2008 16:35:31 +0200 (CEST)
Received: by crow.net.t-labs.tu-berlin.de (Postfix, from userid 10007) id 6D7FF4008D97; Mon, 11 Aug 2008 16:35:31 +0200 (CEST)
Date: Mon, 11 Aug 2008 16:35:31 +0200
From: Vinay Aggarwal <vinay@net.t-labs.tu-berlin.de>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
Message-ID: <20080811143531.GA18911@net.t-labs.tu-berlin.de>
References: <489B498B.4040804@telecomitalia.it>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <489B498B.4040804@telecomitalia.it>
User-Agent: Mutt/1.5.11
Cc: "p2pi@ietf.org" <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

Hello,

Regarding what information the ALTO service can provide:

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.

Any thoughts?

Thanks,
Vinay.

-----------------
Vinay Aggarwal
Deutsche Telekom
Germany.


On Thu, Aug 07, 2008 at 09:14:19PM +0200, Enrico Marocco wrote:
> As some people suggested, it may be useful to try to understand what
> kind of information will be provided by an ALTO service.
> 
> Current version of the charter lists four pieces of information:
> + routing preferences and priority values. The network operator is
>   usually the only entity in possession of such information, but it is
>   in its interests to share at least part of it with applications, in
>   order to reduce traffic on critical links. On the other hand, if
>   following such preferences leads to better-than-random choices, it is
>   also in applications' interest to follow them;
> + AS numbers and approximate geographic locations. Such information is
>   today (partially) available and, in fact, is in some cases already
>   used for peer selection. However, since there is no standard way to
>   obtain it, it is not easy for applications to switch from an
>   information provider to another.
> 
> The charter does not preclude any other kind of information entirely,
> but it sets the bar pretty high, requiring that:
> 
>   When the WG considers standardizing schemas, measures or other
>   information that the ALTO service could provide, the following
>   criteria are important to ensure real feasibility.
>   - Can an ALTO service technically provide that information?
>   - Is the ALTO service willing to obtain and divulge that information?
>   - Is it information that some client will find useful?
>   - Can that client get that information without excessive privacy
>     concerns (e.g. by sending large lists of peers)?
>   - Is it information that clients cannot find easily some other way?
> 
> Thoughts?
> 
> -- 
> Ciao,
> Enrico



> _______________________________________________
> 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