Re: [alto] New ALTO use cases & the upcoming IETF meeting
Leeyoung <leeyoung@huawei.com> Mon, 25 February 2013 22:49 UTC
Return-Path: <leeyoung@huawei.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 13ECD21E8112 for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 14:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Wlrpr8LpNgEc for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 14:49:27 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5C77521E80F2 for <alto@ietf.org>; Mon, 25 Feb 2013 14:49:27 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQB15523; Mon, 25 Feb 2013 22:49:26 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Feb 2013 22:49:24 +0000
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Feb 2013 22:49:25 +0000
Received: from dfweml511-mbs.china.huawei.com ([169.254.15.175]) by dfweml407-hub.china.huawei.com ([10.193.5.132]) with mapi id 14.01.0323.007; Mon, 25 Feb 2013 14:49:20 -0800
From: Leeyoung <leeyoung@huawei.com>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] New ALTO use cases & the upcoming IETF meeting
Thread-Index: AQHOECinm7C2AVtBUEKuLYy9ZUxBv5iLMZ9w
Date: Mon, 25 Feb 2013 22:49:18 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1729104FA5@dfweml511-mbs.china.huawei.com>
References: <51260845.1000909@neclab.eu>
In-Reply-To: <51260845.1000909@neclab.eu>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.179]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [alto] New ALTO use cases & the upcoming IETF meeting
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, 25 Feb 2013 22:49:29 -0000
Hi all, http://www.ietf.org/internet-drafts/draft-dhody-pce-cso-enabled-path-computation-03.txt I just wanted to bring your attention to this draft where ALTO is implied between APP and NET (Cross Stratum) in the context of an extended PCE architecture. ALTO is envisioned in this draft as a mechanism to collect network resource information to the application for their scheduling operation in an effort to select an optimal data center from a set of candidates. This draft addresses the need for underlying network resource information (such as application-specific virtual network topology) that can be made available to APP via ALTO interface. Your comments are appreciated. Regards, Dhruv and Young -----Original Message----- From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of Martin Stiemerling Sent: Thursday, February 21, 2013 5:43 AM To: alto@ietf.org Subject: [alto] New ALTO use cases & the upcoming IETF meeting Hi all, I have seen a number of new ALTO drafts for LMAP, I2RS, etc and also the wish to discuss a rechartering of the ALTO WG. I still do not see the WG to be ready for any rechartering discussion, as we should first finish up our current chartered items. However, I can see the utility to discuss new ideas on what to do with ALTO, but outside the ALTO session at the upcoming IETF meeting in Orlando. My proposal would be to do a side meeting, i.e., we meet sometimes in the evening over a drink and discuss the new drafts/use cases and how to progress ALTO. But, do not rely on my to organize such a side meeting, i.e., somebody else should take the stab in organizing this. Martin -- IETF Transport Area Director martin.stiemerling@neclab.eu NEC Laboratories Europe NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, GB Registered in England 2832014 _______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
- [alto] New ALTO use cases & the upcoming IETF mee… Martin Stiemerling
- Re: [alto] New ALTO use cases & the upcoming IETF… Reinaldo Penno (repenno)
- Re: [alto] New ALTO use cases & the upcoming IETF… Leeyoung
- Re: [alto] New ALTO use cases & the upcoming IETF… Y. Richard Yang
- Re: [alto] New ALTO use cases & the upcoming IETF… Vijay K. Gurbani
- Re: [alto] New ALTO use cases & the upcoming IETF… Y. Richard Yang
- Re: [alto] New ALTO use cases & the upcoming IETF… Martin Stiemerling
- Re: [alto] New ALTO use cases & the upcoming IETF… Leeyoung