Application-Layer Traffic Optimization (ALTO) Deployment Considerations
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 77
- Abstract
- 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.
- Publication Date
- 2016-10-01
- Status Note
- Informational
- DOI
10.17487/RFC7971- Link
- https://doi.org/10.17487/RFC7971
- Author(s)
- Martin StiemerlingSebastian KieselMichael ScharfHans SeidelStefano Previdi
Latest version of IETF RFC 7971
Document Versions — IETF RFC 7971
-
▶ IETF RFC 7971 (2016-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IANA, "Application-Layer Traffic Optimization (ALTO) Protocol", < http://www.iana.org/assignments/alto-protocol >. EXTERNAL
- IETF RFC 5693 [Active*]
- IETF RFC 6708 [Active*]
- IETF RFC 7285 [Active*]
- IETF RFC 7286 [Active*]
Bibliographic Reference(s)
- IETF.draft-deng-alto-p2pcache-03 — ALTO-P2PCACHE EXTERNAL
- IETF.draft-ietf-alto-incr-update-sse-03 — UPDATE-SSE EXTERNAL
- IETF.draft-ietf-i2rs-yang-network-topo-06 — NETWORK-TOPO EXTERNAL
- IETF.draft-jenkins-alto-cdn-use-cases-03 — CDN-USE EXTERNAL
- IETF.draft-kiesel-alto-h12-02 — ALTO-H12 EXTERNAL
- IETF.draft-kiesel-alto-xdom-disc-02 — XDOM-DISC EXTERNAL
- IETF.draft-lee-alto-chinatelecom-trial-04 — CHINA-TRIAL EXTERNAL
- IETF.draft-penno-alto-cdn-03 — ALTO-CDN EXTERNAL
- IETF.draft-scharf-alto-vpn-service-02 — VPN-SERVICE EXTERNAL
- IETF.draft-seedorf-cdni-request-routing-alto-08 — CDNI-FCI EXTERNAL
- IETF.draft-seidel-alto-map-calculation-00 — MAP-CALC EXTERNAL
- IETF RFC 3411 [Active*]
- IETF RFC 3568 [Active*]
- IETF RFC 4026 [Active*]
- IETF RFC 4655 [Active*]
- IETF RFC 4778 [Active*]
- IETF RFC 5594 [Active*]
- IETF RFC 5632 [Active*]
- IETF RFC 6020 [Active*]
- IETF RFC 6241 [Active*]
- IETF RFC 6875 [Active*]
- IETF RFC 7491 [Active*]
- IETF RFC 7752 [Superseded*]
- IETF RFC 7871 [Active*]
- IETF RFC 7921 [Active*]
- IETF RFC 7922 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7971.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7971, Application-Layer Traffic Optimization (ALTO) Deployment Considerations. Available at https://doi.org/10.17487/RFC7971
Snippet:
IETF RFC 7971, Application-Layer Traffic Optimization (ALTO) Deployment Considerations. Available at https://doi.org/10.17487/RFC7971
HTML (ISO 690 compliant)
Preview:
IETF RFC 7971, Application-Layer Traffic Optimization (ALTO) Deployment Considerations. Available at https://doi.org/10.17487/RFC7971
Snippet:
<span class="citation"><cite>IETF RFC 7971</cite>, Application-Layer Traffic Optimization (ALTO) Deployment Considerations. Available at <a href="https://doi.org/10.17487/RFC7971" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7971</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7971, Application-Layer Traffic Optimization (ALTO) Deployment Considerations
doi: 10.17487/RFC7971
url: https://doi.org/10.17487/RFC7971
doi: 10.17487/RFC7971
url: https://doi.org/10.17487/RFC7971
Snippet:
<li> <cite id="bib-rfc7971">IETF RFC 7971</cite>, Application-Layer Traffic Optimization (ALTO) Deployment Considerations <span class="doi">10.17487/RFC7971</span> </li>
Referenced By
- IETF RFC 9241 [Active*]
- IETF RFC 9439 [Active*]