[alto] Caching ALTO
"Thomson, Martin" <Martin.Thomson@commscope.com> Thu, 28 July 2011 17:35 UTC
Return-Path: <Martin.Thomson@commscope.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 04E2E21F8C17 for <alto@ietfa.amsl.com>; Thu, 28 Jul 2011 10:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.577
X-Spam-Level:
X-Spam-Status: No, score=-2.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZWFQDCWtAOd for <alto@ietfa.amsl.com>; Thu, 28 Jul 2011 10:35:22 -0700 (PDT)
Received: from cdcsmgw02.commscope.com (fw.commscope.com [198.135.207.129]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2F321F8B8F for <alto@ietf.org>; Thu, 28 Jul 2011 10:35:22 -0700 (PDT)
X-AuditID: 0a0404e9-b7cc4ae00000074e-7a-4e319de39ae8
Received: from ACDCE7HC2.commscope.com ( [10.86.20.103]) by cdcsmgw02.commscope.com (Symantec Brightmail Gateway) with SMTP id F0.0D.01870.3ED913E4; Thu, 28 Jul 2011 12:35:31 -0500 (CDT)
Received: from SISPE7HC1.commscope.com (10.97.4.12) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.3.159.2; Thu, 28 Jul 2011 12:35:21 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Fri, 29 Jul 2011 01:35:18 +0800
From: "Thomson, Martin" <Martin.Thomson@commscope.com>
To: "alto@ietf.org" <alto@ietf.org>
Date: Fri, 29 Jul 2011 01:35:15 +0800
Thread-Topic: Caching ALTO
Thread-Index: AcxNTLZTbeAPsf+4Q9uAhFBe3cQiMA==
Message-ID: <8B0A9FCBB9832F43971E38010638454F040D2C3928@SISPE7MB1.commscope.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [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: Thu, 28 Jul 2011 17:35:23 -0000
One of the concerns that I had from my brief look at the server implementations on offer the other night was the lack of support for caching mechanisms. Thinking about Robert's request for example scenarios, it seems sensible that EVERY alto flow starts with a request to the IRD. That is, the application always retrieves it, but it is probably cached locally. Caching is going to be key to the scalable performance of this protocol. Implementing that caching in clients is a reasonable starting point, but what I'm seeing right now is that clients are caching on their own. There is no guidance being given by servers. Doing this means that you can't take advantage of the existing caching infrastructure of the web. It's really quite easy. All you need to do is provide Cache-Control headers. --Martin
- Re: [alto] Caching ALTO Vijay K. Gurbani
- [alto] Caching ALTO Thomson, Martin
- Re: [alto] Caching ALTO Richard Alimi
- Re: [alto] Caching ALTO Robert Varga
- Re: [alto] Caching ALTO Picconi Fabio