%% You should probably cite draft-ietf-alto-path-vector instead of this I-D. @techreport{yang-alto-path-vector-04, number = {draft-yang-alto-path-vector-04}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-yang-alto-path-vector/04/}, author = {Greg M. Bernstein and Shiwei Dawn Chen and Kai Gao and Young Lee and Wendy Roome and Michael Scharf and Y. Richard Yang and Jingxuan Zhang}, title = {{ALTO Extension: Path Vector Cost Mode}}, pagetotal = 30, year = 2017, month = mar, day = 13, abstract = {The Application-Layer Traffic Optimization (ALTO) Service has defined network and cost maps to provide basic network information, where the cost maps allow only scalar (numerical or ordinal) cost mode values. This document introduces a new cost mode called path-vector to allow ALTO clients to support use cases such as capacity regions for applications. This document starts with a non-normative example called multi-flow scheduling (or capacity region) to illustrate that ALTO cost maps without path vectors cannot provide sufficient information. This document then defines path-vector as a new cost mode.}, }