IETF Logo Mail Archive

Re: [alto] Caching ALTO

Richard Alimi <rich@velvetsea.net> Thu, 28 July 2011 17:43 UTC

Return-Path: <richard.alimi@gmail.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 3E6E921F8B88 for <alto@ietfa.amsl.com>; Thu, 28 Jul 2011 10:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.955
X-Spam-Level:
X-Spam-Status: No, score=-2.955 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 s6DFxarpcfXh for <alto@ietfa.amsl.com>; Thu, 28 Jul 2011 10:43:36 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 94CCD21F8B8F for <alto@ietf.org>; Thu, 28 Jul 2011 10:43:35 -0700 (PDT)
Received: by iye7 with SMTP id 7so3750158iye.31 for <alto@ietf.org>; Thu, 28 Jul 2011 10:43:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=ZyUxwtKUMLp7xwMLzuNrPjrdZZPyDK7cig0cRh2xvXs=; b=r1l3EaGpKhad990diZRBJ/TiSBqU8AxPf+GlTdUSbQKRdcap4PxPkqVfnvnw0Pjiaf qTFmtKqnDLLg+JqxjkvUGNqkR5gLAFu+HOrr4GrNYDGMuqSZiF/sECtIsYBu+gDZ6CtZ A2GW5peRPf4ALwdp/5mL03TeVXOLstXaa+cNY=
Received: by 10.231.119.216 with SMTP id a24mr220278ibr.58.1311875015170; Thu, 28 Jul 2011 10:43:35 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.114.156 with HTTP; Thu, 28 Jul 2011 10:43:15 -0700 (PDT)
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F040D2C3928@SISPE7MB1.commscope.com>
References: <8B0A9FCBB9832F43971E38010638454F040D2C3928@SISPE7MB1.commscope.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Thu, 28 Jul 2011 10:43:15 -0700
X-Google-Sender-Auth: zNvWQs8ak-rQFq0A-uhm6-xwDfg
Message-ID: <CA+cvDaaNjkJ5Kaqdq+z6f2fDvQGiZ4vnsjOWNrx0-A=qtFU71A@mail.gmail.com>
To: "Thomson, Martin" <Martin.Thomson@commscope.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "alto@ietf.org" <alto@ietf.org>
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: Thu, 28 Jul 2011 17:43:37 -0000

I agree that caching here is important, so thank you for bringing this
up.  In particular, beyond the directory, this is also the signal by
which a server indicates to clients when they should to check for
updated network maps and cost maps.  Servers get to suggest this
interval to clients.

Rich

On Thu, Jul 28, 2011 at 10:35 AM, Thomson, Martin
<Martin.Thomson@commscope.com> wrote:
> 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
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

v2.23.0 | Report a Bug | By Email