[alto] charter extension to support i2aex proposal

Leeyoung <leeyoung@huawei.com> Tue, 05 February 2013 22:17 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 DAC3121F847B for <alto@ietfa.amsl.com>; Tue, 5 Feb 2013 14:17:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 6qtB+Uw-Czu3 for <alto@ietfa.amsl.com>; Tue, 5 Feb 2013 14:17:27 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 911BB21F846C for <alto@ietf.org>; Tue, 5 Feb 2013 14:17:26 -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 APL71865; Tue, 05 Feb 2013 22:17:25 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Feb 2013 22:16:27 +0000
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Feb 2013 22:17:25 +0000
Received: from dfweml511-mbs.china.huawei.com ([169.254.15.175]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.007; Tue, 5 Feb 2013 14:17:18 -0800
From: Leeyoung <leeyoung@huawei.com>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: charter extension to support i2aex proposal
Thread-Index: Ac4D7o3Y7bYPZh0eQ9iDno+O6XmboA==
Date: Tue, 05 Feb 2013 22:17:17 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E17290FC244@dfweml511-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-cr-hashedpuzzle: ACMP A+9z BqtJ CRv0 Cr7c DZBX Di1V FBLA FI7k GNqU Go/i HDFd Ij2r JCUG JIeT KHM1; 1; YQBsAHQAbwBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {893046D7-A32B-4AD7-9C11-64DFCE47F13E}; bABlAGUAeQBvAHUAbgBnAEAAaAB1AGEAdwBlAGkALgBjAG8AbQA=; Tue, 05 Feb 2013 22:17:15 GMT; YwBoAGEAcgB0AGUAcgAgAGUAeAB0AGUAbgBzAGkAbwBuACAAdABvACAAcwB1AHAAcABvAHIAdAAgAGkAMgBhAGUAeAAgAHAAcgBvAHAAbwBzAGEAbAA=
x-cr-puzzleid: {893046D7-A32B-4AD7-9C11-64DFCE47F13E}
x-originating-ip: [10.192.11.96]
Content-Type: multipart/alternative; boundary="_000_7AEB3D6833318045B4AE71C2C87E8E17290FC244dfweml511mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [alto] charter extension to support i2aex proposal
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, 05 Feb 2013 22:17:28 -0000

Hello ALTO WG participants,

We have uploaded a couple of drafts.

http://datatracker.ietf.org/doc/draft-lee-alto-app-net-info-exchange/

http://datatracker.ietf.org/doc/draft-lee-alto-ext-dc-resource/

This is an follow-up effort to address the issues raised in the i2aex BOF. The first draft addresses the need to extend the current ALTO cost map to include a graph type that depicts critical links and resource bottlenecks of underlying network topology. The second draft addresses how to model data center resources using ALTO model. This draft addresses what abstraction is needed in the context of data center selection problem.

In order to continue on with this work, we believe the current charter would need to be re-chartered in the spirit of i2aex.  It would be great to know if there is enough interest in this kind of work in ALTO WG.

Best Regards,
Young