Re: [p2pi] Information in an ALTO protocol
David R Oran <oran@cisco.com> Wed, 27 August 2008 16:59 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 560433A6ACF; Wed, 27 Aug 2008 09:59:52 -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 C80493A694C for <p2pi@core3.amsl.com>; Wed, 27 Aug 2008 09:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 FMiPblAkCjTD for <p2pi@core3.amsl.com>; Wed, 27 Aug 2008 09:59:49 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id E9EC23A6ACF for <p2pi@ietf.org>; Wed, 27 Aug 2008 09:59:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,279,1217808000"; d="scan'208";a="43627661"
Received: from sjc12-sbr-sw3-3f5.cisco.com (HELO imail.cisco.com) ([172.19.96.182]) by sj-iport-5.cisco.com with ESMTP; 27 Aug 2008 16:58:12 +0000
Received: from stealth-10-32-245-150.cisco.com ([10.32.245.150]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id m7RGXNb7022083; Wed, 27 Aug 2008 09:33:23 -0700
Message-Id: <59F52543-CDB0-41FB-991D-7985E8237559@cisco.com>
From: David R Oran <oran@cisco.com>
To: Lisa Dusseault <ldusseault@commerce.net>
In-Reply-To: <91D210DB-C42D-4430-A46C-B6CE10AEA4AE@commerce.net>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Wed, 27 Aug 2008 12:58:09 -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> <BEEA9A6E-26F6-4314-B4B5-EB6396BA3DCF@cisco.com> <91D210DB-C42D-4430-A46C-B6CE10AEA4AE@commerce.net>
X-Mailer: Apple Mail (2.928.1)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2463; t=1219854804; x=1220718804; 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:=20Lisa=20Dusseault=20<ldusseault@commerce.net>; bh=uOVSMym808VVziLJjjh4RuZICCjKddFhOjYHyzGzc94=; b=aAhdGwH8RX6p29vR3YS0HPO2mi3Ycl8xglxJ2aUvphWy2BCVQFcvQzCnXk 6NoSfIIVK9uwcetmmSSpg7hcv9p0j0ra2AOSJPXuBCnnr1oqqKpH5W6mMyAo nk5vpGy+yT;
Authentication-Results: imail.cisco.com; header.From=oran@cisco.com; dkim=pass ( sig from cisco.com/oregon verified; );
Cc: p2pi@ietf.org
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 27, 2008, at 12:51 PM, Lisa Dusseault wrote: > > On Aug 25, 2008, at 12:25 PM, David R Oran wrote: >> >> 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. > > You're making the assumption now, that ALTO will need to add proxies > or intermediaries ("will almost inevitability"). I don't really > have evidence that you're wrong about that, but I also don't see the > use cases right now. Do you have anything specific in mind? > Yeah: 1. my ISP runs a redirector to their "transparent" ALTO server so I can't get directly to the one I want to get to. 2. My P2P "community" wants to cache and do lookaside stuff to provide more globally optimized swarm spreading. So, I use their Alto "proxy" and let them help decide who needs to be asked for what. >> >> >> 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 > > These are good architectural principles to remember while writing > and reviewing drafts, assuming they can be followed without falling > into the trap of designing the be-all and end-all system. > > -- Lisa > >> >> >> 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 >> > _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- [p2pi] Information in an ALTO protocol Enrico Marocco
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Vinay Aggarwal
- Re: [p2pi] Information in an ALTO protocol Lars Eggert
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol chsoft
- Re: [p2pi] Information in an ALTO protocol Vinay Aggarwal
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Nicholas Weaver
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Sebastian Kiesel
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Fabio Hecht
- Re: [p2pi] Information in an ALTO protocol Song Haibin
- Re: [p2pi] Information in an ALTO protocol Vijay K. Gurbani
- Re: [p2pi] Information in an ALTO protocol David R Oran
- Re: [p2pi] Information in an ALTO protocol Spencer Dawkins
- Re: [p2pi] Information in an ALTO protocol Lisa Dusseault
- Re: [p2pi] Information in an ALTO protocol David R Oran
- Re: [p2pi] Information in an ALTO protocol Lisa Dusseault
- Re: [p2pi] Information in an ALTO protocol David R Oran
- Re: [p2pi] Information in an ALTO protocol Reinaldo Penno
- Re: [p2pi] Information in an ALTO protocol Lisa Dusseault
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Reinaldo Penno
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Salman Abdul Baset
- Re: [p2pi] Information in an ALTO protocol Griffiths, Chris
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol stefano previdi
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol stefano previdi
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol stefano previdi
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Ye WANG
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Nicholas Weaver
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Nicholas Weaver
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Philip Levis
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Ye WANG
- Re: [p2pi] Information in an ALTO protocol The 8472
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Salman Abdul Baset