[alto] FW: New Version Notification for draft-randriamasy-alto-cost-context-00.txt

"Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia-bell-labs.com> Tue, 15 November 2016 13:27 UTC

Return-Path: <sabine.randriamasy@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 0F6E4129600 for <alto@ietfa.amsl.com>; Tue, 15 Nov 2016 05:27:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.402
X-Spam-Level:
X-Spam-Status: No, score=-6.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, 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 K7Wl91ArbkNO for <alto@ietfa.amsl.com>; Tue, 15 Nov 2016 05:27:07 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 03D34129540 for <alto@ietf.org>; Tue, 15 Nov 2016 05:27:06 -0800 (PST)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id 04A7CD69F3C5A for <alto@ietf.org>; Tue, 15 Nov 2016 13:27:01 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id uAFDR2LY030229 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Tue, 15 Nov 2016 13:27:03 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id uAFDR2G2018167 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <alto@ietf.org>; Tue, 15 Nov 2016 14:27:02 +0100
Received: from FR711WXCHMBA01.zeu.alcatel-lucent.com ([169.254.1.13]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0301.000; Tue, 15 Nov 2016 14:27:02 +0100
From: "Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia-bell-labs.com>
To: IETF ALTO <alto@ietf.org>
Thread-Topic: New Version Notification for draft-randriamasy-alto-cost-context-00.txt
Thread-Index: AQHSPyo0ZFtXZdkW+0i0m01lyg+xXaDaCPCA
Date: Tue, 15 Nov 2016 13:27:02 +0000
Message-ID: <A7A5844EB93EB94AB22C2068B10AD65A017F93467E@FR711WXCHMBA01.zeu.alcatel-lucent.com>
References: <147920533199.10316.15266716749977839040.idtracker@ietfa.amsl.com>
In-Reply-To: <147920533199.10316.15266716749977839040.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/ga9OUzf_L3Vioa8N-Rq5j_ODWZU>
Subject: [alto] FW: New Version Notification for draft-randriamasy-alto-cost-context-00.txt
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: Tue, 15 Nov 2016 13:27:09 -0000

Hello,

A new draft entitled " ALTO Contextual Cost Values " has been posted and proposes an extension expose ALTO cost values depending on qualitative parameters such as "uplink", "wifi", "sla-xx", "uda" etc..

The 2 presented use cases apply to cellular LTE networks and may be extended to others. 

Section 3 lists a number of ALTO extensions needed to support these use cases. List discussions have started for many of them. In particular:
- cellular networks and mobility models,
- multiple ({src}, {dst}) pairs in query input,
- abstracted network element properties,
- extended topologies and costs

So your feedback on this draft and further discussions on extensions are more than welcome.

Thanks,
Sabine

>>-----Original Message-----
>>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>Sent: mardi 15 novembre 2016 11:22
>>To: Randriamasy, Sabine (Nokia - FR) <sabine.randriamasy@nokia-bell-
>>labs.com>
>>Subject: New Version Notification for draft-randriamasy-alto-cost-context-
>>00.txt
>>
>>
>>A new version of I-D, draft-randriamasy-alto-cost-context-00.txt
>>has been successfully submitted by Sabine Randriamasy and posted to the
>>IETF repository.
>>
>>Name:		draft-randriamasy-alto-cost-context
>>Revision:	00
>>Title:		ALTO Contextual Cost Values
>>Document date:	2016-11-15
>>Group:		Individual Submission
>>Pages:		19
>>URL:            https://www.ietf.org/internet-drafts/draft-randriamasy-alto-cost-
>>context-00.txt
>>Status:         https://datatracker.ietf.org/doc/draft-randriamasy-alto-cost-
>>context/
>>Htmlized:       https://tools.ietf.org/html/draft-randriamasy-alto-cost-
>>context-00
>>
>>
>>Abstract:
>>   The Application-Layer Traffic Optimization (ALTO) Service has defined
>>   network and cost maps to provide basic network information, where the
>>   cost maps allow only one JSON value for a requested metric.
>>
>>   This document introduces several protocol extensions to allow ALTO
>>   clients to support use cases such as context based connection
>>   selection in cellular networks and calendaring for unattended data.
>>   This document refers to other extension proposals posted in the ALTO
>>   WG that can support the present use cases as well.  Likewise, some of
>>   the proposed extensions may serve other ALTO use cases.
>>
>>
>>
>>
>>
>>Please note that it may take a couple of minutes from the time of submission
>>until the htmlized version and diff are available at tools.ietf.org.
>>
>>The IETF Secretariat