[p2pi] ALTO Information Export Service

Stanislav Shalunov <shalunov@shlang.com> Mon, 27 October 2008 23:17 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 E0C1528C0E0; Mon, 27 Oct 2008 16:17:28 -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 54A293A6813 for <p2pi@core3.amsl.com>; Mon, 27 Oct 2008 16:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.823
X-Spam-Level:
X-Spam-Status: No, score=-1.823 tagged_above=-999 required=5 tests=[AWL=-0.777, BAYES_00=-2.599, HTML_IMAGE_ONLY_24=1.552, HTML_MESSAGE=0.001]
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 ezZIA6aG0HBa for <p2pi@core3.amsl.com>; Mon, 27 Oct 2008 16:17:26 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by core3.amsl.com (Postfix) with ESMTP id CA5C33A6BBC for <p2pi@ietf.org>; Mon, 27 Oct 2008 16:17:19 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so2500089wfd.31 for <p2pi@ietf.org>; Mon, 27 Oct 2008 16:17:03 -0700 (PDT)
Received: by 10.142.240.19 with SMTP id n19mr2984530wfh.191.1225149423071; Mon, 27 Oct 2008 16:17:03 -0700 (PDT)
Received: from ?192.168.1.103? (c-67-188-243-194.hsd1.ca.comcast.net [67.188.243.194]) by mx.google.com with ESMTPS id 24sm1363740wff.17.2008.10.27.16.17.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 27 Oct 2008 16:17:01 -0700 (PDT)
Message-Id: <127D035B-1B67-4168-9DFE-90C55173562D@shlang.com>
From: Stanislav Shalunov <shalunov@shlang.com>
To: p2pi@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 16:16:59 -0700
X-Mailer: Apple Mail (2.929.2)
Cc: Richard Woundy <Richard_Woundy@cable.comcast.com>
Subject: [p2pi] ALTO Information Export Service
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="===============1370749547=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

We put together a first iteration of a very simple ALTO solution  
draft.  We hope this will be useful as an example point in the  
solutions space and thus allow to refine the requirements document and  
the problem statement.

http://www.ietf.org/internet-drafts/draft-shalunov-alto-infoexport-00.txt

Abstract

    The ALTO Information Export Service is a simple way to convey ISP
    routing policy preferences to applications.  Applications that could
    use this service are those that have a choice in connection
    endpoints.  Examples of such applications are peer-to-peer and
    content delivery networks.

    Applications already have access to great amount of underlying
    topology information.  For example, views of the Internet routing
    table are easily available at looking glass servers and entirely
    practical to download to every client.  What is missing is the
    routing policy information -- what does the local ISP actually
    prefer?

    This document describes a very simple mechanism that would allow to
    export such information to applications.  While such service would
    primarily be provided by the network, i.e., the local ISP, third
    parties could also operate this service.


--
Stanislav Shalunov



_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi