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
needed to discover an ALTO server outside of the 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.
tree) and returns one or more URI(s) of information resources related
to that IP address or prefix.
[1]
Barry Leiba,et al.
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
,
2017,
RFC.
[2]
Scott Rose,et al.
DNS Security Introduction and Requirements
,
2005,
RFC.
[3]
Vince Fuller,et al.
Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan
,
2006,
RFC.
[4]
Stephen E. Deering,et al.
IP Version 6 Addressing Architecture
,
1995,
RFC.
[5]
Jan Seedorf,et al.
Application-Layer Traffic Optimization (ALTO) Problem Statement
,
2009
.
[6]
Leslie Daigle,et al.
Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)
,
2007,
RFC.
[7]
Yakov Rekhter,et al.
Address Allocation for Private Internets
,
1994,
RFC.
[8]
Dan Wing,et al.
Session Traversal Utilities for NAT (STUN)
,
2020,
RFC.
[9]
Eric Rescorla,et al.
HTTP Over TLS
,
2000,
RFC.