[alto] Protocol extensions for multi-cost information

Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com> Mon, 19 March 2012 21:57 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 00E2321E8012 for <alto@ietfa.amsl.com>; Mon, 19 Mar 2012 14:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.582
X-Spam-Level:
X-Spam-Status: No, score=-7.582 tagged_above=-999 required=5 tests=[AWL=-1.333, 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 bim9KRgZpyFK for <alto@ietfa.amsl.com>; Mon, 19 Mar 2012 14:57:39 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [62.23.212.56]) by ietfa.amsl.com (Postfix) with ESMTP id 17CD521E800C for <alto@ietf.org>; Mon, 19 Mar 2012 14:57:38 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q2JLvaIL022800 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <alto@ietf.org>; Mon, 19 Mar 2012 22:57:37 +0100
Received: from [135.244.225.39] (135.120.57.7) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 19 Mar 2012 22:57:37 +0100
Message-ID: <4F67ABCB.2@alcatel-lucent.com>
Date: Mon, 19 Mar 2012 22:57:31 +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>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: [alto] Protocol extensions for multi-cost information
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: Mon, 19 Mar 2012 21:57:40 -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 draft-marocco-alto-next-00 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.

We now seek your opinion on the principle of specifying Alto protocol 
extensions to enable Multi-Cost transactions and get this document 
adopted as a WG doc. To this end we present additional use cases that 
motivate the need to do this. The mechanics will be further specified 
and based on versions 05/06.

Thanks,
Sabine

--