Skip to main content

ALTO Performance Cost Metrics

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Qin Wu , Y. Richard Yang , Young Lee , Dhruv Dhody , Sabine Randriamasy
Last updated 2016-08-29
Replaced by RFC 9439
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-alto-performance-metrics
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Cost Metric is a basic concept in Application-Layer Traffic Optimization (ALTO). It is used in both the Cost Map Service and the Endpoint Cost Service. Future extensions to ALTO may also use Cost Metric. Different applications may benefit from different Cost Metrics. For example, a Resource Consumer may prefer Resource Providers that have low delay to the Resource Consumer. However the base ALTO protocol [ALTO] has documented only a single cost metric, i.e., the generic "routingcost" metric (Sec. 14.2 of ALTO base specification [ALTO]). In this document, we proposes a set of Cost Metrics, derived and aggregated from routing protocols with different granularity and scope, such as BGP-LS,OSPF-TE and ISIS-TE, or from end to end traffic management tool. We currently document 11 new Performance Metric to measure network delay, jitter, packet loss, hop count, and bandwidth. The metrics documented in this document provide a relatively comprehensive set of Cost Metrics for ALTO and allow applications to determine "where" to connect based on end to end network performance criteria. Additional Cost Metrics such as financial cost metrics may be documented in other documents.


Qin Wu
Y. Richard Yang
Young Lee
Dhruv Dhody
Sabine Randriamasy

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)