Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 9274

Authors:

R. Alimi, Ed.
R. Penno, Ed.
Y. Yang, Ed.
S. Kiesel
S. Previdi
W. Roome
S. Shalunov
R. Woundy

Stream:

IETF

Source:

alto (ops)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

Applications using the Internet already have access to some topologyinformation of Internet Service Provider (ISP) networks. Forexample, views to Internet routing tables at Looking Glass serversare available and can be practically downloaded to many networkapplication clients. What is missing is knowledge of the underlyingnetwork topologies from the point of view of ISPs. In other words,what an ISP prefers in terms of traffic optimization -- and a way todistribute it.

The Application-Layer Traffic Optimization (ALTO) services defined inthis document provide network information (e.g., basic networklocation structure and preferences of network paths) with the goal ofmodifying network resource consumption patterns while maintaining orimproving application performance. The basic information of ALTO isbased on abstract maps of a network. These maps provide a simplifiedview, yet enough information about a network for applications toeffectively utilize them. Additional services are built on top ofthe maps.

This document describes a protocol implementing the ALTO services.Although the ALTO services would primarily be provided by ISPs, otherentities, such as content service providers, could also provide ALTOservices. Applications that could use the ALTO services are thosethat have a choice to which end points to connect. Examples of suchapplications are peer-to-peer (P2P) and content delivery networks.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.