Application-Layer Traffic Optimization (ALTO) Problem Statement

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 14
Abstract: 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.
Publication Date: 2009-10-01
Status Note: Informational
DOI: 10.17487/RFC5693
Link: https://doi.org/10.17487/RFC5693
Author(s): Jan Seedorf
Eric Burger
Keyword(s): P2P

Latest version of IETF RFC 5693

Document Versions — IETF RFC 5693

▶ IETF RFC 5693 (2009-10-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

Kiesel, S., Popkin, L., Previdi, S., Woundy, R., and Y. Yang, "Application-Layer Traffic Optimization (ALTO) Requirements", Work in Progress, April 2009. EXTERNAL
Choffnes, D. and F. Bustamante, "Taming the Torrent: A practical approach to reducing cross-ISP traffic in P2P systems", Proceedings of ACM SIGCOMM, August 2008. EXTERNAL
Glasner, J., "P2P Fuels Global Bandwidth Binge", April 2005, < http://www.wired.com >. EXTERNAL
Aggarwal, V., Feldmann, A., and C. Scheideler, "Can ISPs and P2P systems co-operate for improved performance?", ACM SIGCOMM Computer Communications Review (CCR), 37:3, pp. 29-40. EXTERNAL
Karagiannis, T., Rodriguez, P., and K. Papagiannaki, "Should ISPs fear Peer-Assisted Content Distribution?", ACM USENIX IMC, Berkeley 2005. EXTERNAL
Akella, A., Seshan, S., and A. Shaikh, "An Empirical Evaluation of WideArea Internet Bottlenecks", Proceedings of ACM SIGCOMM, October 2003. EXTERNAL
Saucez, D. and B. Donnet, "The case for an informed path selection service", Work in Progress, February 2008. EXTERNAL
Xie, H., Krishnamurthy, A., Silberschatz, A., and R. Yang, "P4P: Explicit Communications for Cooperative Control Between P2P and Network Providers", < http://www.dcia.info/documents/P4P_Overview.pdf >. EXTERNAL
IETF RFC 3031 [Active*]
IETF RFC 3260 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5693.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 5693, Application-Layer Traffic Optimization (ALTO) Problem Statement. Available at https://doi.org/10.17487/RFC5693

Snippet:

IETF RFC 5693, Application-Layer Traffic Optimization (ALTO) Problem Statement. Available at https://doi.org/10.17487/RFC5693

HTML (ISO 690 compliant)

Preview:

IETF RFC 5693, Application-Layer Traffic Optimization (ALTO) Problem Statement. Available at https://doi.org/10.17487/RFC5693

Snippet:

<span class="citation"><cite>IETF RFC 5693</cite>, Application-Layer Traffic Optimization (ALTO) Problem Statement. Available at <a href="https://doi.org/10.17487/RFC5693" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5693</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 5693, Application-Layer Traffic Optimization (ALTO) Problem Statement
doi: 10.17487/RFC5693
url: https://doi.org/10.17487/RFC5693

Snippet:

<li>
<cite id="bib-rfc5693">IETF RFC 5693</cite>, Application-Layer Traffic Optimization (ALTO) Problem Statement
<span class="doi">10.17487/RFC5693</span>
</li>

Referenced By

IETF RFC 6707 [Active*]
IETF RFC 7285 [Active*]
IETF RFC 7491 [Active*]
IETF RFC 7752 [Superseded*]
IETF RFC 9522 [Active*]
IETF RFC 9552 [Active*]