ALTO Server Discovery Protocol
draft-kiesel-alto-3pdisc-05
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sebastian Kiesel , Martin Stiemerling , Nico Schwan , Michael Scharf , Marco Tomsu , Song Yongchao | ||
| Last updated | 2011-03-14 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
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 is called ALTO server discovery. This memo describes an ALTO server discovery mechanism based on several alternative mechanisms that are applicable in a diverse set of ALTO deployments.
Authors
Sebastian Kiesel
Martin Stiemerling
Nico Schwan
Michael Scharf
Marco Tomsu
Song Yongchao
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)