RFC 6029: A Survey on Research on the Application-Layer Traffic Optimization (ALTO) Problem
In plain English — editorial summary, not part of the RFC
A significant part of the Internet traffic today is generated by peer-to-peer (P2P) applications used originally for file sharing, and more recently for real-time communications and live media streaming. Such applications discover a route to each other through an overlay network with little knowledge of the underlying network topology. As a result, they may choose peers based on information deduced from empirical measurements, which can lead to suboptimal choices. This document, a product of the P2P Research Group, presents a survey of existing literature on discovering and using network topology information for Application-Layer Traffic Optimization. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6029
- Published
- October 2010
- Authors
- I. Rimac; V. Hilt; M. Tomsu; V. Gurbani; E. Marocco
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6875The P2P Network Experiment Council's Activities and Experiments with Application-Layer Traffic Optimization (ALTO) in JapanCurrent
February 2013
- RFC 5693Application-Layer Traffic Optimization (ALTO) Problem StatementCurrent
October 2009
- 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 8076A Usage for Shared Resources in RELOAD (ShaRe)Current
March 2017
- RFC 2353APPN/HPR in IP Networks APPN Implementers' Workshop Closed Pages DocumentCurrent
May 1998
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?