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

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

Return-Path: <sabine.randriamasy@alcatel-lucent.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A60B011E8083; Mon, 12 Mar 2012 18:03:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.249
X-Spam-Level:
X-Spam-Status: No, score=-8.249 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4CSd7D76QaDc; Mon, 12 Mar 2012 18:03:13 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by ietfa.amsl.com (Postfix) with ESMTP id D23AF11E8079; Mon, 12 Mar 2012 18:03:12 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q2D13Brs020719 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 13 Mar 2012 02:03:11 +0100
Received: from [135.244.225.73] (135.120.57.7) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (135.120.45.61) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 13 Mar 2012 02:03:10 +0100
Message-ID: <4F5E9CC8.50205@alcatel-lucent.com>
Date: Tue, 13 Mar 2012 02:03:04 +0100
From: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>, altoext@ietf.org
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Subject: [alto] [Fwd: I-D Action: draft-randriamasy-alto-multi-cost-06.txt]
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 01:03:13 -0000

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>




--