RFC 7971: Application-Layer Traffic Optimization (ALTO) Deployment Considerations
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7971
- Published
- October 2016
- Authors
- M. Stiemerling; S. Kiesel; M. Scharf; H. Seidel; S. Previdi
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 77
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7966Security at the Attribute-Value Pair (AVP) Level for Non-neighboring Diameter Nodes: Scenarios and RequirementsCurrent
September 2016
- RFC 7952Defining and Using Metadata with YANGCurrent
August 2016
- RFC 7951JSON Encoding of Data Modeled with YANGCurrent
August 2016
- RFC 7950The YANG 1.1 Data Modeling LanguageUpdated
August 2016
- RFC 7948Internet Exchange BGP Route Server OperationsCurrent
September 2016
- RFC 7944Diameter Routing Message PriorityCurrent
August 2016
- RFC 7999BLACKHOLE CommunityCurrent
October 2016
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
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?