ALTO Cost Calendar
draft-ietf-alto-cost-calendar-03

The information below is for an old version of the document
Document Type Expired Internet-Draft (alto WG)
Last updated 2018-06-11 (latest revision 2017-12-08)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Reviews
Stream WG state WG Consensus: Waiting for Write-Up
Doc Shepherd Follow-up Underway
Document shepherd Vijay Gurbani
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Vijay Gurbani <vijay.gurbani@nokia.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-alto-cost-calendar-03.txt

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 cost maps enabling an ALTO Server to provide "Cost Calendars". These capabilities are applicable to ALTO metrics with time-varying values. 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.

Authors

Sabine Randriamasy (sabine.randriamasy@nokia-bell-labs.com)
Yang Yang (yry@cs.yale.edu)
Qin Wu (sunseawq@huawei.com)
Deng Lingli (denglingli@chinamobile.com)
Nico Schwan (nico.schwan@thalesgroup.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)