RFC 9439: Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics
In plain English — editorial summary, not part of the RFC
The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers better performance metrics (e.g., lower delay or loss rate), the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (a.k.a. jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimations based on measurements or a Service Level Agreement) available for deriving a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric.
Document record
- Document ID
- RFC9439
- Published
- August 2023
- Authors
- Q. Wu; Y. Yang; Y. Lee; D. Dhody; S. Randriamasy; L. Contreras
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9728OAuth 2.0 Protected Resource MetadataCurrent
April 2025
- RFC 9101The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)Current
August 2021
- RFC 8936Poll-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8935Push-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8414OAuth 2.0 Authorization Server MetadataCurrent
June 2018
- RFC 8142GeoJSON Text SequencesCurrent
April 2017
- RFC 7946The GeoJSON FormatCurrent
August 2016
- RFC 7797JSON Web Signature (JWS) Unencoded Payload OptionCurrent
February 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?