<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.yang-alto-general-cost-type" target="https://datatracker.ietf.org/doc/html/draft-yang-alto-general-cost-type-00">
   <front>
      <title>ALTO Extension: General Cost Types</title>
      <author initials="Y. R." surname="Yang" fullname="Y. Richard Yang">
         <organization>Yale University</organization>
      </author>
      <date month="October" day="19" year="2015" />
      <abstract>
	 <t>   The Application-Layer Traffic Optimization (ALTO) Service has defined
   both the endpoint cost service (ECS) and cost maps to provide
   information to applications about network path properties (e.g.,
   routingcost) from a set of source network points to a set of
   destination network points, where each network point can be a single
   endpoint (in ECS) or a PID which represents a set of endpoints (in a
   cost map).  Considering, conceptually, both ECS and cost map as
   returning a matrix, indexed by sources and destinations as row and
   column, the current ALTO protocol [RFC7285] allows the elements in
   the matrix to be only scalar (i.e., numerical or ordinal).  This,
   however, is limiting in many use cases.  This document discuss
   multiple use cases where scalar-elements can be limitations.  It then
   defines new cost types to allow general cost types, such as vectors
   to represent use cases such path vectors.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-yang-alto-general-cost-type-00" />
   
</reference>
