Re: [cso] Coordinating CSO activity in IETF/IRTF
Leeyoung <leeyoung@huawei.com> Fri, 25 March 2011 19:24 UTC
Return-Path: <leeyoung@huawei.com>
X-Original-To: cso@core3.amsl.com
Delivered-To: cso@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60BF23A6827 for <cso@core3.amsl.com>; Fri, 25 Mar 2011 12:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.017
X-Spam-Level:
X-Spam-Status: No, score=-6.017 tagged_above=-999 required=5 tests=[AWL=-0.218, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WDuzZ1XTycEF for <cso@core3.amsl.com>; Fri, 25 Mar 2011 12:24:32 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 4CB213A682D for <cso@ietf.org>; Fri, 25 Mar 2011 12:24:32 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIM00A04ONIDE@usaga02-in.huawei.com> for cso@ietf.org; Fri, 25 Mar 2011 12:26:07 -0700 (PDT)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0LIM00F9DONIPA@usaga02-in.huawei.com> for cso@ietf.org; Fri, 25 Mar 2011 12:26:06 -0700 (PDT)
Received: from DFWEML401-HUB.china.huawei.com (10.193.5.101) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 25 Mar 2011 12:26:02 -0700
Received: from DFWEML501-MBX.china.huawei.com ([fe80::c52a:9e19:87eb:4531]) by DFWEML401-HUB.china.huawei.com ([fe80::f07f:889f:78ef:8df3%13]) with mapi id 14.01.0270.001; Fri, 25 Mar 2011 12:26:02 -0700
Date: Fri, 25 Mar 2011 19:26:00 +0000
From: Leeyoung <leeyoung@huawei.com>
X-Originating-IP: [10.47.151.130]
To: Leeyoung <leeyoung@huawei.com>, "cso@ietf.org" <cso@ietf.org>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Message-id: <7AEB3D6833318045B4AE71C2C87E8E170C5F5320@DFWEML501-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_CeYnswu66sgjpTwaNztspw)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: Coordinating CSO activity in IETF/IRTF
Thread-index: Acvov8moHFiM+yceTjqnNDQqzrr6YgCYesXg
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Subject: Re: [cso] Coordinating CSO activity in IETF/IRTF
X-BeenThere: cso@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: This list is for pre-WG technical discussion of cross stratum optimization <cso.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/cso>, <mailto:cso-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cso>
List-Post: <mailto:cso@ietf.org>
List-Help: <mailto:cso-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cso>, <mailto:cso-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2011 19:24:33 -0000
Hi, Sorry that the meeting will take place during lunch break. It looks like the room is hard to reserve in other times. Anyhow as previously announced, the coordinating meeting for CSO activity will be held from 11:30 am till 1 pm on March 29 (Tuesday) in "Rokoska" (IESG breakout room). If you have not had chance to read the proposal, the pointer is as follows: https://datatracker.ietf.org/doc/draft-lee-cross-stratum-optimization-datacenter/ See you all soon in Prague, Best regards, Young ________________________________ From: Leeyoung Sent: Tuesday, March 22, 2011 1:35 PM To: 'cso@ietf.org'; 'irtf-discuss@irtf.org' Subject: Coordinating CSO activity in IETF/IRTF Hi, For those who are interested in discussing Cross Application/Network Optimization research, please join our informal discussion meeting in Prague. The meeting will take place 11:30am-1:00pm on March 29 (Tuesday) in the IESG breakout room (Room name will be announced shortly). Thanks. Young