Re: [p2pi] Information in an ALTO protocol
Stanislav Shalunov <shalunov@shlang.com> Fri, 08 August 2008 04:24 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 30E633A6A83; Thu, 7 Aug 2008 21:24:19 -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 6E10B3A69FE for <p2pi@core3.amsl.com>; Thu, 7 Aug 2008 21:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.623
X-Spam-Level:
X-Spam-Status: No, score=-0.623 tagged_above=-999 required=5 tests=[AWL=1.976, BAYES_00=-2.599]
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 RA1AatFirHKc for <p2pi@core3.amsl.com>; Thu, 7 Aug 2008 21:24:16 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by core3.amsl.com (Postfix) with ESMTP id 7BF8E3A6A83 for <p2pi@ietf.org>; Thu, 7 Aug 2008 21:24:16 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so690112wfd.31 for <p2pi@ietf.org>; Thu, 07 Aug 2008 21:24:16 -0700 (PDT)
Received: by 10.142.218.4 with SMTP id q4mr91734wfg.262.1218169456306; Thu, 07 Aug 2008 21:24:16 -0700 (PDT)
Received: from ?192.168.1.103? ( [67.188.243.194]) by mx.google.com with ESMTPS id 32sm1110967wfa.8.2008.08.07.21.24.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 07 Aug 2008 21:24:14 -0700 (PDT)
Message-Id: <A1C4FE8D-B265-44E7-8762-2CB987CA8DA1@shlang.com>
From: Stanislav Shalunov <shalunov@shlang.com>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
In-Reply-To: <489B498B.4040804@telecomitalia.it>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Thu, 07 Aug 2008 21:24:13 -0700
References: <489B498B.4040804@telecomitalia.it>
X-Mailer: Apple Mail (2.926)
Cc: Lisa Dusseault <lisa@osafoundation.org>, "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-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
For what it's worth, I think this is the right kind of information to convey. On Aug 7, 2008, at 12:14 PM, 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 -- 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