Hi Kai, Qiao, Fred and all, We have posted a new version of Multi-Cost ALTO according to your feedback. For short:
- The extensions overview on "testable-cost-type-names", "constraints" and "or-constraints" has been further clarified with additional subsections see 3.6.1 to 3.6.5, - the design for the testable-cost-type-names capability (section 4.1.1) has been updated according to Kai's feedback: "testable-cost-type-names" and "cost-constraints" are now mutually exclusive to prevent legacy clients from issuing constraint tests on untestable cost types, - the text on "constraints" and "or-constraints" input members in section 4.1.2 has been updated accordingly, - the or-constraint member has been corrected to [JSONString or-constraints<0..*><0..*>;], please note that this member will be corrected to [JSONString or-constraints<1..*><1..*>;] in the next draft version. - the ipv4 examples in section 5.6 have been extended with ipv6 examples, Again thank you all for your valuable comments. Please take a look and let us know if these updates meet your expectations, Thanks, Sabine, Wendy >>-----Message d'origine----- >>De : alto [mailto:[email protected]] De la part de internet- >>[email protected] >>Envoyé : lundi 13 juin 2016 18:15 >>À : [email protected] >>Cc : [email protected] >>Objet : [alto] I-D Action: draft-ietf-alto-multi-cost-02.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 >>of the IETF. >> >> Title : Multi-Cost ALTO >> Authors : Sabine Randriamasy >> Wendy Roome >> Nico Schwan >> Filename : draft-ietf-alto-multi-cost-02.txt >> Pages : 27 >> Date : 2016-06-13 >> >>Abstract: >> The ALTO (Application Layer-Traffic Optimization) Protocol >> ([RFC7285]) defines several services that return various metrics >> describing the costs between network endpoints. For example, when >> downloading a file that is mirrored on several sites, a user >> application may use these ALTO cost metrics to determine the most >> efficient mirror site. >> >> An ALTO Server may offer a variety of cost metrics, based on >>latency, >> bandwidth, hop count, jitter, or whatever else the ALTO Server deems >> useful. When selecting a mirror site, a client may consider more >> than one metric, perhaps trading bandwidth for latency. While the >> base ALTO Protocol allows a client to use more than one cost metric, >> to do so, the client must request each metric separately. This >> document defines a new service that allows a client to retrieve >> several cost metrics with one request, which is considerably more >> efficient. In addition, this document extends the ALTO constraint >> tests to allow a user to specify an arbitrary logical combination of >> tests on several cost metrics. >> >> >> >>The IETF datatracker status page for this draft is: >>https://datatracker.ietf.org/doc/draft-ietf-alto-multi-cost/ >> >>There's also a htmlized version available at: >>https://tools.ietf.org/html/draft-ietf-alto-multi-cost-02 >> >>A diff from the previous version is available at: >>https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-multi-cost-02 >> >> >>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
