Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

S. Kiesel
M. Stiemerling

Stream:

IETF

Source:

alto (ops)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8686

Discuss this RFC: Send questions or comments to the mailing listalto@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8686

Abstract

The goal of Application-Layer Traffic Optimization (ALTO) is toprovide guidance to applications that have to select one or severalhosts from a set of candidates capable of providing a desiredresource. ALTO is realized by a client-server protocol. Before anALTO client can ask for guidance, it needs to discover one or moreALTO servers that can provide suitable guidance.

In some deployment scenarios, in particular if the information aboutthe network topology is partitioned and distributed over several ALTOservers, it may be necessary to discover an ALTO server outside ofthe ALTO client's own network domain, in order to get appropriateguidance. This document details applicable scenarios, itemizesrequirements, and specifies a procedure for ALTO cross-domain serverdiscovery.

Technically, the procedure specified in this document takes oneIP address or prefix and a U-NAPTR Service Parameter (typically,"ALTO:https") as parameters. It performs DNS lookups (for NAPTRresource records in the "in-addr.arpa." or "ip6.arpa." trees) andreturns one or more URIs of information resources related to that IPaddress or prefix.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.