Application-Layer Traffic Optimization (ALTO) Requirements
draft-kiesel-alto-reqs-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Sebastian Kiesel , Laird Popkin , Stefano Previdi , Richard Woundy , Y. Richard Yang | ||
Last updated | 2009-05-01 (Latest revision 2009-03-09) | ||
Replaced by | draft-ietf-alto-reqs | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-alto-reqs | |
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:
Abstract
Many Internet applications are used to access resources, such as pieces of information or server processes, which are available in several equivalent replicas on different hosts. This includes, but is not limited to, peer-to-peer file sharing applications. The goal of Application-Layer Traffic Optimization (ALTO) is to provide guidance to applications, which have to select one or several hosts from a set of candidates, that are able to provide a desired resource. This guidance shall be based on parameters that affect performance and efficiency of the data transmission between the hosts, e.g., the topological distance. The ultimate goal is to improve performance (or Quality of Experience) in the application while reducing resource consumption in the underlying network infrastructure. This document enumerates requirements for ALTO, which should be considered when specifying, assessing, or comparing protocols and implementations, and it solicits feedback and discussion.
Authors
Sebastian Kiesel
Laird Popkin
Stefano Previdi
Richard Woundy
Y. Richard Yang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)