ALTO Traffic Engineering Cost Metrics

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Qin Wu  , Y. Yang  , Young Lee  , Dhruv Dhody  , Sabine Randriamasy 
Last updated 2015-11-02 (latest revision 2015-04-29)
Replaced by draft-ietf-alto-performance-metrics
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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 defined only a single cost metric, i.e., the generic "routingcost" metric (Sec. 14.2 of ALTO base specification [ALTO]). In this document, we define eleven Cost Metrics, derived from OSPF-TE and ISIS-TE, to measure network delay, jitter, packet loss, hop count, and bandwidth. The metrics defined in this document provide a relatively comprehensive set of Cost Metrics for ALTO focusing on traffic engineering (TE). Additional Cost Metrics such as financial cost metrics may be defined in other documents.


Qin Wu (
Y. 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.)