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

Wendy Roome <wendy.roome@nokia-bell-labs.com> Thu, 28 July 2016 12:49 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 689EE12DFC7 for <alto@ietfa.amsl.com>; Thu, 28 Jul 2016 05:49:57 -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 mcGcLLTZd-80 for <alto@ietfa.amsl.com>; Thu, 28 Jul 2016 05:49:55 -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 CB2AC12D548 for <alto@ietf.org>; Thu, 28 Jul 2016 05:49:55 -0700 (PDT)
Received: from us70uumx3.dmz.alcatel-lucent.com (unknown [135.245.18.15]) by Websense Email Security Gateway with ESMTPS id F2CFC41BE2965 for <alto@ietf.org>; Thu, 28 Jul 2016 12:49:52 +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 u6SCnscq022988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Thu, 28 Jul 2016 12:49:54 GMT
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id u6SCnrJg024775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2016 12:49:53 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 u6SCnoZb010606; Thu, 28 Jul 2016 07:49:52 -0500 (CDT)
User-Agent: Microsoft-MacOutlook/14.6.6.160626
Date: Thu, 28 Jul 2016 08:49:55 -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: <D3BF75ED.812174%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> <D3BE359A.811156%w.roome@alcatel-lucent.com> <bef531fc-e765-58eb-7fd1-b5a7a8d405a0@nokia-bell-labs.com>
In-Reply-To: <bef531fc-e765-58eb-7fd1-b5a7a8d405a0@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/4Tq4po63iw_3LPveFoDyyru_DCY>
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: Thu, 28 Jul 2016 12:49:57 -0000

Vijay,

Yes, I realized that "here be dragons." :-)

So how about recasting this discussion as format for *new* ALTO services,
like FCS & topology, but leave the existing cost & network maps as they
are?

Of course, if this new approach becomes popular, we might just happen to
notice that it would simplify the existing cost and net maps as well.

	- Wendy Roome

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

>[As an individual, of course]
>
>On 07/27/2016 09:10 AM, Wendy Roome wrote:
>> 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.
>
>Deprecating rfc7285 is not a viable option at this point, at least in my
>opinion.  I think this will add a level of uncertainty to pending work
>that may be detrimental and slow down the progress that we witnessed at
>the Berlin IETF.
>
>I am not being obtuse, of course, just pragmatic.
>
>> 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.
>
>Ultimately whether to go this route is something that the WG will have
>to decide collectively, but my personal opinion is that "here there be
>dragons" :-)
>
>Cheers,
>
>- vijay
>-- 
>Vijay K. Gurbani, Bell Laboratories, Nokia Networks
>1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>Email: vkg@bell-labs.com / vijay.gurbani@nokia-bell-labs.com
>Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq