<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-alto-path-vector" target="https://datatracker.ietf.org/doc/html/draft-ietf-alto-path-vector-00">
   <front>
      <title>ALTO Extension: Path Vector Cost Mode</title>
      <author initials="G. M." surname="Bernstein" fullname="Greg M. Bernstein">
         </author>
      <author initials="S. D." surname="Chen" fullname="Shiwei Dawn Chen">
         </author>
      <author initials="K." surname="Gao" fullname="Kai Gao">
         </author>
      <author initials="Y." surname="Lee" fullname="Young Lee">
         </author>
      <author initials="W." surname="Roome" fullname="Wendy Roome">
         </author>
      <author initials="M." surname="Scharf" fullname="Michael Scharf">
         </author>
      <author initials="Y. R." surname="Yang" fullname="Y. Richard Yang">
         </author>
      <author initials="J." surname="Zhang" fullname="Jingxuan Zhang">
         </author>
      <date month="May" day="6" year="2017" />
      <abstract>
	 <t>   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.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-alto-path-vector-00" />
   
</reference>
