Extending the Application-Layer Traffic Optimization (ALTO) Protocol
draft-marocco-alto-next-00

Document Type Expired Internet-Draft (individual)
Authors Enrico Marocco  , Vijay Gurbani 
Last updated 2012-07-30 (latest revision 2012-01-20)
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-marocco-alto-next-00.txt

Abstract

The Application-Layer Traffic Optimization (ALTO) protocol is designed to allow entities with knowledge about the network infrastructure to export such information to applications that need to choose one or more endpoints to connect to among large sets of logically equivalent ones. The primary use case for the ALTO protocol was peer-to-peer applications for file sharing, video streaming and realtime communications, usually running on end-user devices. However, a number of other applications executing in more controlled environments may also benefit from the information that can be exported through the ALTO protocol. The use cases that have received significant attention include Content Delivery Networks (CDNs), distributed applications running in large datacenters, as well as systems made of inter-communicating ALTO servers. To apply ALTO to these new use cases, this document aims to foster a discussion to determine if, and how, the ALTO protocol could be extended to provide a simple yet useful view of a computational environment that goes beyond the static (or near static) network topology and cost map information.

Authors

Enrico Marocco (enrico.marocco@telecomitalia.it)
Vijay Gurbani (vkg@bell-labs.com)

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