RFC 7285: 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…

Read RFC 7285 on the RFC Editor

Outgoing relationships (17 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Normative reference — RFC 6125: 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)
Normative reference — RFC 5389: Session Traversal Utilities for NAT (STUN)
Normative reference — RFC 1812: Requirements for IP Version 4 Routers
Normative reference — RFC 5952: A Recommendation for IPv6 Address Text Representation
Normative reference — RFC 4632: Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan
Normative reference — RFC 5424: The Syslog Protocol
Informative reference — RFC 2818: HTTP Over TLS
Informative reference — RFC 5706: Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions
Informative reference — RFC 6296: IPv6-to-IPv6 Network Prefix Translation
Informative reference — RFC 6144: Framework for IPv4/IPv6 Translation
Informative reference — RFC 5693: Application-Layer Traffic Optimization (ALTO) Problem Statement
Informative reference — RFC 6708: Application-Layer Traffic Optimization (ALTO) Requirements

Incoming relationships (16 related RFCs)

Updated by, Normatively referenced by — RFC 9274: A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol
Normatively referenced by — RFC 8895: Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
Normatively referenced by — RFC 7971: Application-Layer Traffic Optimization (ALTO) Deployment Considerations
Normatively referenced by — RFC 9240: An Extension for Application-Layer Traffic Optimization (ALTO): Entity Property Maps
Normatively referenced by — RFC 8896: Application-Layer Traffic Optimization (ALTO) Cost Calendar
Normatively referenced by — RFC 9241: Content Delivery Network Interconnection (CDNI) Footprint and Capabilities Advertisement Using Application-Layer Traffic Optimization (ALTO)
Normatively referenced by — RFC 9439: Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics
Normatively referenced by — RFC 7846: Peer-to-Peer Streaming Tracker Protocol (PPSTP)
Normatively referenced by — RFC 9569: The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS)
Informatively referenced by — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Informatively referenced by — RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
Informatively referenced by — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Informatively referenced by — RFC 7491: A PCE-Based Architecture for Application-Based Network Operations
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 7810: IS-IS Traffic Engineering (TE) Metric Extensions
Informatively referenced by — RFC 8686: Application-Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery