RFC 8896: Application-Layer Traffic Optimization (ALTO) Cost Calendar

This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO cost information service so that…

Read RFC 8896 on the RFC Editor

Outgoing relationships (13 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3
Normative reference — RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format
Normative reference — RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Normative reference — RFC 7285: Application-Layer Traffic Optimization (ALTO) Protocol
Normative reference — RFC 8895: Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
Normative reference — RFC 8189: Multi-Cost Application-Layer Traffic Optimization (ALTO)
Informative reference — RFC 2818: HTTP Over TLS
Informative reference — RFC 7159: The JavaScript Object Notation (JSON) Data Interchange Format
Informative reference — RFC 5693: Application-Layer Traffic Optimization (ALTO) Problem Statement
Informative reference — RFC 6708: Application-Layer Traffic Optimization (ALTO) Requirements

Incoming relationships (2 related RFCs)

Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 9240: An Extension for Application-Layer Traffic Optimization (ALTO): Entity Property Maps