RFC 5693: Application-Layer Traffic Optimization (ALTO) Problem Statement
In plain English — editorial summary, not part of the RFC
Distributed applications -- such as file sharing, real-time communication, and live and on-demand media streaming -- prevalent on the Internet use a significant amount of network resources. Such applications often transfer large amounts of data through connections established between nodes distributed across the Internet with little knowledge of the underlying network topology. Some applications are so designed that they choose a random subset of peers from a larger set with which to exchange data. Absent any topology information guiding such choices, or acting on suboptimal or local information obtained from measurements and statistics, these applications often make less than desirable choices. This document discusses issues related to an information-sharing service that enables applications to perform better-than-random peer selection. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5693
- Published
- October 2009
- Authors
- J. Seedorf; E. Burger
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5632Comcast's ISP Experiences in a Proactive Network Provider Participation for P2P (P4P) Technical TrialCurrent
September 2009
- RFC 7904A SIP Usage for REsource LOcation And Discovery (RELOAD)Current
October 2016
- RFC 6392A Survey of In-Network Storage SystemsCurrent
October 2011
- RFC 6646DECoupled Application Data Enroute (DECADE) Problem StatementCurrent
July 2012
- RFC 6817Low Extra Delay Background Transport (LEDBAT)Current
December 2012
- RFC 6940REsource LOcation And Discovery (RELOAD) Base ProtocolCurrent
January 2014
- RFC 6972Problem Statement and Requirements of the Peer-to-Peer Streaming Protocol (PPSP)Current
July 2013
- RFC 7086Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)Current
January 2014
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?