Skip to main content

An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector
RFC 9275

Revision differences

Document history

Date By Action
2022-09-23
(System)
Received changes through RFC Editor sync (created alias RFC 9275, changed title to 'An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector', changed abstract …
Received changes through RFC Editor sync (created alias RFC 9275, changed title to 'An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector', changed abstract to 'This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol.  It extends the ALTO cost map and ALTO property map services so that an application can decide to which endpoint(s) to connect based not only on numerical/ordinal cost values but also on fine-grained abstract information regarding the paths.  This is useful for applications whose performance is impacted by specific components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths.  This extension introduces a new abstraction called the "Abstract Network Element" (ANE) to represent these components and encodes a network path as a vector of ANEs.  Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints.', changed pages to 54, changed standardization level to Experimental, changed state to RFC, added RFC published event at 2022-09-23, changed IESG state to RFC Published)
2022-09-23
(System) RFC published