IETF Logo Mail Archive

Re: [alto] Caching ALTO

Picconi Fabio <Fabio.Picconi@technicolor.com> Mon, 05 September 2011 11:53 UTC

Return-Path: <Fabio.Picconi@technicolor.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 089FF21F8B44 for <alto@ietfa.amsl.com>; Mon, 5 Sep 2011 04:53:51 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBwdOE0zGMUd for <alto@ietfa.amsl.com>; Mon, 5 Sep 2011 04:53:47 -0700 (PDT)
Received: from na3sys009aog103.obsmtp.com (na3sys009aog103.obsmtp.com [74.125.149.71]) by ietfa.amsl.com (Postfix) with ESMTP id EFDD521F8B3A for <alto@ietf.org>; Mon, 5 Sep 2011 04:53:46 -0700 (PDT)
Received: from indysedge02.am.thmulti.com ([157.254.234.156]) (using TLSv1) by na3sys009aob103.postini.com ([74.125.148.12]) with SMTP ID DSNKTmS4rHbHq5xCHZf72kSKY97+Fbm2EXgM@postini.com; Mon, 05 Sep 2011 04:55:31 PDT
Received: from INDYSMAILHT03.am.thmulti.com (157.254.96.147) by indysedge02.am.thmulti.com (157.254.234.156) with Microsoft SMTP Server (TLS) id 8.3.137.0; Mon, 5 Sep 2011 07:53:36 -0400
Received: from MOPESMAILHC03.eu.thmulti.com (141.11.100.132) by INDYSMAILHT03.am.thmulti.com (157.254.96.147) with Microsoft SMTP Server (TLS) id 8.3.137.0; Mon, 5 Sep 2011 07:53:47 -0400
Received: from MOPESMBX01.eu.thmulti.com ([169.254.1.236]) by MOPESMAILHC03.eu.thmulti.com ([141.11.100.132]) with mapi; Mon, 5 Sep 2011 13:53:45 +0200
From: Picconi Fabio <Fabio.Picconi@technicolor.com>
To: "alto@ietf.org" <alto@ietf.org>
Date: Mon, 05 Sep 2011 13:53:43 +0200
Thread-Topic: [alto] Caching ALTO
Thread-Index: AcxNiD/uzE19VLsiR4WjhMN+l9G8mweNou0Q
Message-ID: <320C4182454E96478DC039F2C48198720426CD14CF@MOPESMBX01.eu.thmulti.com>
References: <8B0A9FCBB9832F43971E38010638454F040D2C3928@SISPE7MB1.commscope.com> <4E31A2D0.9050003@pantheon.sk> <4E320206.2010809@bell-labs.com>
In-Reply-To: <4E320206.2010809@bell-labs.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [alto] Caching ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Sep 2011 11:53:51 -0000

Hi,

I'm posting this only now because August has been a slow month... :-)

Regarding caching, I'm writing a draft on "home-gateway based ALTO proxying/caching". The home gateway seems like a nice place to run an ALTO proxy/cache:

- lookup latency: the home gateway is located within the same LAN as the ALTO client.
- simplified discovery: no need for complex discovery mechanisms; the ALTO client can use uPnP/Bonjour style discovery, or even contact the default route IP address on some well-known port.
- load distribution: a gateway-based ALTO cache will offload the ALTO server.

If the gateway's firmware is managed by the ISP (this is common with triple play plans), the ISP can install the ALTO proxy/cache through a remote firmware upgrade. ISPs which agree to provide ALTO information would probably agree to deploy gateway-based ALTO proxies as well.

If the gateway is managed by the user (e.g., openwrt devices), then users can install the ALTO proxy themselves. They may chose to do so to benefit from the reduction in lookup latency.

I will post the I-D in the following days.

Cheers,

Fabio


-----Original Message-----
From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of Vijay K. Gurbani
Sent: vendredi 29 juillet 2011 02:43
To: Robert Varga
Cc: alto@ietf.org
Subject: Re: [alto] Caching ALTO

On 07/28/2011 12:56 PM, Robert Varga wrote:
> Thanks for bringing this up, as it slipped my mind. Maybe we could
> design a few optional test cases to catch this at the next interop?

Yes, most definitely.

I had a brief chat with Enrico about this, and after the
IETF is over (and we have heaved a collective sigh of
relief), I will reach out to the folks who had contributed
to the test case document and we will turn it into an
Internet-Draft.

Enrico and I will like to maintain this I-D as a living
document to document the test cases etc. as the protocol
progresses, with the intention that the I-D will eventually
become an Informational RFC.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

v2.23.0 | Report a Bug | By Email