ALTO Deployment Considerations
draft-stiemerling-alto-deployments-06

Document Type Expired Internet-Draft (individual)
Last updated 2011-01-25
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
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-stiemerling-alto-deployments-06.txt

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 these applications, which have to select one or several hosts from a set of candidates, that are able to provide a desired resource. The protocol is under specification in the ALTO working group. This memo discusses deployment related issues of ALTO for peer-to-peer and CDNs, some preliminary security considerations, and also initial guidance for application designers using ALTO.

Authors

Martin Stiemerling (martin.stiemerling@neclab.eu)
Sebastian Kiesel (ietf-alto@skiesel.de)

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