Re: [p2pi] Refining the ALTO problem statement [Was: Re: discussing P2PI-related standardization in Dublin]
Enrico Marocco <enrico.marocco@telecomitalia.it> Fri, 13 June 2008 14:37 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 B0E8A3A6920; Fri, 13 Jun 2008 07:37:37 -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 E6A013A695D for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 07:37:36 -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 rBK+PejUj-qV for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 07:37:33 -0700 (PDT)
Received: from maild.telecomitalia.it (maild.telecomitalia.it [156.54.233.30]) by core3.amsl.com (Postfix) with ESMTP id 667483A6817 for <p2pi@ietf.org>; Fri, 13 Jun 2008 07:37:30 -0700 (PDT)
Received: from ptpxch010ba020.idc.cww.telecomitalia.it ([156.54.240.53]) by maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Jun 2008 16:38:01 +0200
Received: from GRFHUB703BA020.griffon.local ([10.188.101.113]) by ptpxch010ba020.idc.cww.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Jun 2008 16:38:01 +0200
Received: from [10.229.8.35] (10.229.8.35) by smtp.telecomitalia.it (10.188.101.116) with Microsoft SMTP Server (TLS) id 8.1.263.0; Fri, 13 Jun 2008 16:38:00 +0200
Message-ID: <4852862D.9030202@telecomitalia.it>
Date: Fri, 13 Jun 2008 16:37:33 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509)
MIME-Version: 1.0
To: Laird Popkin <laird@pando.com>
References: <565621476.393261213359293462.JavaMail.root@dkny.pando.com>
In-Reply-To: <565621476.393261213359293462.JavaMail.root@dkny.pando.com>
X-Enigmail-Version: 0.95.0
X-OriginalArrivalTime: 13 Jun 2008 14:38:01.0078 (UTC) FILETIME=[14945160:01C8CD63]
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: multipart/mixed; boundary="===============0604211757=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
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