RFC 6708: Application-Layer Traffic Optimization (ALTO) Requirements
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 guidance shall be based on parameters that affect performance and efficiency of the data transmission between the hosts, e.g., the topological distance. The ultimate goal is to improve performance or Quality of Experience in the application while reducing the utilization of the underlying network infrastructure. This document enumerates requirements for specifying, assessing, or comparing protocols and implementations. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6708
- Published
- September 2012
- Authors
- S. Kiesel; S. Previdi; M. Stiemerling; R. Woundy; Y. Yang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6703Reporting IP Network Performance Metrics: Different Points of ViewCurrent
August 2012
- RFC 6727Definitions of Managed Objects for Packet SamplingCurrent
October 2012
- RFC 6728Configuration Data Model for the IP Flow Information Export (IPFIX) and Packet Sampling (PSAMP) ProtocolsCurrent
October 2012
- RFC 6733Diameter Base ProtocolUpdated
October 2012
- RFC 6734Diameter Attribute-Value Pairs for Cryptographic Key TransportCurrent
October 2012
- RFC 6735Diameter Priority Attribute-Value PairsCurrent
October 2012
- RFC 6736Diameter Network Address and Port Translation Control ApplicationCurrent
October 2012
- RFC 6737The Diameter Capabilities Update ApplicationCurrent
October 2012
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?