Skip to main content

Application-Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery
RFC 8686

Revision differences

Document history

Date By Action
2020-03-09
(System)
Received changes through RFC Editor sync (changed title to 'Application-Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery', changed abstract to 'The goal of Application-Layer Traffic Optimization …
Received changes through RFC Editor sync (changed title to 'Application-Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery', changed abstract to '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. Before an ALTO client can ask for guidance, it needs to discover one or more ALTO servers that can provide suitable guidance.

In some deployment scenarios, in particular if the information about the network topology is partitioned and distributed over several ALTO servers, it may be necessary to discover an ALTO server outside of the ALTO client's own network domain, in order to get appropriate guidance. This document details applicable scenarios, itemizes requirements, and specifies a procedure for ALTO cross-domain server discovery.

Technically, the procedure specified in this document takes one IP address or prefix and a U-NAPTR Service Parameter (typically, "ALTO:https") as parameters. It performs DNS lookups (for NAPTR resource records in the "in-addr.arpa." or "ip6.arpa." trees) and returns one or more URIs of information resources related to that IP address or prefix.', changed pages to 34, changed standardization level to Proposed Standard, changed state to RFC, changed IESG state to RFC Published)
2020-02-11
(System)
Received changes through RFC Editor sync (changed abstract to 'The goal of Application-Layer Traffic Optimization (ALTO) is to provide guidance to applications that have to …
Received changes through RFC Editor sync (changed abstract to '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. Before an ALTO client can ask for guidance, it needs to discover one or more ALTO servers that can provide suitable guidance.

In some deployment scenarios, in particular if the information about the network topology is partitioned and distributed over several ALTO servers, it may be necessary to discover an ALTO server outside of the ALTO client's own network domain, in order to get appropriate guidance. This document details applicable scenarios, itemizes requirements, and specifies a procedure for ALTO cross-domain server discovery.

Technically, the procedure specified in this document takes one IP address or prefix and a U-NAPTR Service Parameter (typically, "ALTO:https") as parameters. It performs DNS lookups (for NAPTR resource records in the "in-addr.arpa." or "ip6.arpa." trees) and returns one or more URIs of information resources related to that IP address or prefix.')
2020-02-11
(System) Received changes through RFC Editor sync (changed title to 'Application-Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery')
2020-02-06
(System)
Received changes through RFC Editor sync (created alias RFC 8686, changed title to 'Application-Layer Traffic Optimization (ALTO) Cross‑Domain Server Discovery', changed abstract to 'The …
Received changes through RFC Editor sync (created alias RFC 8686, changed title to 'Application-Layer Traffic Optimization (ALTO) Cross‑Domain Server Discovery', changed abstract to '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. Before an ALTO client can ask for guidance, it needs to discover one or more ALTO servers that can provide suitable guidance.

In some deployment scenarios, in particular if the information about the network topology is partitioned and distributed over several ALTO servers, it may be necessary to discover an ALTO server outside of the ALTO client's own network domain, in order to get appropriate guidance. This document details applicable scenarios, itemizes requirements, and specifies a procedure for ALTO cross-domain server discovery.

Technically, the procedure specified in this document takes one IP address or prefix and a U-NAPTR Service Parameter (typically, "ALTO:https") as parameters. It performs DNS lookups (for NAPTR resource records in the "in-addr.arpa." or "ip6.arpa." trees) and returns one or more URIs of information resources related to that IP address or prefix.', changed pages to 34, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-02-06, changed IESG state to RFC Published)
2020-02-06
(System) RFC published