Hi all,
We have posted a new version of the Multi-Cost ALTO extension proposal. This
update aims at minimizing the number of protocol updates needed to support
Multi-Cost ALTO Services.
Our intent is to gauge the dispositions of this draft with respect to being a
WG item.
Please see our summary below. Any feedback and comments on the draft is welcome.
Thanks,
Sabine and Wendy
In a nutshell, the Multi-Cost (MC) ALTO extension:
- allows to carry multiple cost metrics in a single ALTO request or response,
- allows to combine 'AND' and 'OR' logical operators on constraints, allowing
requests such as for example "give me costs among {those PIDs/Endpoints} that
satisfy 'hopcount' = 0 OR routingcost in [5, 10]"
- proposes additional abstracted TE-related Cost metrics to score resources
availabilities
Applicable service information resources are: Cost Map (CM), Filtered Cost Map
(FCM), Endpoint Cost Map (ECM)
The updates proposed in the MC ALTO draft:
- stay with the same media types for MC service information resources
- the following fields are added:
Capability fields:
multi-cost-type-names:
Array of cost type names. Presence means this resource can return
a multi-cost. A filtered cost map resource can have either
cost-type-names
or multi-cost-type-names or both. Former means it can return a
single
cost, latter a multi cost. Client selects which.
A full cost map resource has cost-type-names or
multi-cost-type-names,
but not both. Former means it returns a single cost, latter
means it returns
a multi cost. Since it is get-mode, the resource returns what it
returns;
the client has no choice.
testable-cost-types:
Array of cost-type names that can be used in Multi- Cost and
Logical Operator (MCLO) constraints.
Presence means this resource supports MCLO constraints.
Server response fields:
multi-cost-types:
Used in meta of multi-cost response, instead of cost-type.
An array of cost-types, in the order in which they appear
in the multi-cost array.
Client request fields:
multi-cost-types:
For multi-cost aware filtered cost map resources, to get a
multi-cost
response, client provides multi-cost-types, instead of cost-types,
with an array of cost-types in the order in which the server
should return them.
>>-----Message d'origine-----
>>De : [email protected] [mailto:[email protected]]
>>Envoyé : lundi 9 mars 2015 20:21
>>À : Nico Schwan; RANDRIAMASY, SABINE (SABINE); RANDRIAMASY, SABINE
>>(SABINE); ROOME, Wendy D (Wendy); Nico Schwan; ROOME, Wendy D (Wendy)
>>Objet : New Version Notification for draft-randriamasy-alto-multi-cost-
>>10.txt
>>
>>
>>A new version of I-D, draft-randriamasy-alto-multi-cost-10.txt
>>has been successfully submitted by Sabine Randriamasy and posted to the
>>IETF repository.
>>
>>Name: draft-randriamasy-alto-multi-cost
>>Revision: 10
>>Title: Multi-Cost ALTO
>>Document date: 2015-03-09
>>Group: Individual Submission
>>Pages: 37
>>URL: http://www.ietf.org/internet-drafts/draft-randriamasy-
>>alto-multi-cost-10.txt
>>Status: https://datatracker.ietf.org/doc/draft-randriamasy-
>>alto-multi-cost/
>>Htmlized: http://tools.ietf.org/html/draft-randriamasy-alto-
>>multi-cost-10
>>Diff: http://www.ietf.org/rfcdiff?url2=draft-randriamasy-
>>alto-multi-cost-10
>>
>>Abstract:
>> IETF is designing a new service called ALTO (Application Layer
>> traffic Optimization) that includes a "Network Map Service", an
>> "Endpoint Cost Service" and an "Endpoint (EP) Ranking Service" and
>> thus incentives for application clients to connect to ISP preferred
>> Endpoints. These services provide a view of the Network Provider
>> (NP) topology to overlay clients.
>>
>> The present draft proposes a simple way to extend the information
>> provided by the current ALTO protocol in two ways. First, including
>> information on multiple Cost Types in a single ALTO transaction
>> provides a better mapping of the Selected Endpoints to needs of the
>> growing diversity of Content and Resources Networking Applications
>> and to the network conditions. Second, one ALTO query and response
>> exchange on N Cost Types is faster and more efficient than N single
>> cost transactions. All this also helps producing a faster and more
>> robust choice when multiple Endpoints need to be selected. Last,
>>the
>> draft proposes to enrich the filtering capabilities by allowing
>> constraints involving several metrics combined by several types of
>> logical operators. This allows the applications to set finer
>> requirements and above all to include compromises on those
>> requirements.
>>
>>
>>
>>
>>
>>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.
>>
>>The IETF Secretariat
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
