%% You should probably cite rfc9275 instead of this I-D.
@techreport{ietf-alto-path-vector-07,
    number =    {draft-ietf-alto-path-vector-07},
    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/07/},
    author =    {Kai Gao and Young Lee and Sabine Randriamasy and Y. Richard Yang and Jingxuan Zhang},
    title =     {{ALTO Extension: Path Vector Cost Type}},
    pagetotal = 29,
    year =      ** No value found for 'doc.pub_date.year' **,
    month =     ** No value found for 'doc.pub_date' **,
    day =       ** No value found for 'doc.pub_date.day' **,
    abstract =  {The Application-Layer Traffic Optimization (ALTO) protocol {[}RFC7285{]} has defined cost maps and endpoint cost maps to provide basic network information. However, they provide only scalar (numerical or ordinal) cost mode values, 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 the capacity region for a given set of flows (called co-flows). A non-normative example called co-flow scheduling is presented to illustrate the limitations of existing ALTO endpoint cost maps. After that, details of the extension are defined.},
}