Application-Layer Traffic Optimization (ALTO) Anycast Address
draft-kiesel-alto-ip-based-srv-disc-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sebastian Kiesel , Reinaldo Penno | ||
| Last updated | 2015-01-02 (Latest revision 2014-07-01) | ||
| 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 that have to select one or several hosts from a set of candidates capable of providing a desired resource. ALTO is realized by a client-server protocol. This document establishes a well-known IP address for the ALTO service and specifies how ALTO clients embedded in the resource consumer can use it to access the ALTO service. Terminology and Requirements Language This document makes use of the ALTO terminology defined in RFC 5693 [RFC5693].
Authors
Sebastian Kiesel
Reinaldo Penno
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)