Re: [alto] New version: draft-schwan-alto-incr-updates-02.txt
sreekanth madhavan <sreekanthm@huawei.com> Fri, 27 July 2012 05:00 UTC
Return-Path: <sreekanth.madhavan@huawei.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 18A0A21F854F for <alto@ietfa.amsl.com>; Thu, 26 Jul 2012 22:00:45 -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 zuh2C+vm9WYz for <alto@ietfa.amsl.com>; Thu, 26 Jul 2012 22:00:44 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id C314221F853F for <alto@ietf.org>; Thu, 26 Jul 2012 22:00:43 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIC73668; Fri, 27 Jul 2012 01:00:41 -0400 (EDT)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 26 Jul 2012 21:58:15 -0700
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 26 Jul 2012 21:57:58 -0700
Received: from blrprnc03ns (10.18.96.92) by szxeml412-hub.china.huawei.com (10.82.67.91) with Microsoft SMTP Server id 14.1.323.3; Fri, 27 Jul 2012 12:57:55 +0800
From: sreekanth madhavan <sreekanthm@huawei.com>
To: "'Schwan, Nico (Nico)'" <nico.schwan@alcatel-lucent.com>, "'Roome, W D'" <w.roome@alcatel-lucent.com>
References: <E45D69B5D95C074A90D71F60F6A18EF0891BB53FF8@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
In-Reply-To: <E45D69B5D95C074A90D71F60F6A18EF0891BB53FF8@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Date: Fri, 27 Jul 2012 10:27:54 +0530
Message-ID: <002c01cd6bb4$62a8b000$27fa1000$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1jU9pnb89QN6W3SHWam0gr2KsTRQIYAJUQ
Content-Language: en-us
X-Originating-IP: [10.18.96.92]
X-CFilter-Loop: Reflected
Cc: alto@ietf.org
Subject: Re: [alto] New version: draft-schwan-alto-incr-updates-02.txt
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: Fri, 27 Jul 2012 05:00:45 -0000
Hi, I have reviewed the draft. Following are my comments: Section 3.1. HTTP HTTP [RFC2616] provides request-header fields to express conditional requests. Typically these conditional requests are used by caches to decide whether a copy of a resource they have can be served to a requesting client directly or not. Responses to conditional HTTP requests must be exactly the same as for normal HTTP GET requests. Thus sending a modified map version (i.e. a partial update) violates the HTTP standard. Conditional requests can still be used to avoid transmitting an unchanged Map multiple times. The options are discussed in the following. [sreekanth]: RFC 3229 defines how delta encoding can be supported as an compatible extension to HTTP/1.1. Can't we use the same framework for alto incremental updates ? Section 3.1.1: If-Modified-Since HTTP Header [sreekanth]: This timestamp-based approach is prone to error because of the lack of timestamp resolution: if a resource changes twice during one second, the change might not be detectable. It is better to use the ETag. IMO notification based cache invalidation mechanism can be added as an alternate approach. Regards, Sreekanth -----Original Message----- From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of Schwan, Nico (Nico) Sent: Monday, July 16, 2012 6:37 PM To: alto@ietf.org Cc: Roome, W D Subject: [alto] New version: draft-schwan-alto-incr-updates-02.txt All, we have submitted an updated version of the "ALTO Incremental Updates" draft which analyses options for partial updates of ALTO Network and Cost Maps. In this version we have further detailed the solution which is based on Filtered Map Services. As suggested in the last meeting we have also included a short numerical evaluation of the most promising options in the draft. Our main findings are that for more than 100 PIDs partial updates are useful, and that the solution based on Filtered Maps is more efficient than JSON Patch in terms of needed bytes for encoding. Any comments on the discussed options, the numbers, or anything else are welcome! Thanks, Nico -------------- A new version of I-D, draft-schwan-alto-incr-updates-02.txt has been successfully submitted by Nico Schwan and posted to the IETF repository. Filename: draft-schwan-alto-incr-updates Revision: 02 Title: ALTO Incremental Updates Creation date: 2012-07-16 WG ID: Individual Submission Number of pages: 26 URL: http://www.ietf.org/internet-drafts/draft-schwan-alto-incr-updates-02.txt Status: http://datatracker.ietf.org/doc/draft-schwan-alto-incr-updates Htmlized: http://tools.ietf.org/html/draft-schwan-alto-incr-updates-02 Diff: http://tools.ietf.org/rfcdiff?url2=draft-schwan-alto-incr-updates-02 Abstract: The goal of Application-Layer Traffic Optimization (ALTO) is to bridge the gap between network and applications by provisioning network related information. This allows applications to make informed decisions, for example when selecting a target host from a set of candidates. Therefore an ALTO server provides network and cost maps to its clients. This draft discusses options on how to provide incremental updates for these maps, with the goal of reducing the amount of data needed for transmitting the maps and shortly evaluates the two most promising options. _______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
- [alto] New version: draft-schwan-alto-incr-update… Schwan, Nico (Nico)
- Re: [alto] New version: draft-schwan-alto-incr-up… sreekanth madhavan
- Re: [alto] New version: draft-schwan-alto-incr-up… Schwan, Nico (Nico)