Dear WG members and reviewers, We have just submitted a new version of the Path Vector draft. This revision addresses the comments in the Last Call reviews, most notably:
1. Add IPv6 examples 2. Change the "content-id" format in multipart messages to conform to RFC 2387 & 5322 3. Add descriptions of potential use cases including a. what is the role of ALTO server/client b. what information can be provided c. how the ALTO client may use the information 4. Add examples for abstract network elements in Sec 5.1 5. Add a paragraph to clarify "ANE domain" in Sec 6.2 6. Add paragraphs to emphasize the role of ALTO when providing max-reservable-bandwidth property Diffs: https://www.ietf.org/rfcdiff?url1=draft-ietf-alto-path-vector-17&url2=draft-ietf-alto-path-vector-19 Best, Kai -----Original Messages----- From: internet-dra...@ietf.org Sent Time: 2021-10-26 07:34:54 (Tuesday) To: i-d-annou...@ietf.org Cc: alto@ietf.org Subject: [alto] I-D Action: draft-ietf-alto-path-vector-19.txt 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 Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename : draft-ietf-alto-path-vector-19.txt Pages : 63 Date : 2021-10-25 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map service and ALTO Property Map service so that the application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also details of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-19.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-19 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto _______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
