%% You should probably cite rfc9439 instead of this I-D. @techreport{ietf-alto-performance-metrics-02, number = {draft-ietf-alto-performance-metrics-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/02/}, author = {Qin Wu and Y. Richard Yang and Young Lee and Dhruv Dhody and Sabine Randriamasy}, title = {{ALTO Performance Cost Metrics}}, pagetotal = 28, year = 2017, month = jul, day = 3, abstract = {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. Different applications may benefit from different Cost Metrics. For example, a Resource Consumer may prefer Resource Providers that offer a low delay delivery to the Resource Consumer. However the base ALTO protocol {[}ALTO{]} has documented only one single cost metric, i.e., the generic "routingcost" metric (Sec. 14.2 of ALTO base specification {[}ALTO{]}). This document, 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 tools. It currently documents Network Performance Cost Metrics reporting on network delay, jitter, packet loss, hop count, and bandwidth. These metrics may be exposed by an ALTO Server to allow applications to determine "where" to connect based on network performance criteria. Additional Cost Metrics involving ISP specific considerations or other network technologies may be documented in further versions of this draft.}, }