Application-Layer Traffic Optimization (ALTO) Protocol
RFC 7285
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['ALTO Information Resources', 'Network Map', 'PID', 'Filtered Network Map', 'Cost Map', 'Endpoint Property Service', 'Endpoint Cost Service']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "R. Woundy": changed name from "Richard Woundy" to "R. Woundy", cleared country (was "USA"), changed order from "-1" to "8" |
|
2026-05-20
|
(System) | Changed author "S. Shalunov": changed name from "Stanislav Shalunov" to "S. Shalunov", cleared country (was "USA"), changed order from "-1" to "7" |
|
2026-05-20
|
(System) | Changed author "W. Roome": changed name from "Wendy Roome" to "W. Roome", cleared country (was "USA"), changed order from "-1" to "6" |
|
2026-05-20
|
(System) | Changed author "S. Previdi": changed name from "Stefano Previdi" to "S. Previdi", changed affiliation from "Cisco Systems" to "Cisco Systems, Inc.", cleared country (was "Italy"), … Changed author "S. Previdi": changed name from "Stefano Previdi" to "S. Previdi", changed affiliation from "Cisco Systems" to "Cisco Systems, Inc.", cleared country (was "Italy"), changed order from "-1" to "5" |
|
2026-05-20
|
(System) | Changed author "S. Kiesel": changed name from "Sebastian Kiesel" to "S. Kiesel", cleared country (was "Germany"), changed order from "-1" to "4" |
|
2026-05-20
|
(System) | Changed author "Y. Yang": changed name from "Y. Richard Yang" to "Y. Yang", changed is_editor from "False" to "True", cleared country (was "USA"), changed order … Changed author "Y. Yang": changed name from "Y. Richard Yang" to "Y. Yang", changed is_editor from "False" to "True", cleared country (was "USA"), changed order from "2" to "3" |
|
2026-05-20
|
(System) | Changed author "R. Penno": changed name from "Reinaldo Penno" to "R. Penno", changed is_editor from "False" to "True", changed affiliation from "Cisco Systems" to "Cisco … Changed author "R. Penno": changed name from "Reinaldo Penno" to "R. Penno", changed is_editor from "False" to "True", changed affiliation from "Cisco Systems" to "Cisco Systems, Inc.", cleared country (was "USA"), changed order from "1" to "2" |
|
2026-05-20
|
(System) | Changed author "R. Alimi": changed name from "Richard Alimi" to "R. Alimi", changed is_editor from "False" to "True", cleared country (was "USA"), changed order from … Changed author "R. Alimi": changed name from "Richard Alimi" to "R. Alimi", changed is_editor from "False" to "True", cleared country (was "USA"), changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2022-01-28
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2021-11-09
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'Applications using the Internet already have access to some topology information of Internet Service Provider (ISP) … Received changes through RFC Editor sync (changed abstract to 'Applications using the Internet already have access to some topology information of Internet Service Provider (ISP) networks. For example, views to Internet routing tables at Looking Glass servers are available and can be practically downloaded to many network application clients. What is missing is knowledge of the underlying network topologies from the point of view of ISPs. In other words, what an ISP prefers in terms of traffic optimization -- and a way to distribute it. The Application-Layer Traffic Optimization (ALTO) services defined in this document provide network information (e.g., basic network location structure and preferences of network paths) with the goal of modifying network resource consumption patterns while maintaining or improving application performance. The basic information of ALTO is based on abstract maps of a network. These maps provide a simplified view, yet enough information about a network for applications to effectively utilize them. Additional services are built on top of the maps. This document describes a protocol implementing the ALTO services. Although the ALTO services would primarily be provided by ISPs, other entities, such as content service providers, could also provide ALTO services. Applications that could use the ALTO services are those that have a choice to which end points to connect. Examples of such applications are peer-to-peer (P2P) and content delivery networks.') |
|
2017-05-16
|
(System) | Changed document authors from "Richard Alimi, Yang Yang, Reinaldo Penno" to "Richard Alimi, Yang Yang, Reinaldo Penno, Sebastian Kiesel, Wendy Roome, Richard Woundy, Stefano Previdi, … Changed document authors from "Richard Alimi, Yang Yang, Reinaldo Penno" to "Richard Alimi, Yang Yang, Reinaldo Penno, Sebastian Kiesel, Wendy Roome, Richard Woundy, Stefano Previdi, Stanislav Shalunov" |
|
2015-10-14
|
(System) | Notify list changed from alto-chairs@ietf.org, draft-ietf-alto-protocol@ietf.org to (None) |
|
2014-09-08
|
(System) | IANA registries were updated to include RFC7285 |
|
2014-09-05
|
(System) | RFC published |