Re: [p2pi] Refining the ALTO problem statement [Was: Re: discussing P2PI-related standardization in Dublin]
Laird Popkin <laird@pando.com> Fri, 13 June 2008 15:25 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 E30AB3A69AA; Fri, 13 Jun 2008 08:25:17 -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 657D53A69AA for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 08:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.165
X-Spam-Level:
X-Spam-Status: No, score=-10.165 tagged_above=-999 required=5 tests=[AWL=0.100, 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 G2V+uz-d3ufU for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 08:25:12 -0700 (PDT)
Received: from dkny.pando.com (dkny.pando.com [67.99.55.163]) by core3.amsl.com (Postfix) with ESMTP id 555683A6969 for <p2pi@ietf.org>; Fri, 13 Jun 2008 08:25:12 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by dkny.pando.com (Postfix) with ESMTP id 2C40AE10C17; Fri, 13 Jun 2008 11:25:44 -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 hccSX-lKuIie; Fri, 13 Jun 2008 11:25:40 -0400 (EDT)
Received: from [10.10.20.61] (unknown [10.10.20.61]) by dkny.pando.com (Postfix) with ESMTP id 2DB86E10AD0; Fri, 13 Jun 2008 11:25:40 -0400 (EDT)
Message-Id: <B023B3B2-5A5C-4B2A-B950-5C342B863A7E@pando.com>
From: Laird Popkin <laird@pando.com>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
In-Reply-To: <4852862D.9030202@telecomitalia.it>
Mime-Version: 1.0 (Apple Message framework v924)
Date: Fri, 13 Jun 2008 11:25:39 -0400
References: <565621476.393261213359293462.JavaMail.root@dkny.pando.com> <4852862D.9030202@telecomitalia.it>
X-Mailer: Apple Mail (2.924)
Cc: "p2pi@ietf.org" <p2pi@ietf.org>
Subject: Re: [p2pi] Refining the ALTO problem statement [Was: Re: discussing P2PI-related standardization in Dublin]
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
Yes, I certainly didn't mean to imply that there was any problem with the "oracle" approach or the ALTO proposal - I am a strong supporter of this model. My only concern is that we don't limit our discussion to the one signaling protocol that was used as an example. My apologies if my (perhaps overly detailed) email came across as more negative than I intended. :-) - LP On Jun 13, 2008, at 10:37 AM, Enrico Marocco wrote: > Laird Popkin wrote: >> One point I'll make related to the signaling protocol for querying >> the >> "oracle" is that while the "send in a list of peer IP addresses and >> receive a sorted list back" approach is appealing in its >> simplicity, it >> has some serious limitations that would need to be taken into >> account. > > Actually I used the term "oracle" in a general way, to refer to > servers > providing information useful for peer selection. The "sorting" oracle > is only one proposed approach for addressing the problem of p2p > traffic > optimization. Other competing or complementary approaches, e.g. based > on network coordinates or topology/policy information, have both > advantages and disadvantages in respect to it. > > The main goal of ALTO is to compare the different approaches on a > technical basis with a view towards standardization > > -- > Ciao, > Enrico _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- Re: [p2pi] Refining the ALTO problem statement [W… Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement [W… Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi
- Re: [p2pi] Refining the ALTO problem statement [W… Stephane Bortzmeyer
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement [W… Stephane Bortzmeyer
- Re: [p2pi] Refining the ALTO problem statement [W… Stephane Bortzmeyer
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement [W… Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement [W… Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement [W… Y. R. Yang
- Re: [p2pi] Refining the ALTO problem statement [W… Stephane Bortzmeyer
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi