[alto] FW: I-D Action: draft-ietf-alto-cost-calendar-02.txt

["Randriamasy, Sabine (Nokia - FR/Nozay)" <[e-mail]>]

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. In this version:

- the CalendarAttributes design was updated to be self-contained and support Multi-Cost,
- the calendar request specification text has additional rules to ensure consistency with the number of requested metrics and backwards compatibility,  
- the CalendarResponseAttributes: have similar new rules,
- other request and responses formats were updated to support multi-cost

- section 4.3 "Recap of rules related to ALTO Cost Calendars" has been dropped and most of its text transferred in 2.2.2 Compatibility with legacy ALTO Clients
- section 5 "Use cases for ALTO Cost Schedule" has been dropped as other sections already include use cases and examples.

Your feedback on the design is more than welcome before additional text harmonization between Filtered Cost Map and Endpoint Cost Map Service.

Thanks,
Sabine
  

>>-----Original Message-----
>>From: alto [mailto:[e-mail]] On Behalf Of internet-
>>[e-mail]
>>Sent: 03 July 2017 23:48
>>To: [e-mail]
>>Cc: [e-mail]
>>Subject: [alto] I-D Action: draft-ietf-alto-cost-calendar-02.txt
>>
>>
>>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>This draft is a work item of the Application-Layer Traffic Optimization of the
>>IETF.
>>
>>        Title           : ALTO Cost Calendar
>>        Authors         : Sabine Randriamasy
>>                          Richard Yang
>>                          Qin Wu
>>                          Lingli Deng
>>                          Nico Schwan
>>	Filename        : draft-ietf-alto-cost-calendar-02.txt
>>	Pages           : 25
>>	Date            : 2017-07-03
>>
>>Abstract:
>>   The goal of Application-Layer Traffic Optimization (ALTO) is to
>>   bridge the gap between network and applications by provisioning
>>   network related information in order to allow applications to make
>>   network informed decisions.  The present draft extends the ALTO cost
>>   information so as to broaden the decision possibilities of
>>   applications to not only decide 'where' to connect to, but also
>>   'when'.  This is useful to applications that need to schedule their
>>   data transfers and connections and have a degree of freedom to do so.
>>   ALTO guidance to schedule application traffic can also efficiently
>>   help for load balancing and resources efficiency.  Besides, the ALTO
>>   Cost Calendar allows to schedule the ALTO requests themselves and
>>   thus to save a number of ALTO transactions.
>>
>>   This draft proposes new capabilities and attributes on filtered cost
>>   maps and endpoint costs enabling an ALTO Server to provide "Cost
>>   Calendars".  These capabilities are applicable to time-sensitive ALTO
>>   metrics.  With ALTO Cost Calendars, an ALTO Server exposes ALTO Cost
>>   Values in JSON arrays where each value corresponds to a given time
>>   interval.  The time intervals as well as other Calendar attributes
>>   are specified in the IRD and ALTO Server responses.
>>
>>
>>
>>The IETF datatracker status page for this draft is:
>>https://datatracker.ietf.org/doc/draft-ietf-alto-cost-calendar/
>>
>>There are also htmlized versions available at:
>>https://tools.ietf.org/html/draft-ietf-alto-cost-calendar-02
>>https://datatracker.ietf.org/doc/html/draft-ietf-alto-cost-calendar-02
>>
>>A diff from the previous version is available at:
>>https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cost-calendar-02
>>
>>
>>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.
>>
>>Internet-Drafts are also available by anonymous FTP at:
>>ftp://ftp.ietf.org/internet-drafts/
>>
>>_______________________________________________
>>alto mailing list
>>[e-mail]
>>https://www.ietf.org/mailman/listinfo/alto