RFC 8896: Application-Layer Traffic Optimization (ALTO) Cost Calendar
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8896
- Published
- November 2020
- Authors
- S. Randriamasy; R. Yang; Q. Wu; L. Deng; N. Schwan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 35
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8895Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)Current
November 2020
- RFC 8897Requirements for Resource Public Key Infrastructure (RPKI) Relying PartiesCurrent
September 2020
- RFC 8893Resource Public Key Infrastructure (RPKI) Origin Validation for BGP ExportCurrent
September 2020
- RFC 8901Multi-Signer DNSSEC ModelsCurrent
September 2020
- RFC 8889Multipoint Alternate-Marking Method for Passive and Hybrid Performance MonitoringObsoleted
August 2020
- RFC 8886Secure Device InstallCurrent
September 2020
- RFC 8906A Common Operational Problem in DNS Servers: Failure to CommunicateCurrent
September 2020
- RFC 8907The Terminal Access Controller Access-Control System Plus (TACACS+) ProtocolUpdated
September 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?