%% You should probably cite rfc9275 instead of this I-D.
@techreport{ietf-alto-path-vector-03,
    number =    {draft-ietf-alto-path-vector-03},
    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-path-vector/03/},
    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 Type}},
    pagetotal = 25,
    year =      2018,
    month =     mar,
    day =       5,
    abstract =  {The Application-Layer Traffic Optimization (ALTO) protocol {[}RFC7285{]} has defined several resources and services to provide clients with basic network information. However, the base ALTO protocol and latest extensions only provide end-to-end metrics, which are insufficient to satisfy the demands of solving more complex network optimization problems. This document introduces an extension to the base ALTO protocol, namely the path-vector extension, which allows ALTO clients to query information such as capacity regions for a given set of flows. A non-normative example called multi-flow scheduling is presented to illustrate the limitations of existing ALTO (endpoint) cost maps. After that, details of the extension are defined.},
}