Subject: [alto] TR: New Version Notification for draft-randriamasy-alto-cost-calendar-03.txt

From: "RANDRIAMASY, SABINE (SABINE)" <[email-masked]>
Date: Fri, 13 Mar 2015 16:51:16 +0000

Hi all,

We have posted a new version of the "ALTO Cost Calendar" extension proposal draft, that aims at broadening
 the decision possibilities of applications to not only decide 'where' to connect to, but also 'when'. 
The updates in this version aim at simplifying the protocol updates needed to support Calendared ALTO Services. 

Our intent is to gauge the dispositions of this draft with respect to being a WG item. 
Please see our summary below. Any feedback and comments on the draft are welcome.

Thanks,
Sabine, Richard, Qin, Lingli and Nico 
-----------------------------------------------
In a nutshell, an ALTO Cost Calendar:

- allows Applications to carefully schedule their connections or data transfers
- allows ALTO Clients to schedule their ALTO Calendar requests themselves and thus save time and resources
- is applicable to time-sensitive ALTO metrics and applications that do not need immediate transfer 

The applicable service information resources are: Endpoint Cost Map (ECM), the Cost Map (CM) and Filtered Cost Map (FCM) if the CM or FCM size is manageable

To support this, the extensions proposed in the ALTO Calendar draft:
- the structure of a Client request for an ALTO Calendar remains unchanged. 
- encodes Calendar costs values as an array of N time dependent values. For instance a diurnal cost value pattern may be encoded in 12 values each applicable to an interval of 2 hours.
- adds fields in the IRD capabilities on the properties of the N time intervals (e.g.: num-intervals = 12, time-interval-size = 2hours)
- conveys these properties in the "meta" of ALTO Server responses, together with calendar attribute values on the start date and repetitiveness of the calendar. E.g. "repeat" : 4 if the current calendar values are valid for 4 days after its start date.

The draft also identifies a number of points subject to discussion, such as the attribute names or the possible extensions to Cost Mode so as to support ALTO Calendars with values in string "Mode". The current examples assume values in the Numerical Mode.

Besides, we may want to restrict conveying the "repeat" attribute in the Server responses only.  
-----------------------------------------------

>>-----Message d'origine-----
>>De : [email-masked] [mailto:[email-masked]]
>>Envoyé : mardi 10 mars 2015 01:19
>>À : Nico Schwan; RANDRIAMASY, SABINE (SABINE); Qin Wu; Wenson Wu;
>>Richard Yang; RANDRIAMASY, SABINE (SABINE); Deng Lingli; Nico Schwan;
>>Yang Yang; Lingli Deng
>>Objet : New Version Notification for draft-randriamasy-alto-cost-
>>calendar-03.txt
>>
>>
>>A new version of I-D, draft-randriamasy-alto-cost-calendar-03.txt
>>has been successfully submitted by Sabine Randriamasy and posted to the
>>IETF repository.
>>
>>Name:		draft-randriamasy-alto-cost-calendar
>>Revision:	03
>>Title:		ALTO Cost Calendar
>>Document date:	2015-03-09
>>Group:		Individual Submission
>>Pages:		32
>>URL:            http://www.ietf.org/internet-drafts/draft-randriamasy-
>>alto-cost-calendar-03.txt
>>Status:         https://datatracker.ietf.org/doc/draft-randriamasy-
>>alto-cost-calendar/
>>Htmlized:       http://tools.ietf.org/html/draft-randriamasy-alto-cost-
>>calendar-03
>>Diff:           http://www.ietf.org/rfcdiff?url2=draft-randriamasy-
>>alto-cost-calendar-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
>>   informed decisions.  The present draft proposes to extend the cost
>>   information provided by the ALTO protocol.  The purpose is to
>>broaden
>>   the decision possibilities of applications to not only decide
>>'where'
>>   to connect to, but also 'when'.  This is useful to applications that
>>   have a degree of freedom on when to schedule data transfers, such as
>>   non- instantaneous data replication between data centers or service
>>   provisioning to end systems with irregular connectivity.  ALTO
>>   guidance to schedule application traffic can also efficiently help
>>   for load balancing and resources efficiency.
>>
>>   The draft proposes a new cost Mode called "Calendar" Mode, that is
>>   applicable to time-sensitive ALTO metrics and allows Applications to
>>   carefully schedule their connections or data transfers.  In the
>>   Calendar Mode, 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.  Besides the functional time-shift enhancement the ALTO Cost
>>   Calendar also allows to schedule the ALTO requests themselves and
>>   thus save a number of ALTO transactions.
>>
>>
>>
>>
>>
>>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