Skip to main content

ALTO and Content Delivery Networks

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Reinaldo Penno , Jan Medved , Richard Alimi , Richard Yang , Stefano Previdi
Last updated 2011-03-14
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Networking applications can request through the ALTO protocol information about the underlying network topology from the ISP or Content Provider (henceforth referred as Provider) point of view. In other words, information about what a Provider prefers in terms of traffic optimization -- and a way to distribute it. The ALTO Service provides information such as preferences of network resources with the goal of modifying network resource consumption patterns while maintaining or improving application performance. One of the main use cases of the ALTO Service is its integration with Content Delivery Networks (CDN). The purpose of this draft is twofold: first, to describe how ALTO can be used in existing and new CDNs, both within an ISP and in separate organizational entities from the ISP; second, to collect requirements for ALTO usage in CDNs and to provide recommendations into the development of the ALTO protocol for better support of CDNs.


Reinaldo Penno
Jan Medved
Richard Alimi
Richard Yang
Stefano Previdi

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)