IETF Logo Mail Archive

Re: [p2pi] Refining the ALTO problem statement

"Stanislav Shalunov" <shalunov@shlang.com> Thu, 26 June 2008 00:43 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 178B13A68F8; Wed, 25 Jun 2008 17:43:42 -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 6FE0D3A6813 for <p2pi@core3.amsl.com>; Mon, 23 Jun 2008 16:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 f81EXcL4Yftv for <p2pi@core3.amsl.com>; Mon, 23 Jun 2008 16:58:39 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by core3.amsl.com (Postfix) with ESMTP id 24BBA3A67FB for <p2pi@ietf.org>; Mon, 23 Jun 2008 16:58:39 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so7702945rvf.49 for <p2pi@ietf.org>; Mon, 23 Jun 2008 16:58:39 -0700 (PDT)
Received: by 10.141.197.14 with SMTP id z14mr13584276rvp.283.1214265519582; Mon, 23 Jun 2008 16:58:39 -0700 (PDT)
Received: by 10.150.196.13 with HTTP; Mon, 23 Jun 2008 16:58:39 -0700 (PDT)
Message-ID: <dfa4ab960806231658m9d978dev4216aedbdd32079e@mail.gmail.com>
Date: Mon, 23 Jun 2008 16:58:39 -0700
From: Stanislav Shalunov <shalunov@shlang.com>
To: John Leslie <john@jlc.net>
In-Reply-To: <20080623164523.GB26944@verdi>
MIME-Version: 1.0
Content-Disposition: inline
References: <7335188A-BA0A-48E6-9D6B-9E4F6F09A4C6@nokia.com> <00b601c8cfb5$3aa68180$6401a8c0@china.huawei.com> <20080616173953.GF3759@verdi> <C3D5E72B-76D4-47A0-8CD8-830E5B2E0F33@nokia.com> <20080623164523.GB26944@verdi>
X-Mailman-Approved-At: Wed, 25 Jun 2008 17:43:40 -0700
Cc: p2pi@ietf.org
Subject: Re: [p2pi] Refining the ALTO problem statement
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

On Mon, Jun 23, 2008 at 9:45 AM, John Leslie <john@jlc.net> wrote:
>   P2P applications have good reason to want to know (instantaneous)
> congestion, and what the likelihood is that the congestion will get
> better or worse soon.

This is the function of transport.  P2P apps, by doing e2e
measurements, already have pretty decent information about state of
congestion, and use it just the way you'd expect.

What P2P apps don't have, and what ALTO should provide, is new
information -- not whether a path is congested, but whether a path is
preferred by the ISP.  Some simple notion of cost or preferred ASes or
IP prefixes or whatnot.

This is information that the routing layer has and that the overlay
routing in P2P has no access to.

--
Stanislav Shalunov
http://shlang.com/
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi

v2.29.0 | Report a Bug | By Email | System Status