Hi Jensen and WG I started to review the draft. I have one technical comment that I would like to share:
In section 5.1 (Cost Mode : Array): *"This document extends the CostMode defined in Section 10.5 of [RFC7285] with a new cost mode: "array". This cost mode indicates that every cost value in a cost map represents an array rather than a simple value. The values are arrays of JSONValue."* It seems that the current path-vector draft can not support multi-paths between source/destination points. What if an ALTO client wants to know the different paths (or all paths) for a pair of endpoints or PIDs?. For example, in the Broker-assisted architecture, a filtered cost map could provide an array of arrays of values to provide all possible paths for each source and destination node. Let me know your thoughts about that. Ss Danny Lachos On Mon, Jul 2, 2018 at 5:08 PM Jensen Zhang <[email protected]> wrote: > Hi all, > > In this revision -04, we do the following changes: > > - The major change is to decouple the multipart query service from the > path vector. > - Instead, A capability called "allow-compound-response" is introduced > to make the property map inline. > - The multipart query service is moved to a new document and defined > for the general cases. > - The examples section is revised to better explain the usage of the path > vector extension. > - The compatibility of the path vector extension is better clarified. > - Some general discussions are raised. > > Looking forward to receiving your feedback. > > Thanks, > Jensen > > On Tue, Jul 3, 2018 at 3:46 AM <[email protected]> wrote: > >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the Application-Layer Traffic Optimization >> WG of the IETF. >> >> Title : ALTO Extension: Path Vector Cost Type >> Authors : Greg Bernstein >> Shiwei Dawn Chen >> Kai Gao >> Young Lee >> Wendy Roome >> Michael Scharf >> Y. Richard Yang >> Jingxuan Jensen Zhang >> Filename : draft-ietf-alto-path-vector-04.txt >> Pages : 29 >> Date : 2018-07-02 >> >> 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 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. >> >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ >> >> There are also htmlized versions available at: >> https://tools.ietf.org/html/draft-ietf-alto-path-vector-04 >> https://datatracker.ietf.org/doc/html/draft-ietf-alto-path-vector-04 >> >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-04 >> >> >> Please note that it may take a couple of minutes from the time of >> submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> alto mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/alto >> > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
