Hi all, We have submitted a new version of the "ALTO Cost Calendar" draft, that extends the decision possibilities of applications to not only decide 'where' to connect to, but also 'when'. We would like 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: - provides arrays of cost values for a given metric, where each value corresponds to a time interval - conveys attributes allowing an ALTO Client to properly interpret the values, such as: size and number of intervals, date of the starting point of the calendar, optional information on value array periodicity ALTO Clients can thus schedule both their connections and ALTO Calendar requests The applicable service information resources are: Endpoint Cost Map (ECM), and Filtered Cost Map (FCM) A calendar is announced in the IRD as a capability associated to a cost type name of a FCM or ECM. Calendar attribute values are also conveyed in the "meta" member of ALTO Server responses. The proposed Calendar design: - does not introduce a new mode, - does not introduce new media types, - is applicable to any cost mode ================================================================== >>-----Message d'origine----- >>De : [email protected] [mailto:[email protected]] >>Envoyé : mardi 7 juillet 2015 01:16 >>À : 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-04.txt >> >> >>A new version of I-D, draft-randriamasy-alto-cost-calendar-04.txt >>has been successfully submitted by Sabine Randriamasy and posted to the >>IETF repository. >> >>Name: draft-randriamasy-alto-cost-calendar >>Revision: 04 >>Title: ALTO Cost Calendar >>Document date: 2015-07-06 >>Group: Individual Submission >>Pages: 33 >>URL: https://www.ietf.org/internet-drafts/draft-randriamasy- >>alto-cost-calendar-04.txt >>Status: https://datatracker.ietf.org/doc/draft-randriamasy- >>alto-cost-calendar/ >>Htmlized: https://tools.ietf.org/html/draft-randriamasy-alto- >>cost-calendar-04 >>Diff: https://www.ietf.org/rfcdiff?url2=draft-randriamasy- >>alto-cost-calendar-04 >> >>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 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 also allows to schedule the ALTO requests themselves >> and thus save a number of ALTO transactions. >> >> The 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. >> >> >> >> >> >>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 _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
