[altoext] [Fwd: [Fwd: I-D Action: draft-randriamasy-alto-multi-cost-06.txt]]

Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com> Tue, 13 March 2012 17:06 UTC

Message-ID: <4F5F7E72.8070903@alcatel-lucent.com>
Date: Tue, 13 Mar 2012 18:05:54 +0100
From: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: altoext@ietf.org
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "SCHWAN, Nico" <Nico.Schwan@alcatel-lucent.com>
Subject: [altoext] [Fwd: [Fwd: I-D Action: draft-randriamasy-alto-multi-cost-06.txt]]
Precedence: list

Hi all,

below is an e-mail to the ALTO list advertising a new version of the 
multi-cost draft.
See mail below and 
http://tools.ietf.org/id/draft-randriamasy-alto-multi-cost-06.txt

As a part of this draft proposes extensions to the cost information and 
exposes  use cases motivating these extensions, I also posted it to the 
altoext list but didn't see it appear.
If this was intentional, then I apologize for the spam.
Otherwise we would appreciate your feedback and suggestions.

Thanks
Sabine & Nico

-------- Message original --------
Sujet : 	[Fwd: I-D Action: draft-randriamasy-alto-multi-cost-06.txt]
Date : 	Tue, 13 Mar 2012 02:03:04 +0100
De : 	Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
Pour : 	alto@ietf.org <alto@ietf.org>, altoext@ietf.org <altoext@ietf.org>
Copie à : 	Schwan, Nico (Nico) <nico.schwan@alcatel-lucent.com>



Hi all,

We have submitted a new version of the draft "Multi-Cost ALTO", where 
the first part includes use cases motivating the introduction of 
additional cost types, the usage of of multiple costs to select 
endpoints and their simultaneous usage in a single transaction. New ALTO 
use cases brought in the altoex draft are taken into account.

The second part lists and specifies the required & recommended 
extensions of the base ALTO protocol to support multi-cost transactions 
and specified the proposed Multi-Cost Services for the Cost Map end 
Endpoint Cost services. This part however is based in the previous 
version (10) of the ALTO protocol. So that this draft and the previous 
one (05) present 2 options are possible for the specs, with light 
changes depending on the outcomes of the WG discussions in ALTO and i2aex.

As this draft relates to both ALTO and i2aex topics, this message is 
posted on both lists.

The part on "dynamic" costs, present in the previous version (05) has 
been removed and presented in a separate draft.

Discussions and new ALTO use cases brought in the altoex mailing list 
are considered as well as previous discussions since the last IETF. We 
would like to focus the discussion on the motivation and use cases but 
feedback on any aspect of the draft is wellcome.

Thanks
Sabine


-------- Message original --------
Sujet : 	I-D Action: draft-randriamasy-alto-multi-cost-06.txt
Date : 	Tue, 13 Mar 2012 00:48:52 +0100
De : 	internet-drafts@ietf.org <internet-drafts@ietf.org>
Répondre à : 	internet-drafts@ietf.org <internet-drafts@ietf.org>
Pour : 	i-d-announce@ietf.org <i-d-announce@ietf.org>




-- 






-- 

---------------------------------------------------------
Sabine RANDRIAMASY 
Alcatel-Lucent Bell Labs France 
Centre de Villarceau
Route de Villejust - 91620 NOZAY - FRANCE

E-MAIL : Sabine.Randriamasy@alcatel-lucent.com
TEL: +33 (0)1 30 77 27 45 
         (On Net) 2 103 27 45
---------------------------------------------------------

[altoext] [Fwd: I-D Action: draft-randriamasy-alt… Sabine Randriamasy
[altoext] [Fwd: [Fwd: I-D Action: draft-randriama… Sabine Randriamasy