[alto] New version: draft-schwan-alto-incr-updates-02.txt
"Schwan, Nico (Nico)" <nico.schwan@alcatel-lucent.com> Mon, 16 July 2012 13:06 UTC
Return-Path: <nico.schwan@alcatel-lucent.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 7E3D321F87FD for <alto@ietfa.amsl.com>; Mon, 16 Jul 2012 06:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level:
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
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 YewN3pwk-rVk for <alto@ietfa.amsl.com>; Mon, 16 Jul 2012 06:06:19 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 937BD21F8532 for <alto@ietf.org>; Mon, 16 Jul 2012 06:06:19 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q6GD6xlU005825 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 16 Jul 2012 15:07:00 +0200
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.55]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Mon, 16 Jul 2012 15:06:47 +0200
From: "Schwan, Nico (Nico)" <nico.schwan@alcatel-lucent.com>
To: "alto@ietf.org" <alto@ietf.org>
Date: Mon, 16 Jul 2012 15:06:46 +0200
Thread-Topic: New version: draft-schwan-alto-incr-updates-02.txt
Thread-Index: Ac1jU9pnb89QN6W3SHWam0gr2KsTRQ==
Message-ID: <E45D69B5D95C074A90D71F60F6A18EF0891BB53FF8@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "Roome, W D" <w.roome@alcatel-lucent.com>
Subject: [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: Mon, 16 Jul 2012 13:06:20 -0000
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] 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)