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

From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <[email-masked]>
Date: Tue, 4 Jul 2017 13:42:31 +0000

Hi all,

An update of draft "ALTO Contextual Cost Values" (see nutshell below) has just been submitted. Great thanks for the feedback on the previous version. The updates in v2:  
- address WG comments, in particular concerns on (near) real-time changes in wireless networks, by clarifying the meaning of the example cellular connection cost and naming it "ARFcost" for Abstracted RFcost,
- add definitions and rules on context attributes and backwards compatibility and update the example IRD, 
- update the example FCM request 

The current design :
(1) - keeps the Cost Type definition as specified in RFC 7285, 
(2) - indicates context attributes in information resources,
(3) - encodes the attributes in JSON Strings with constant values, 

(1) ensures backwards compatibility,
(3) wants to moderate the number of context parameters and avoid too many indirections for the Server, since context parameters are qualitative and expected to have few values. 

Further WG feedback and proposals are more than welcome,
Thanks, 
Sabine
 
---------------------
ALTO Contextual Cost Value in a nutshell: 
This draft proposes to extend the cost information specified in [RFC7285] by providing, for a same cost metric, several values where each one depends on qualitative criteria as opposed to quantitative criteria such as time. To this end, ALTO queries and responses associate so-called "context attributes" to cost metrics. 
This allows to require for example:
- "routingcost", in the context of SLA-3 AND "cellular" or "wifi" access type,
- or calendar of "cellular connection costs" in the context of "uplink" and "downlink" directions AND depending on whether "unattended data is allowed" or "unattended data is not allowed".
---------------------

>>-----Original Message-----
>>From: [email-masked] [mailto:[email-masked]]
>>Sent: 04 July 2017 01:54
>>To: Randriamasy, Sabine (Nokia - FR/Nozay) <sabine.randriamasy@nokia-
>>bell-labs.com>
>>Subject: New Version Notification for draft-randriamasy-alto-cost-context-
>>02.txt
>>
>>
>>A new version of I-D, draft-randriamasy-alto-cost-context-02.txt
>>has been successfully submitted by Sabine Randriamasy and posted to the
>>IETF repository.
>>
>>Name:		draft-randriamasy-alto-cost-context
>>Revision:	02
>>Title:		ALTO Contextual Cost Values
>>Document date:	2017-07-03
>>Group:		Individual Submission
>>Pages:		18
>>URL:            https://www.ietf.org/internet-drafts/draft-randriamasy-alto-cost-
>>context-02.txt
>>Status:         https://datatracker.ietf.org/doc/draft-randriamasy-alto-cost-
>>context/
>>Htmlized:       https://tools.ietf.org/html/draft-randriamasy-alto-cost-
>>context-02
>>Htmlized:       https://datatracker.ietf.org/doc/html/draft-randriamasy-alto-
>>cost-context-02
>>Diff:           https://www.ietf.org/rfcdiff?url2=draft-randriamasy-alto-cost-
>>context-02
>>
>>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