ALTO Extensions for Traffic Engineering (TE) performance metrics in JSON format

Document Type Expired Internet-Draft (individual)
Authors Qin Wu  , Young Lee  , Dhruv Dhody 
Last updated 2014-04-23 (latest revision 2013-10-20)
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. However the base protocol defines only a single cost metric, i.e., the generic "routingcost" metric (Sec. 14.2 of ALTO base specification [ALTO]). In practice, applications may request network information on other cost (including performance) metrics. In this document, we define five new base metrics which are delay, jitter, pktloss (packet loss), bandwidth and hopcount. These base metrics are further extended with these nine new metrics linkdelay, linkjitter, linkloss, maxbw (Maximum Bandwidth), maxreservbw (Maximum Reserved Bandwdith), unreservbw (Unreserved Bandwidth), residuebw (Residual Bandwidth), availbw (Available Bandwidth), and utilbw (Utilized Bandwidth). Also a new parameter anomalousstate is added. These fourteen cost metrics are derived from OSPF-TE and ISIS-TE and can be either used as constraint attribute associated with 'routingcost' cost metric attribute or used as returned Cost metrics in the response, or both and hence provide a relatively comprehensive set of cost metrics for ALTO.


Qin Wu (
Young Lee (
Dhruv Dhody (

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