Internet Engineering Task Force (ietf) Application-layer Traffic Optimization (alto) Protocol

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. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

[1]  Fred Baker,et al.  Requirements for IP Version 4 Routers , 1995, RFC.

[2]  Nathaniel S. Borenstein,et al.  Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types , 1996, RFC.

[3]  Scott O. Bradner,et al.  Key words for use in RFCs to Indicate Requirement Levels , 1997, RFC.

[4]  Roy Fielding,et al.  Architectural Styles and the Design of Network-based Software Architectures"; Doctoral dissertation , 2000 .

[5]  Roy T. Fielding,et al.  Uniform Resource Identifier (URI): Generic Syntax , 2005, RFC.

[6]  Vince Fuller,et al.  Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan , 2006, RFC.

[7]  Cullen Jennings Computational Puzzles for SPAM Reduction in SIP , 2007 .

[8]  Vidya Narayanan,et al.  ALTO: A Multi Dimensional Peer Selection Problem , 2008 .

[9]  Abraham Silberschatz,et al.  P4p: provider portal for applications , 2008, SIGCOMM '08.

[10]  Reinaldo Penno,et al.  ALTO Information Export Service , 2008 .

[11]  Dan Wing,et al.  Session Traversal Utilities for NAT (STUN) , 2020, RFC.

[12]  Jan Seedorf,et al.  Application-Layer Traffic Optimization (ALTO) Problem Statement , 2009 .

[13]  Vidya Narayanan,et al.  A Client to Service Query Response Protocol for ALTO , 2009 .

[14]  Anja Feldmann,et al.  The PROXIDOR Service , 2009 .

[15]  David Harrington Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions , 2009, RFC.

[16]  Rainer Gerhards,et al.  The Syslog Protocol , 2009, RFC.

[17]  Yang Yang,et al.  P4P Protocol Specification , 2009 .

[18]  Masanobu Kawashima,et al.  A Recommendation for IPv6 Address Text Representation , 2010, RFC.

[19]  Fred Baker,et al.  Framework for IPv4/IPv6 Translation , 2011, RFC.

[20]  Jon Peterson,et al.  ALTO Network-Server and Server-Server APIs , 2011 .

[21]  Jeff Hodges,et al.  Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS) , 2011, RFC.

[22]  Fred Baker,et al.  IPv6-to-IPv6 Network Prefix Translation , 2011, RFC.

[23]  Martin Stiemerling,et al.  ALTO Deployment Considerations , 2011 .

[24]  Martin Stiemerling,et al.  Application-Layer Traffic Optimization (ALTO) Requirements , 2012, RFC.

[25]  Jan Medved,et al.  Use Cases for ALTO within CDNs , 2012 .

[26]  Roy T. Fielding,et al.  Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content , 2014, RFC.

[27]  Tim Bray,et al.  Internet Engineering Task Force (ietf) the Javascript Object Notation (json) Data Interchange Format , 2022 .

[28]  Roy T. Fielding,et al.  Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing , 2014, RFC.

[29]  Thomas Narten,et al.  Guidelines for Writing an IANA Considerations Section in RFCs , 1998, RFC.

[30]  Eric Rescorla,et al.  The Transport Layer Security (TLS) Protocol Version 1.3 , 2018, RFC.