Re: [p2pi] Information in an ALTO protocol

David R Oran <oran@cisco.com> Mon, 25 August 2008 19: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 98DC33A696C; Mon, 25 Aug 2008 12:25:50 -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 A9DE53A696C for <p2pi@core3.amsl.com>; Mon, 25 Aug 2008 12:25:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.11
X-Spam-Level:
X-Spam-Status: No, score=-5.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
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 2K4fEdxsuFZY for <p2pi@core3.amsl.com>; Mon, 25 Aug 2008 12:25:48 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 2D1D23A68B3 for <p2pi@ietf.org>; Mon, 25 Aug 2008 12:25:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,266,1217808000"; d="scan'208";a="69219791"
Received: from sjc12-sbr-sw3-3f5.cisco.com (HELO imail.cisco.com) ([172.19.96.182]) by sj-iport-1.cisco.com with ESMTP; 25 Aug 2008 19:25:35 +0000
Received: from stealth-10-32-245-152.cisco.com ([10.32.245.152]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id m7PJ0ssv009877 for <p2pi@ietf.org>; Mon, 25 Aug 2008 12:00:54 -0700
Message-Id: <BEEA9A6E-26F6-4314-B4B5-EB6396BA3DCF@cisco.com>
From: David R Oran <oran@cisco.com>
To: p2pi@ietf.org
In-Reply-To: <48AAD5EF.5030303@alcatel-lucent.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Mon, 25 Aug 2008 15:25:33 -0400
References: <489B498B.4040804@telecomitalia.it> <20080811143531.GA18911@net.t-labs.tu-berlin.de> <E3361EDE-EDC6-4EF0-9249-B87B6C2D349C@nokia.com> <df9ced400808110837n57c79866se83369300812975e@mail.gmail.com> <20080811165443.GB18911@net.t-labs.tu-berlin.de> <1219070969.6961.37.camel@bart2> <48AAD5EF.5030303@alcatel-lucent.com>
X-Mailer: Apple Mail (2.928.1)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2079; t=1219690855; x=1220554855; c=relaxed/simple; s=oregon; h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=oran@cisco.com; z=From:=20David=20R=20Oran=20<oran@cisco.com> |Subject:=20Re=3A=20[p2pi]=20Information=20in=20an=20ALTO=2 0protocol |Sender:=20 |To:=20p2pi@ietf.org; bh=/J/6xfvIhiCfAiRk47MshCqQLaFpNf5na4TjokWABBQ=; b=evo6nunsQWWz/ZuLRpAHwLAPxujtN+wHaPfI9niU4HdPjBJyar56bA5wyV ZHjl0QBmTtj5oJ2gw7x0GP+qDeK/dClCfMEd6IHq1rkEQ18eS/S9YTKZgbjK /9AO9fHnoi;
Authentication-Results: imail.cisco.com; header.From=oran@cisco.com; dkim=pass ( sig from cisco.com/oregon verified; );
Subject: Re: [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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

On Aug 19, 2008, at 10:17 AM, Vijay K. Gurbani wrote:

> Fabio Hecht wrote:
>> in this case, would an ALTO Server query other ALTO Servers to gather
>> this information? Because, from an ISP point of view, the ALTO Server
>> would not know what the last-hop bandwidth is for every other peer.
>> Would the protocol then be the same used by the overlay applications?
>
> Fabio: At this point, not much thought has been given to an Inter-ALTO
> server protocol or what its form may be.  We are trying to get our
> hands around the needed information that could serve as the building
> block for an ALTO server - ALTO client protocol.
>
This is only tangentially related to the main topic of this thread,  
but since it occurred to me on reading this exchange about server  
chaining I thought I'd mention it here:

Many client/server protocols are were initially designed to be  
strictly two party, with no architectural support for proxies or other  
stateful intermediaries (HTTP and RTSP come to mind...there are likely  
many others).

It may behoove us to build proxy capability into ALTO from day 1,  
since it will almost inevitably have to be added later at some level  
of pain, perhaps large, and almost assuredly some undesirable security  
tradeoffs.

This probably involves at least the following:
- separating our end-to-end from ho--by hop (transport layer?) security
- clear data model separation between things used to "route" requests  
and things used to interpret queries.
- a flexible addressing model
- a way to aggregate and summarize in responses

and likely a bunch of other considerations I'm missing in the above.

DaveO.

> Thanks,
>
> - vijay
> -- 
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
> Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
> WWW:   http://www.alcatel-lucent.com/bell-labs
> _______________________________________________
> p2pi mailing list
> p2pi@ietf.org
> https://www.ietf.org/mailman/listinfo/p2pi

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