Using ALTO for ALTO server selection
draft-kiesel-alto-alto4alto-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Sebastian Kiesel | ||
| Last updated | 2010-07-05 | ||
| 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) | ||
https://www.ietf.org/archive/id/draft-kiesel-alto-alto4alto-00.txt
Abstract
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. Entities seeking guidance need to discover and possibly select an ALTO server to ask. This document proposes an ALTO-based scheme to select an ALTO server that can give guidance to a given ALTO client. Unlike some other proposed ALTO discovery mechanisms, this solution works well if the client seeks guidance from a set of ALTO servers that are operated by an entity which is not the operator of the access network.
Authors
Sebastian Kiesel (ietf-alto@skiesel.de)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)