Application-Layer Traffic Optimization (ALTO) Deployment Considerations

Abstract

Many Internet applications are used to access resources such as pieces of information or server processes that are available in several equivalent replicas on different hosts. This includes, but is not limited to, peer-to-peer file sharing applications. 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. This memo discusses deployment-related issues of ALTO. It addresses different use cases of ALTO such as peer-to-peer file sharing and Content Delivery Networks (CDNs) and presents corresponding examples. The document also includes recommendations for network administrators and application designers planning to deploy ALTO, such as recommendations on how to generate ALTO map information.

A Stochastic Analytical Modeling Framework on ISP–P2P Collaborations in Multidomain Environments

“…5. As discussed above, such interaction can be implemented by the protocol interactions between ALTO elements [37]. Specifically, the P2P tracker can be corresponding to the ALTO client and the CE can be implemented by the ALTO server.…”

Muded

“…Before the ALTO base protocol, the ALTO problem statement (SEEDORF; BURGER, 2009) and requirements (KIESEL et al, 2012) were published in 2009 (RFC5693) and 2012 (RFC6708), respectively. Afterward, several extensions have been standardized, such as deployment considerations (RFC7971) (STIEMERLING et al, 2016), a multi-cost map to retrieve several cost metrics in a single query/response transaction (RFC8189) (RAN-DRIAMASY et al, 2017), and server discovery (RFC7286) (SONG et al, 2014) and cross-domain server discovery (RFC8686) (KIESEL; STIEMERLING, 2020) to identify a topologically nearby ALTO server or ALTO servers outside of a network domain, respectively.…”