Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

Q. Wu
Y. Yang
Y. Lee
D. Dhody
S. Randriamasy
L. Contreras

Stream:

IETF

Source:

alto (ops)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9439

Discuss this RFC: Send questions or comments to the mailing listalto@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9439

Abstract

The cost metric is a basic concept in Application-Layer TrafficOptimization (ALTO), and different applications may use differenttypes 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 endpointcost request in order to identify a resource provider that offersbetter performance metrics (e.g., lower delay or loss rate), the baseprotocol does not define the cost metric to be used.

This document addresses this issue by extending the specification toprovide a variety of network performance metrics, including networkdelay, delay variation (a.k.a. jitter), packet loss rate, hop count,and bandwidth.

There are multiple sources (e.g., estimations based on measurementsor a Service Level Agreement) available for deriving a performancemetric. This document introduces an additional "cost-context" fieldto the ALTO "cost-type" field to convey the source of a performancemetric.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.