[p2pi] Information in an ALTO protocol

Enrico Marocco <enrico.marocco@telecomitalia.it> Thu, 07 August 2008 19:20 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 D7B373A6958; Thu, 7 Aug 2008 12:20:12 -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 8E80E3A6958 for <p2pi@core3.amsl.com>; Thu, 7 Aug 2008 12:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.88
X-Spam-Level: *
X-Spam-Status: No, score=1.88 tagged_above=-999 required=5 tests=[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 sbk0EAuTEf2g for <p2pi@core3.amsl.com>; Thu, 7 Aug 2008 12:20:10 -0700 (PDT)
Received: from maild.telecomitalia.it (maild.telecomitalia.it [156.54.233.30]) by core3.amsl.com (Postfix) with ESMTP id 472683A6942 for <p2pi@ietf.org>; Thu, 7 Aug 2008 12:20:10 -0700 (PDT)
Received: from ptpxch010ba020.idc.cww.telecomitalia.it ([156.54.240.53]) by maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Aug 2008 21:20:09 +0200
Received: from grfhub701ba020.griffon.local ([10.188.101.111]) by ptpxch010ba020.idc.cww.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Aug 2008 21:20:09 +0200
Received: from [172.16.82.18] (163.162.180.246) by smtp.telecomitalia.it (10.188.101.114) with Microsoft SMTP Server (TLS) id 8.1.278.0; Thu, 7 Aug 2008 21:20:08 +0200
Message-ID: <489B498B.4040804@telecomitalia.it>
Date: Thu, 07 Aug 2008 21:14:19 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: "p2pi@ietf.org" <p2pi@ietf.org>
X-OriginalArrivalTime: 07 Aug 2008 19:20:09.0252 (UTC) FILETIME=[9B46EE40:01C8F8C2]
Cc: Lisa Dusseault <lisa@osafoundation.org>
Subject: [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: multipart/mixed; boundary="===============2011568660=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

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