[alto] [Fwd: New Version Notification for draft-randriamasy-alto-multi-cost-07.txt]
Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com> Fri, 19 October 2012 16:14 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 B59AF21F8464 for <alto@ietfa.amsl.com>; Fri, 19 Oct 2012 09:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.149
X-Spam-Level:
X-Spam-Status: No, score=-10.149 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hU2x1NVBRIJY for <alto@ietfa.amsl.com>; Fri, 19 Oct 2012 09:14:59 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id CC89C21F8462 for <alto@ietf.org>; Fri, 19 Oct 2012 09:14:58 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q9JGElNc014580 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 19 Oct 2012 18:14:56 +0200
Received: from [172.27.204.144] (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; Fri, 19 Oct 2012 18:14:54 +0200
Message-ID: <50817C79.9090709@alcatel-lucent.com>
Date: Fri, 19 Oct 2012 18:14:49 +0200
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="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
Cc: Bill Roome <w.roome@alcatel-lucent.com>
Subject: [alto] [Fwd: New Version Notification for draft-randriamasy-alto-multi-cost-07.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: Fri, 19 Oct 2012 16:14:59 -0000
Hi all, We have just submitted a new version of draft Multi-Cost ALTO. Main diffs with the previous version (06): - there is no more incentive to require multiple costs in the 'numerical' mode (when applicable). The reason is that a multi-cost request can be done for any purpose, such as updates on one cost type in 'ordinal' combined with 'numerical'information on another cost type. The purpose does not restrict to multi variate optimization. - a new feature on constraints is introduced in section "4.6. Extended constraints on multi-cost values". It extends the base protocol in two ways: (1) combining constraints on multiple metrics related with a logical 'AND', to cover requirements such as: "select solutions with moderate routingcost" AND "low hopcount", (2) combining constraints on multiple metrics related with both a logical 'AND' and a logical 'OR'. This allows to cover constraints such as: "'hopcount' values in [6,20) OR 'routingcost' values in [100,200]" It also allows an application to make comprimises such as: "select solutions with either moderate 'hopcount' and high 'routingcost' OR higher 'hopcount' and moderate 'routingcost'". A specification for 'constraint' members of input parameters extended for multiple cost types and logical operators is provided in section 5. Comments and feedback on this new draft are more than wellcome, Thanks Sabine -------- Message original -------- Sujet : New Version Notification for draft-randriamasy-alto-multi-cost-07.txt Date : Fri, 19 Oct 2012 17:07:32 +0200 De : internet-drafts@ietf.org <internet-drafts@ietf.org> Pour : RANDRIAMASY, SABINE (SABINE) <sabine.randriamasy@alcatel-lucent.com> Copie à : Roome, W D <w.roome@alcatel-lucent.com>, ietf@nico-schwan.de <ietf@nico-schwan.de> A new version of I-D, draft-randriamasy-alto-multi-cost-07.txt has been successfully submitted by Sabine Randriamasy and posted to the IETF repository. Filename: draft-randriamasy-alto-multi-cost Revision: 07 Title: Multi-Cost ALTO Creation date: 2012-10-19 WG ID: Individual Submission Number of pages: 37 URL: http://www.ietf.org/internet-drafts/draft-randriamasy-alto-multi-cost-07.txt Status: http://datatracker.ietf.org/doc/draft-randriamasy-alto-multi-cost Htmlized: http://tools.ietf.org/html/draft-randriamasy-alto-multi-cost-07 Diff: http://www.ietf.org/rfcdiff?url2=draft-randriamasy-alto-multi-cost-07 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 light 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 lighter than N single cost transactions. All this also helps producing a faster and more robust choice when multiple Endpoints need to be selected. The IETF Secretariat
- [alto] [Fwd: New Version Notification for draft-r… Sabine Randriamasy