Re: [alto] A unified approach to value schemas and ALTO maps

Wendy Roome <wendy.roome@nokia-bell-labs.com> Wed, 27 July 2016 14:10 UTC

Return-Path: <wendy.roome@nokia-bell-labs.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 F341F12D98D for <alto@ietfa.amsl.com>; Wed, 27 Jul 2016 07:10:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r33Ws3MAyTkk for <alto@ietfa.amsl.com>; Wed, 27 Jul 2016 07:10:50 -0700 (PDT)
Received: from smtp-us.alcatel-lucent.com (us-hpswa-esg-01.alcatel-lucent.com [135.245.18.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8806F12D97B for <alto@ietf.org>; Wed, 27 Jul 2016 07:10:50 -0700 (PDT)
Received: from us70uumx3.dmz.alcatel-lucent.com (unknown [135.245.18.15]) by Websense Email Security Gateway with ESMTPS id D89C0DC73A50F for <alto@ietf.org>; Wed, 27 Jul 2016 14:10:46 +0000 (GMT)
Received: from us70uusmtp3.zam.alcatel-lucent.com (us70uusmtp3.zam.alcatel-lucent.com [135.5.2.65]) by us70uumx3.dmz.alcatel-lucent.com (GMO) with ESMTP id u6REAmua004358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Wed, 27 Jul 2016 14:10:49 GMT
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id u6REAmnm011864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jul 2016 14:10:48 GMT
Received: from [135.222.152.71] (wdr-i7mbp2.mh.lucent.com [135.222.152.71]) by umail.lucent.com (8.13.8/TPES) with ESMTP id u6REAhjw013066; Wed, 27 Jul 2016 09:10:45 -0500 (CDT)
User-Agent: Microsoft-MacOutlook/14.6.6.160626
Date: Wed, 27 Jul 2016 10:10:46 -0400
From: Wendy Roome <wendy.roome@nokia-bell-labs.com>
To: "Vijay K. Gurbani" <vijay.gurbani@nokia-bell-labs.com>, Wendy Roome <wendy.roome@nokia-bell-labs.com>, IETF ALTO <alto@ietf.org>
Message-ID: <D3BE359A.811156%w.roome@alcatel-lucent.com>
Thread-Topic: [alto] A unified approach to value schemas and ALTO maps
References: <D3BD183E.80D4FC%w.roome@alcatel-lucent.com> <5d97f6d3-1fb4-de8a-92fe-4ac36268584a@nokia-bell-labs.com>
In-Reply-To: <5d97f6d3-1fb4-de8a-92fe-4ac36268584a@nokia-bell-labs.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/93BVAiOD1ZvrAHkXJJmiyJpaQqg>
Subject: Re: [alto] A unified approach to value schemas and ALTO maps
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 27 Jul 2016 14:10:52 -0000

Vijay,

It would not obsolete rfc7285, but it would deprecate much of it. An ALTO
server would continue to provide network maps, cost maps, ECS, EPS, etc,
as in 7285.

But new work & extensions would use the new presentation scheme.


The new format resources can co-exist in the IRD with the rfc7285
resources. Ideally, an ALTO server would provide cost map resources in
both old & new formats, via different resource entries in the IRD.

I see it as replacing rfc7285 in the same way the ipv6 "replaces" ipv4. :-)

	- Wendy Roome

On 07/27/2016, 09:44, "Vijay K. Gurbani"
<vijay.gurbani@nokia-bell-labs.com> wrote:

>[As individual]
>
>On 07/26/2016 12:38 PM, Wendy Roome wrote:
>>So are people interested in pursuing this approach? The good news is that
>>will unify everything. The bad news is it will replace everything in rfc
>>7285.
>
>Wendy: "Replace" how?  By making rfc7285 obsolete?  If the approach
>outlined will not be backwardly compatible to rfc7285 then I think we
>should tread with caution.  I don't think it will be in our interest to
>obsolete rfc7285 at a time when there appears to be arising interest in
>it.
>
>Cheers,
>
>- vijay
>--
>Vijay K. Gurbani, Bell Laboratories, Nokia Networks