Dear ALTO WG, The version below addresses the reviews received from our AD Martin Duke, the IANA with Sabrina Tanamal, the OPSDIR Scott Bradner, the ARTDIR Spencer Dawkins and the SECDIR Paul Wouters. Great thanks to all of you for your review, insight and valuable guidance. This v19 It has been edited upon your feedback to our proposed updates. We hope all the issues have been solved. Until the submission deadline, I will: - Detail to Spencer and Mike Bishop how their comments have been addressed, - look-up occurrences of "domain name" where "entity" should be inserted, - wait for your further feedback.
Thanks, Sabine >-----Original Message----- >From: alto <[email protected]> On Behalf Of [email protected] >Sent: Monday, October 25, 2021 7:03 PM >To: [email protected] >Cc: [email protected] >Subject: [alto] I-D Action: draft-ietf-alto-unified-props-new-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: Entity Property Maps > Authors : Wendy Roome > Sabine Randriamasy > Y. Richard Yang > Jingxuan Jensen Zhang > Kai Gao > Filename : draft-ietf-alto-unified-props-new-19.txt > Pages : 61 > Date : 2021-10-25 > >Abstract: > This document specifies an extension to the base Application-Layer > Traffic Optimization (ALTO) Protocol that generalizes the concept of > "endpoint properties", which were so far tied to IP addresses, to > entities defined by a wide set of objects. Further, these properties > are presented as maps, similar to the network and cost maps in the > base ALTO protocol. While supporting the endpoints and related > endpoint property service defined in RFC7285, the protocol is > extended in two major directions. First, from endpoints restricted > to IP addresses to entities covering a wider and extensible set of > objects; second, from properties on specific endpoints to entire > entity property maps. These extensions introduce additional features > allowing entities and property values to be specific to a given > information resource. This is made possible by a generic and > flexible design of entity and property types. > > >The IETF datatracker status page for this draft is: >https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ > >There is also an htmlized version available at: >https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-19 > >A diff from the previous version is available at: >https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-19 > > >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
