RFC 8686: Application-Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8686
- Published
- February 2020
- Authors
- S. Kiesel; M. Stiemerling
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 34
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8683Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise NetworksCurrent
November 2019
- RFC 8671Support for Adj-RIB-Out in the BGP Monitoring Protocol (BMP)Updated
November 2019
- RFC 8704Enhanced Feasible-Path Unicast Reverse Path ForwardingCurrent
February 2020
- RFC 8650Dynamic Subscription to YANG Events and Datastores over RESTCONFCurrent
November 2019
- RFC 8642Policy Behavior for Well-Known BGP CommunitiesCurrent
August 2019
- RFC 8641Subscription to YANG Notifications for Datastore UpdatesCurrent
September 2019
- RFC 8640Dynamic Subscription to YANG Events and Datastores over NETCONFCurrent
September 2019
- RFC 8639Subscription to YANG NotificationsCurrent
September 2019
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?