[alto] [Fwd: New Version Notification for draft-randriamasy-alto-cost-schedule-00.txt]
Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com> Mon, 19 March 2012 22:40 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 E4E8F21E8046 for <alto@ietfa.amsl.com>; Mon, 19 Mar 2012 15:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.249
X-Spam-Level:
X-Spam-Status: No, score=-9.249 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
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 CXG+VBFhNgJ8 for <alto@ietfa.amsl.com>; Mon, 19 Mar 2012 15:40:27 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 12DD621F8852 for <alto@ietf.org>; Mon, 19 Mar 2012 15:40:26 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q2JMePPh013933 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <alto@ietf.org>; Mon, 19 Mar 2012 23:40:26 +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 23:40:25 +0100
Message-ID: <4F67B5D4.3050907@alcatel-lucent.com>
Date: Mon, 19 Mar 2012 23:40:20 +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="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Subject: [alto] [Fwd: New Version Notification for draft-randriamasy-alto-cost-schedule-00.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: Mon, 19 Mar 2012 22:40:28 -0000
Hi all, We have submitted a new draft entitled ALTO Cost Schedule and proposing extensions on Cost Value specifications. The idea is to provide cost values as a set of values each defined on a given time period, together with appropriate description attributes. The main motivation is that current ALTO Costs and their modes provide static values, assuming to report on information that does not change rapidly. However the ALTO use cases now extend to CDNs, Data centers and non real time applications that deal with information changing rapidly. If this information can be predicted, non-real time applications or management systems using ALTO could take advantage of scheduling their access to content or resources. Another motivation of scheduled costs is the need to regulate the traffic through incentives: if ALTO provides an abstracted or aggregated form of dynamic information that is centrally managed (and readable), it can help preserving network stability while keeping network state information confidential. This draft has also been advertised on the altoex mailing-list but we would appreciate your feedback on the use cases (relevance, whether other ones are applicable), whether it makes sense to extend ALTO to support time-dependent arrays of cost values. Thanks, Sabine -------- Message original -------- Sujet : New Version Notification for draft-randriamasy-alto-cost-schedule-00.txt Date : Tue, 6 Mar 2012 01:53:25 +0100 De : internet-drafts@ietf.org <internet-drafts@ietf.org> Pour : RANDRIAMASY, SABINE (SABINE) <sabine.randriamasy@alcatel-lucent.com> Copie à : Schwan, Nico (Nico) <nico.schwan@alcatel-lucent.com> A new version of I-D, draft-randriamasy-alto-cost-schedule-00.txt has been successfully submitted by Sabine Randriamasy and posted to the IETF repository. Filename: draft-randriamasy-alto-cost-schedule Revision: 00 Title: ALTO Cost Schedule Creation date: 2012-03-05 WG ID: Individual Submission Number of pages: 13 Abstract: The goal of Application-Layer Traffic Optimization (ALTO) is to bridge the gap between network and applications by provisioning network related information. This allows applications to make informed decisions, for example when selecting a target host from a set of candidates. The ALTO problem statement [RFC5693] considers typical applications as file sharing, real-time communication and live streaming peer-to-peer networks. Recently other use cases focused on Content Distribution Networks and Data Centers have emerged [draft-jenkins-alto-cdn-use-cases-01]. The present draft proposes to extend the cost information provided by the ALTO protocol. The purpose is to broaden the decision possibilities of applications to not only decide 'where' to connect to, but also 'when' to connect. This is useful to applications that have a degree of freedom on when to schedule data transfers, such as non-instantaneous data replication between data centers. The draft therefore specifies a new cost mode, called the "schedule" mode. In this mode the ALTO server offers cost maps that contain link ratings that are valid for a given timeframe (e.g. hourly) for a period of time (e.g. a day). Besides the functional time-shift enhancement providing multi-timeframe cost values the extansion also allows the saving of a number of ALTO transactions and thus resources on the ALTO server and clients. The IETF Secretariat
- [alto] [Fwd: New Version Notification for draft-r… Sabine Randriamasy