Applications using the Internet already have access to some
topology information of Internet Service Provider (ISP) networks. For
example, views to Internet routing tables at Looking Glass servers are
available and can be practically downloaded to many network application
clients. What is missing is knowledge of the underlying network topologies
from the point of view of ISPs. In other words, what an ISP prefers in
terms of traffic optimization -- and a way to distribute it.
The Application-Layer Traffic Optimization (ALTO) services defined in this
document provide network information (e.g., basic network location
structure and preferences of network paths) with the goal of modifying
network resource consumption patterns while maintaining or improving
application performance. The basic information of ALTO is based on
abstract maps of a network. These maps provide a simplified view, yet
enough information about a network for applications to effectively utilize
them. Additional services are built on top of the maps.
This document describes a protocol implementing the ALTO services.
Although the ALTO services would primarily be provided by ISPs, other
entities, such as content service providers, could also provide ALTO
services. Applications that could use the ALTO services are those that
have a choice to which end points to connect. Examples of such
applications are peer-to-peer (P2P) and content delivery networks.
%0 Report
%1 ki-2014-0010
%A (Editor), Richard Alimi
%A (Editor), Reinaldo Penno
%A (Editor), Y. Richard Yang
%A Kiesel, Sebastian
%A Previdi, Stefano
%A Roome, Wendy
%A Shalunov, Stanislav
%A Woundy, Richard
%D 2014
%I RFC Editor
%K
%N 7285
%P 1-91
%R 10.17487/RFC7285
%T Application-Layer Traffic Optimization (ALTO) Protocol
%U https://www.rfc-editor.org/info/rfc7285
%X Applications using the Internet already have access to some
topology information of Internet Service Provider (ISP) networks. For
example, views to Internet routing tables at Looking Glass servers are
available and can be practically downloaded to many network application
clients. What is missing is knowledge of the underlying network topologies
from the point of view of ISPs. In other words, what an ISP prefers in
terms of traffic optimization -- and a way to distribute it.
The Application-Layer Traffic Optimization (ALTO) services defined in this
document provide network information (e.g., basic network location
structure and preferences of network paths) with the goal of modifying
network resource consumption patterns while maintaining or improving
application performance. The basic information of ALTO is based on
abstract maps of a network. These maps provide a simplified view, yet
enough information about a network for applications to effectively utilize
them. Additional services are built on top of the maps.
This document describes a protocol implementing the ALTO services.
Although the ALTO services would primarily be provided by ISPs, other
entities, such as content service providers, could also provide ALTO
services. Applications that could use the ALTO services are those that
have a choice to which end points to connect. Examples of such
applications are peer-to-peer (P2P) and content delivery networks.
%Z Current status: proposed standard.
@techreport{ki-2014-0010,
abstract = {Applications using the Internet already have access to some
topology information of Internet Service Provider (ISP) networks. For
example, views to Internet routing tables at Looking Glass servers are
available and can be practically downloaded to many network application
clients. What is missing is knowledge of the underlying network topologies
from the point of view of ISPs. In other words, what an ISP prefers in
terms of traffic optimization -- and a way to distribute it.
The Application-Layer Traffic Optimization (ALTO) services defined in this
document provide network information (e.g., basic network location
structure and preferences of network paths) with the goal of modifying
network resource consumption patterns while maintaining or improving
application performance. The basic information of ALTO is based on
abstract maps of a network. These maps provide a simplified view, yet
enough information about a network for applications to effectively utilize
them. Additional services are built on top of the maps.
This document describes a protocol implementing the ALTO services.
Although the ALTO services would primarily be provided by ISPs, other
entities, such as content service providers, could also provide ALTO
services. Applications that could use the ALTO services are those that
have a choice to which end points to connect. Examples of such
applications are peer-to-peer (P2P) and content delivery networks.},
added-at = {2016-03-03T17:45:04.000+0100},
annote = {Current status: proposed standard.},
author = {(Editor), Richard Alimi and (Editor), Reinaldo Penno and (Editor), Y. Richard Yang and Kiesel, Sebastian and Previdi, Stefano and Roome, Wendy and Shalunov, Stanislav and Woundy, Richard},
biburl = {https://puma.ub.uni-stuttgart.de/bibtex/2edddb0fd9a4d74e04cc307d1b73312b7/rainerreichel},
doi = {10.17487/RFC7285},
howpublished = {Internet Requests for Comments},
institution = {{RFC Editor}},
interhash = {36088b57f16ee32fad3774ca25dad418},
intrahash = {edddb0fd9a4d74e04cc307d1b73312b7},
issn = {2070-1721},
key = {RFC7285},
keywords = {},
month = sep,
number = 7285,
pages = {1-91},
publisher = {{RFC Editor}},
timestamp = {2016-03-04T09:57:29.000+0100},
title = {{Application-Layer Traffic Optimization (ALTO) Protocol}},
txt = {https://www.rfc-editor.org/rfc/rfc7285.txt},
type = {{RFC}},
url = {https://www.rfc-editor.org/info/rfc7285},
year = 2014
}