ALTO and Content Delivery Networks
draft-penno-alto-cdn-03

Document Type Expired Internet-Draft (individual)
Last updated 2011-03-14
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-penno-alto-cdn-03.txt

Abstract

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.

Authors

Reinaldo Penno (rpenno@juniper.net)
Jan Medved (jmedved@juniper.net)
Richard Alimi (ralimi@google.com)
Richard Yang (yry@yale.edu)
Stefano Previdi (sprevidi@cisco.com)

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