File formats:

Also available: XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

S. Randriamasy
R. Yang
Q. Wu
L. Deng
N. Schwan

Stream:

IETF

Source:

alto (ops)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8896

Discuss this RFC: Send questions or comments to the mailing list alto@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8896

Abstract

This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO cost information service so that applications decide not only 'where' to connect but also 'when'. This is useful for applications that need to perform bulk data transfer and would like to schedule these transfers during an off-peak hour, for example. This extension introduces the ALTO Cost Calendar with which 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 Information Resources Directory and ALTO Server responses.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.