Hi,
As discussed during the ALTO WG meeting, a new version
draft-ietf-alto-multi-cost-08 has been uploaded. The updates are listed below.
Thanks,
Sabine
----------------------------- v08 updates
--------------------------------------------------------
--- Section 3.6.5. Legacy ALTO Client issues
Addressed language update request from secdir.
In 1st paragraph, replaced "legacy" by "legacy client".
--- Section 4.2.3. Response
Harmonized definition of ALTO responses for the ECS with section 4.1.3. Response
<t>In "meta", the value of field "cost-type" will be ignored by
the receiver and set to {}. Instead, the field "multi-cost-types"
is added with the same value as the "multi-cost-types" input parameter.</t>
--- Section 7. Privacy And Security Considerations
Appended text sent to the secdir, with slight re-wording
"<t>The Multi-Cost optimization even
tends to reduce the on the wire data exchange volume, compared to
multiple
single cost ALTO transactions. Likewise, the risk related to massive
Multi-Cost
requests is moderated by the fact that Multi-Cost constraints
additionally
filter ALTO Server responses and thus reduce their volume.</t>"
----------------------------- v08 updates
--------------------------------------------------------
>>-----Original Message-----
>>From: alto [mailto:[email protected]] On Behalf Of internet-
>>[email protected]
>>Sent: 05 April 2017 14:45
>>To: [email protected]
>>Cc: [email protected]
>>Subject: [alto] I-D Action: draft-ietf-alto-multi-cost-08.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-08.txt
>> Pages : 29
>> Date : 2017-04-05
>>
>>Abstract:
>> The ALTO (Application Layer-Traffic Optimization) Protocol
>> ([RFC7285]) defines several services that return various metrics
>> describing the costs between network endpoints. 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. For
>> example, when downloading a file that is mirrored on several sites, a
>> user application may consider more than one metric, perhaps trading
>> bandwidth for latency to determine the most efficient mirror site.
>>
>> While the base ALTO Protocol allows an ALTO 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 are also htmlized versions available at:
>>https://tools.ietf.org/html/draft-ietf-alto-multi-cost-08
>>https://datatracker.ietf.org/doc/html/draft-ietf-alto-multi-cost-08
>>
>>A diff from the previous version is available at:
>>https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-multi-cost-08
>>
>>
>>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
