Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 35
- Abstract
- 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.
- Publication Date
- 2023-08-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC9439- Link
- https://doi.org/10.17487/RFC9439
- Author(s)
- Qin WuY. Richard YangYoung LeeDhruv DhodySabine RandriamasyLuis M. Contreras
- Keyword(s)
- JSON, ALTO
Latest version of IETF RFC 9439
Document Versions — IETF RFC 9439
-
▶ IETF RFC 9439 (2023-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IANA, "Performance Metrics", <https://www.iana.org/assignments/performance-metrics/>. EXTERNAL
- IETF RFC 2119 [Active*]
- IETF RFC 3630 [Active*]
- IETF RFC 5305 [Active*]
- IETF RFC 6390 [Active*]
- IETF RFC 7285 [Active*]
- IETF RFC 7471 [Active*]
- IETF RFC 8126 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8259 [Active*]
- IETF RFC 8446 [Superseded*]
- IETF RFC 8570 [Active*]
- IETF RFC 8571 [Active*]
- RFC8895 — RFC8895 EXTERNAL
- IETF RFC 9110 [Active*]
- IETF RFC 9438 [Active*]
Bibliographic Reference(s)
- 10.1109-TNET.2020.3016838 — Prophet EXTERNAL
- 10.1145-3366707 — G2 EXTERNAL
- IETF.draft-corre-quic-throughput-testing-00 — I-D.corre-quic-throughput-testing EXTERNAL
- Volz, J. and B. Rabenstein, "Prometheus: A Next-Generation Monitoring System (Talk)", SREcon15 Europe, May 2015. EXTERNAL
- Pujol, E., Poese, I., Zerwas, J., Smaragdakis, G., and A. Feldmann, "Steering Hyper-Giants' Traffic at Scale", ACM CoNEXT '19, December 2019. EXTERNAL
- IETF RFC 2330 [Active*]
- IETF RFC 2681 [Active*]
- IETF RFC 3393 [Active*]
- IETF RFC 5357 [Active*]
- IETF RFC 7679 [Active*]
- RFC7971 — RFC7971 EXTERNAL
- IETF RFC 9000 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC9439.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 9439, Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics. Available at https://doi.org/10.17487/RFC9439
Snippet:
IETF RFC 9439, Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics. Available at https://doi.org/10.17487/RFC9439
HTML (ISO 690 compliant)
Preview:
IETF RFC 9439, Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics. Available at https://doi.org/10.17487/RFC9439
Snippet:
<span class="citation"><cite>IETF RFC 9439</cite>, Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics. Available at <a href="https://doi.org/10.17487/RFC9439" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9439</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 9439, Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics
doi: 10.17487/RFC9439
url: https://doi.org/10.17487/RFC9439
doi: 10.17487/RFC9439
url: https://doi.org/10.17487/RFC9439
Snippet:
<li> <cite id="bib-rfc9439">IETF RFC 9439</cite>, Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics <span class="doi">10.17487/RFC9439</span> </li>
Referenced By
- IETF RFC 9522 [Active*]