From xuxiaohu@huawei.com Sun Mar 11 21:05:53 2012 Return-Path: X-Original-To: dc@ietfa.amsl.com Delivered-To: dc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A2E521F857A; Sun, 11 Mar 2012 21:05:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.672 X-Spam-Level: X-Spam-Status: No, score=-4.672 tagged_above=-999 required=5 tests=[AWL=1.927, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 PyoNZIjWz22G; Sun, 11 Mar 2012 21:05:52 -0700 (PDT) Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7ACF621F8578; Sun, 11 Mar 2012 21:05:52 -0700 (PDT) Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0R0090A7DPFT@szxga05-in.huawei.com>; Mon, 12 Mar 2012 12:05:49 +0800 (CST) Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0R00A5Z7DOG4@szxga05-in.huawei.com>; Mon, 12 Mar 2012 12:05:49 +0800 (CST) Received: from szxeml212-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AHT21804; Mon, 12 Mar 2012 12:05:01 +0800 Received: from SZXEML414-HUB.china.huawei.com (10.82.67.153) by szxeml212-edg.china.huawei.com (172.24.2.181) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 12 Mar 2012 12:04:37 +0800 Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.71]) by SZXEML414-HUB.china.huawei.com ([10.82.67.153]) with mapi id 14.01.0323.003; Mon, 12 Mar 2012 12:04:56 +0800 Date: Mon, 12 Mar 2012 04:04:56 +0000 From: Xuxiaohu X-Originating-IP: [10.108.4.99] To: "l2vpn@ietf.org" Message-id: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02CD186B@szxeml525-mbx.china.huawei.com> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-language: zh-CN Content-transfer-encoding: base64 Accept-Language: zh-CN, en-US Thread-topic: New Version Notification for draft-xu-l2vpn-vpls-isis-03.txt Thread-index: AQHNAAMIHCuioWjdJ0ymjBIRI9TFDJZmCXnQ X-MS-Has-Attach: X-MS-TNEF-Correlator: X-CFilter-Loop: Reflected Cc: "dc@ietf.org" Subject: [dc] fwd: New Version Notification for draft-xu-l2vpn-vpls-isis-03.txt X-BeenThere: dc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Data Center Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 04:05:53 -0000 SGkgYWxsLA0KDQpBbiB1cGRhdGVkIHZlcnNpb24gb2YgSVMtSVMgVlBMUyAoaHR0cDovL3Rvb2xz LmlldGYub3JnL2h0bWwvZHJhZnQteHUtbDJ2cG4tdnBscy1pc2lzLTAzKSBoYXMgYmVlbiBzdWJt aXR0ZWQuIEEgbWFqb3IgY2hhbmdlIGlzIHRvIGRlc2NyaWJlIHRoZSByZXF1aXJlbWVudHMgb2Yg Y2xvdWQgZGF0YSBjZW50ZXIgbmV0d29ya3MgYW5kIHRoZSBtb3RpdmF0aW9ucyBmb3IgSVMtSVMg VlBMUy4NCg0KQW55IGNvbW1lbnRzIGFuZCBzdWdnZXN0aW9ucyBhcmUgYXBwcmVjaWF0ZWQuDQoN CkJlc3QgcmVnYXJkcywNClhpYW9odQ0KDQo+IC0tLS0t6YKu5Lu25Y6f5Lu2LS0tLS0NCj4g5Y+R 5Lu25Lq6OiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNA aWV0Zi5vcmddDQo+IOWPkemAgeaXtumXtDogMjAxMuW5tDPmnIgxMuaXpSAxMTo0OA0KPiDmlLbk u7bkuro6IFh1eGlhb2h1DQo+IOaKhOmAgTogaHNoYWhAY2llbmEuY29tDQo+IOS4u+mimDogTmV3 IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC14dS1sMnZwbi12cGxzLWlzaXMtMDMudHh0 DQo+IA0KPiBBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQteHUtbDJ2cG4tdnBscy1pc2lzLTAz LnR4dCBoYXMgYmVlbiBzdWNjZXNzZnVsbHkNCj4gc3VibWl0dGVkIGJ5IFhpYW9odSBYdSBhbmQg cG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQo+IA0KPiBGaWxlbmFtZToJIGRyYWZ0LXh1 LWwydnBuLXZwbHMtaXNpcw0KPiBSZXZpc2lvbjoJIDAzDQo+IFRpdGxlOgkJIFZpcnR1YWwgUHJp dmF0ZSBMQU4gU2VydmljZSAoVlBMUykgVXNpbmcgSVMtSVMNCj4gQ3JlYXRpb24gZGF0ZToJIDIw MTItMDMtMDkNCj4gV0cgSUQ6CQkgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQo+IE51bWJlciBvZiBw YWdlczogMTENCj4gDQo+IEFic3RyYWN0Og0KPiAgICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBh IGxpZ2h0LXdlaWdodCBWaXJ0dWFsIFByaXZhdGUgTEFOIFNlcnZpY2UNCj4gICAgKFZQTFMpLCBy ZWZlcnJlZCB0byBhcyBJUy1JUyBWUExTLCB3aGljaCB1c2VzIElTLUlTIGZvciBhdXRvLQ0KPiAg ICBkaXNjb3ZlcnkgYW5kIHNpZ25hbGluZy4gSVMtSVMgVlBMUyBpcyBpbnRlbmRlZCB0byBiZSB1 c2VkIGFzIGENCj4gICAgc2NhbGFibGUgY2xvdWQgZGF0YSBjZW50ZXIgbmV0d29yayBzb2x1dGlv bi4NCj4gDQo+IA0KPiANCj4gDQo+IA0KPiBUaGUgSUVURiBTZWNyZXRhcmlhdA0K From xuxiaohu@huawei.com Mon Mar 12 18:33:48 2012 Return-Path: X-Original-To: dc@ietfa.amsl.com Delivered-To: dc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F15321F877B; Mon, 12 Mar 2012 18:33:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.746 X-Spam-Level: X-Spam-Status: No, score=-4.746 tagged_above=-999 required=5 tests=[AWL=1.853, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 HhGwtoCzLqnS; Mon, 12 Mar 2012 18:33:47 -0700 (PDT) Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 1E59C21F8735; Mon, 12 Mar 2012 18:33:47 -0700 (PDT) Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0S00MPJUWT30@szxga05-in.huawei.com>; Tue, 13 Mar 2012 09:31:42 +0800 (CST) Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0S003YTUWTZG@szxga05-in.huawei.com>; Tue, 13 Mar 2012 09:31:41 +0800 (CST) Received: from szxeml213-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AHK35187; Tue, 13 Mar 2012 09:31:40 +0800 Received: from SZXEML438-HUB.china.huawei.com (10.72.61.73) by szxeml213-edg.china.huawei.com (172.24.2.30) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Mar 2012 09:30:47 +0800 Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.71]) by szxeml438-hub.china.huawei.com ([10.72.61.73]) with mapi id 14.01.0323.003; Tue, 13 Mar 2012 09:31:34 +0800 Date: Tue, 13 Mar 2012 01:31:32 +0000 From: Xuxiaohu X-Originating-IP: [10.108.4.99] To: "dc@ietf.org" , "opsawg@ietf.org" Message-id: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02CD2D33@szxeml525-mbx.china.huawei.com> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-language: zh-CN Content-transfer-encoding: base64 Accept-Language: zh-CN, en-US Thread-topic: New Version Notification for draft-xu-virtual-subnet-07.txt Thread-index: AQHNADYOf/fuhjGgkEqSAHzLif7gnJZnaoOQ X-MS-Has-Attach: X-MS-TNEF-Correlator: X-CFilter-Loop: Reflected Cc: Susan Hares Subject: [dc] fwd: New Version Notification for draft-xu-virtual-subnet-07.txt X-BeenThere: dc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Data Center Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 01:33:48 -0000 SGkgYWxsLA0KDQpBbiB1cGRhdGVkIHZlcnNpb24gb2YgVmlydHVhbCBTdWJuZXQgKGh0dHA6Ly90 b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXh1LXZpcnR1YWwtc3VibmV0LTA3KSB3aGljaCBpcyBh IGhvc3Qgcm91dGUgYmFzZWQgZGF0YSBjZW50ZXIgaW50ZXJjb25uZWN0IHNvbHV0aW9uLCBoYXMg YmVlbiBzdWJtaXR0ZWQuIA0KDQpNYWpvciBjaGFuZ2VzIGluY2x1ZGU6IA0KMSkgYWRkIGEgZGV0 YWlsZWQgZGVzY3JpcHRpb24gb2YgY2xvdWQgZGF0YSBjZW50ZXIgaW50ZXJjb25uZWN0IHJlcXVp cmVtZW50cy4gDQoyKSBhZGQgYSBzZWN0aW9uIGRlc2NyaWJpbmcgaG93IHRvIHNjYWxlIHRoZSBG SUJzIGFuZCBSSUJzIG9mIFBFIHJvdXRlcnMgYW5kIGhvdyB0byBzY2FsZSB0aGUgTUFDIHRhYmxl cyBvZiBkYXRhIGNlbnRlciBzd2l0Y2hlcy4NCjMpIGFkZCBhIHNlY3Rpb24gZGVzY3JpYmluZyBo b3cgdG8gc2NhbGUgdGhlIEFSUCB0YWJsZXMgb2YgZGF0YSBjZW50ZXIgZ2F0ZXdheXMuDQo0KSBh ZGQgYSBuZXcgY28tYXV0aG9yLiANCjUpIGNoYW5nZSBpdHMgY2F0ZWdvcnkgZnJvbSBzdGFuZGFy ZCB0cmFjayB0byBpbmZvcm1hdGlvbmFsLg0KDQpBbnkgY29tbWVudHMgYW5kIHN1Z2dlc3Rpb25z IGFyZSB3ZWxjb21lLg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiAtLS0tLemCruS7tuWO n+S7ti0tLS0tDQo+IOWPkeS7tuS6ujogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86 aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXQ0KPiDlj5HpgIHml7bpl7Q6IDIwMTLlubQz5pyIMTLm l6UgMTc6NTQNCj4g5pS25Lu25Lq6OiBYdXhpYW9odQ0KPiDmioTpgIE6IFN1c2FuIEhhcmVzDQo+ IOS4u+mimDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC14dS12aXJ0dWFsLXN1 Ym5ldC0wNy50eHQNCj4gDQo+IEEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC14dS12aXJ0dWFs LXN1Ym5ldC0wNy50eHQgaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5DQo+IHN1Ym1pdHRlZCBieSBYaWFv aHUgWHUgYW5kIHBvc3RlZCB0byB0aGUgSUVURiByZXBvc2l0b3J5Lg0KPiANCj4gRmlsZW5hbWU6 CSBkcmFmdC14dS12aXJ0dWFsLXN1Ym5ldA0KPiBSZXZpc2lvbjoJIDA3DQo+IFRpdGxlOgkJIFZp cnR1YWwgU3VibmV0OiBBIEhvc3QgUm91dGUgYmFzZWQgU3VibmV0IEV4dGVuc2lvbiBTb2x1dGlv bg0KPiBDcmVhdGlvbiBkYXRlOgkgMjAxMi0wMy0xMg0KPiBXRyBJRDoJCSBJbmRpdmlkdWFsIFN1 Ym1pc3Npb24NCj4gTnVtYmVyIG9mIHBhZ2VzOiAxMw0KPiANCj4gQWJzdHJhY3Q6DQo+ICAgIFRo aXMgZG9jdW1lbnQgZGVzY3JpYmVzIGEgaG9zdCByb3V0ZSBiYXNlZCBzdWJuZXQgZXh0ZW5zaW9u IHNvbHV0aW9uDQo+ICAgIHJlZmVycmVkIHRvIGFzIFZpcnR1YWwgU3VibmV0LCB3aGljaCBtYWlu bHkgcmV1c2VzIGV4aXN0aW5nIEJHUC9NUExTDQo+ICAgIElQIFZQTiBbUkZDNDM2NF0gYW5kIEFS UCBwcm94eSBbUkZDOTI1XVtSRkMxMDI3XSB0ZWNobm9sb2dpZXMuDQo+ICAgIFZpcnR1YWwgU3Vi bmV0IHByb3ZpZGVzIGEgc2NhbGFibGUgYXBwcm9hY2ggZm9yIGludGVyY29ubmVjdGluZw0KPiAg ICBnZW9ncmFwaGljYWxseSBkaXNwZXJzZWQgY2xvdWQgZGF0YSBjZW50ZXJzLg0KPiANCj4gDQo+ IA0KPiANCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo= From xuxiaohu@huawei.com Mon Mar 12 18:56:39 2012 Return-Path: X-Original-To: dc@ietfa.amsl.com Delivered-To: dc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F1321F887B; Mon, 12 Mar 2012 18:56:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.815 X-Spam-Level: X-Spam-Status: No, score=-4.815 tagged_above=-999 required=5 tests=[AWL=1.784, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 GSm+8BoUqVnK; Mon, 12 Mar 2012 18:56:38 -0700 (PDT) Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 6C48621F8861; Mon, 12 Mar 2012 18:56:34 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0S00G2KVZOQ1@szxga04-in.huawei.com>; Tue, 13 Mar 2012 09:55:01 +0800 (CST) Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0S00FBMVZLXO@szxga04-in.huawei.com>; Tue, 13 Mar 2012 09:55:00 +0800 (CST) Received: from szxeml212-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AHU10620; Tue, 13 Mar 2012 09:55:00 +0800 Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by szxeml212-edg.china.huawei.com (172.24.2.181) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Mar 2012 09:54:34 +0800 Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.71]) by szxeml418-hub.china.huawei.com ([10.82.67.157]) with mapi id 14.01.0323.003; Tue, 13 Mar 2012 09:54:58 +0800 Date: Tue, 13 Mar 2012 01:54:57 +0000 From: Xuxiaohu X-Originating-IP: [10.108.4.99] To: "dc@ietf.org" , "opsawg@ietf.org" Message-id: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02CD2D61@szxeml525-mbx.china.huawei.com> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-language: zh-CN Content-transfer-encoding: base64 Accept-Language: zh-CN, en-US Thread-topic: time slot request//re: New Version Notification for draft-xu-virtual-subnet-07.txt Thread-index: AQHNALxLwtGCZ7C4GkqECzkHaly51A== X-MS-Has-Attach: X-MS-TNEF-Correlator: X-CFilter-Loop: Reflected Cc: Susan Hares Subject: [dc] time slot request//re: New Version Notification for draft-xu-virtual-subnet-07.txt X-BeenThere: dc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Data Center Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 01:56:39 -0000 SGkgT1BTIFdHIGNvLWNoYWlycyBhbmQgQXJlYSBkaXJlY3RvcnMsDQoNCkkgd291bGQgbGlrZSB0 byByZXF1ZXN0IGEgMTUtbWluIHRpbWVzbG90IGZvciBwcmVzZW50aW5nIHRoaXMgZHJhZnQgb24g dGhlIE9QUyBXRyBhbmQgQXJlYSBqb2ludCBzZXNzaW9uLg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFv aHUNCg0KPiAtLS0tLemCruS7tuWOn+S7ti0tLS0tDQo+IOWPkeS7tuS6ujogWHV4aWFvaHUNCj4g 5Y+R6YCB5pe26Ze0OiAyMDEy5bm0M+aciDEz5pelIDk6MzENCj4g5pS25Lu25Lq6OiBkY0BpZXRm Lm9yZzsgJ29wc2F3Z0BpZXRmLm9yZycNCj4g5oqE6YCBOiAnU3VzYW4gSGFyZXMnDQo+IOS4u+mi mDogZndkOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LXh1LXZpcnR1YWwtc3Vi bmV0LTA3LnR4dA0KPiANCj4gSGkgYWxsLA0KPiANCj4gQW4gdXBkYXRlZCB2ZXJzaW9uIG9mIFZp cnR1YWwgU3VibmV0DQo+IChodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC14dS12aXJ0 dWFsLXN1Ym5ldC0wNykgd2hpY2ggaXMgYSBob3N0IHJvdXRlDQo+IGJhc2VkIGRhdGEgY2VudGVy IGludGVyY29ubmVjdCBzb2x1dGlvbiwgaGFzIGJlZW4gc3VibWl0dGVkLg0KPiANCj4gTWFqb3Ig Y2hhbmdlcyBpbmNsdWRlOg0KPiAxKSBhZGQgYSBkZXRhaWxlZCBkZXNjcmlwdGlvbiBvZiBjbG91 ZCBkYXRhIGNlbnRlciBpbnRlcmNvbm5lY3QgcmVxdWlyZW1lbnRzLg0KPiAyKSBhZGQgYSBzZWN0 aW9uIGRlc2NyaWJpbmcgaG93IHRvIHNjYWxlIHRoZSBGSUJzIGFuZCBSSUJzIG9mIFBFIHJvdXRl cnMgYW5kDQo+IGhvdyB0byBzY2FsZSB0aGUgTUFDIHRhYmxlcyBvZiBkYXRhIGNlbnRlciBzd2l0 Y2hlcy4NCj4gMykgYWRkIGEgc2VjdGlvbiBkZXNjcmliaW5nIGhvdyB0byBzY2FsZSB0aGUgQVJQ IHRhYmxlcyBvZiBkYXRhIGNlbnRlcg0KPiBnYXRld2F5cy4NCj4gNCkgYWRkIGEgbmV3IGNvLWF1 dGhvci4NCj4gNSkgY2hhbmdlIGl0cyBjYXRlZ29yeSBmcm9tIHN0YW5kYXJkIHRyYWNrIHRvIGlu Zm9ybWF0aW9uYWwuDQo+IA0KPiBBbnkgY29tbWVudHMgYW5kIHN1Z2dlc3Rpb25zIGFyZSB3ZWxj b21lLg0KPiANCj4gQmVzdCByZWdhcmRzLA0KPiBYaWFvaHUNCj4gDQo+ID4gLS0tLS3pgq7ku7bl jp/ku7YtLS0tLQ0KPiA+IOWPkeS7tuS6ujogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWls dG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXQ0KPiA+IOWPkemAgeaXtumXtDogMjAxMuW5tDPm nIgxMuaXpSAxNzo1NA0KPiA+IOaUtuS7tuS6ujogWHV4aWFvaHUNCj4gPiDmioTpgIE6IFN1c2Fu IEhhcmVzDQo+ID4g5Li76aKYOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LXh1 LXZpcnR1YWwtc3VibmV0LTA3LnR4dA0KPiA+DQo+ID4gQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRy YWZ0LXh1LXZpcnR1YWwtc3VibmV0LTA3LnR4dCBoYXMgYmVlbiBzdWNjZXNzZnVsbHkNCj4gPiBz dWJtaXR0ZWQgYnkgWGlhb2h1IFh1IGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4N Cj4gPg0KPiA+IEZpbGVuYW1lOgkgZHJhZnQteHUtdmlydHVhbC1zdWJuZXQNCj4gPiBSZXZpc2lv bjoJIDA3DQo+ID4gVGl0bGU6CQkgVmlydHVhbCBTdWJuZXQ6IEEgSG9zdCBSb3V0ZSBiYXNlZCBT dWJuZXQgRXh0ZW5zaW9uIFNvbHV0aW9uDQo+ID4gQ3JlYXRpb24gZGF0ZToJIDIwMTItMDMtMTIN Cj4gPiBXRyBJRDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4gPiBOdW1iZXIgb2YgcGFnZXM6 IDEzDQo+ID4NCj4gPiBBYnN0cmFjdDoNCj4gPiAgICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBh IGhvc3Qgcm91dGUgYmFzZWQgc3VibmV0IGV4dGVuc2lvbiBzb2x1dGlvbg0KPiA+ICAgIHJlZmVy cmVkIHRvIGFzIFZpcnR1YWwgU3VibmV0LCB3aGljaCBtYWlubHkgcmV1c2VzIGV4aXN0aW5nIEJH UC9NUExTDQo+ID4gICAgSVAgVlBOIFtSRkM0MzY0XSBhbmQgQVJQIHByb3h5IFtSRkM5MjVdW1JG QzEwMjddIHRlY2hub2xvZ2llcy4NCj4gPiAgICBWaXJ0dWFsIFN1Ym5ldCBwcm92aWRlcyBhIHNj YWxhYmxlIGFwcHJvYWNoIGZvciBpbnRlcmNvbm5lY3RpbmcNCj4gPiAgICBnZW9ncmFwaGljYWxs eSBkaXNwZXJzZWQgY2xvdWQgZGF0YSBjZW50ZXJzLg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4N Cj4gPiBUaGUgSUVURiBTZWNyZXRhcmlhdA0K From spencer@wonderhamster.org Wed Mar 21 10:05:22 2012 Return-Path: X-Original-To: dc@ietfa.amsl.com Delivered-To: dc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3BF121F85A4; Wed, 21 Mar 2012 10:05:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.932 X-Spam-Level: X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 lzd0-eBg2F1n; Wed, 21 Mar 2012 10:05:22 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 1285A21F84F7; Wed, 21 Mar 2012 10:05:22 -0700 (PDT) Received: from [192.168.2.9] (cpe-76-182-255-76.tx.res.rr.com [76.182.255.76]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MGis5-1S6KVm1sxN-00EE8B; Wed, 21 Mar 2012 13:05:21 -0400 Message-ID: <4F6A0A41.3050006@wonderhamster.org> Date: Wed, 21 Mar 2012 12:05:05 -0500 From: Spencer Dawkins User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: apps-discuss@ietf.org, opsawg@ietf.org, tsvwg@ietf.org, cdni@ietf.org, dc@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:37kwmDyh1PGtEv1+GuK5JGGumWHU/GEI1BmdmoUug8c hWnMw72RwkhAxsiU6NG7N79qlJQ2XV6Z5awI9Cd48xzXeg5xFU 776j0JR0CGgz/Me5v58EWM1FwIxl3WeJpt1rC5lVJTGIRDApNj Y5EGXhxNayCTqYWx4P27UPyH5xJ2sNZ6axI84XY2/21DUaEibd X2jyXDdNbpDdekwqfzSMsiWaa0wMb7Wy87HIiScZG9r+c85VYG tfT5MBRwtPWjQlRfl1m4rnht0aaWMtrR59lQpOw2/QpT5+wlQu epn5Vg7T+8MSL4TRS9TDCWCg16mEyA/Z8zH6ksI23CL/SnqZNv P5TKeqNw8EBjZjP2pah70i10iOL6ag912CaluRy5Y Subject: [dc] Announcing the i2aex BoF X-BeenThere: dc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Data Center Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2012 17:05:22 -0000 Hi all, David Harrington asked me to act as BoF Shepherd for the Infrastructure-to-application Information Exposure (i2aex) BoF, and I wanted to make sure that a broad community of interest was aware of this BoF, especially since the BoF is scheduled for Monday, Afternoon Session 1, at 1300 PM. Preliminary discussion has been going on for some time now on the altoext@ietf.org mailing list, mainly among people in some way involved in the standardization the ALTO protocol. In order to have a conversation that's as productive as possible in Paris, we would really like to invite people who are involved on different sides of the same problem to bring their perspective as well. Here's a short description, with the usual pointers. Follow-ups to altoext@ietf.org, please. The goal of the (non-WG-forming) BoF is to investigate infrastructure- to-application information exposure and communications requirements in fully controlled (e.g., data centers) or partially controlled environments (e.g. CDN). Existing mechanisms such as SNMP, IGP, BGP and other protocols that monitor and manage infrastructure may reveal much if not all of the possibly required information, but are typically only accessible to the operators of the network infrastructure. CDNs and data center applications have some requirements to operate over the Internet, possibly between administrative domains. On the other hand, the ALTO protocol was initially designed to address peer-to-peer application requirements, but was designed to be extensible and could be quite easily adapted to export the pieces of information that CDN and data center applications would benefit from. The BoF will thus primarily seek an answer to the following questions: + do CDN and data center applications require (or benefit in a significant way from) accessing to information that cannot be made available through existing mechanisms in a practical way? + is an extension to the ALTO protocol (or to any other protocol) a viable way to address such requirements? Additional information about the topic is available on the BoF wiki entry: http://trac.tools.ietf.org/bof/trac/#Transport The provisional agenda for the meeting is online at: http://www.ietf.org/proceedings/83/agenda/agenda-83-i2aex.txt From vumip1@gmail.com Wed Mar 21 10:50:32 2012 Return-Path: X-Original-To: dc@ietfa.amsl.com Delivered-To: dc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C90421E808C; Wed, 21 Mar 2012 10:50:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.492 X-Spam-Level: X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=-0.560, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666] 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 Wd0wZ7JN4zPv; Wed, 21 Mar 2012 10:50:31 -0700 (PDT) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 381DB21E8040; Wed, 21 Mar 2012 10:50:31 -0700 (PDT) Received: by yenm5 with SMTP id m5so1308124yen.31 for ; Wed, 21 Mar 2012 10:50:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zC0cm5QYiRjo5405z/iXCy1JqbVw+rHCtRUW70A0pPs=; b=NP27W+seIGqA/JW8UnZjgNF7vOZqgqPG14AV1VMOkwJNGyLAd/ZqB+4FqhiGkRyY4s aOIeEkHFf1l2GZq6iOhKxR1r8yAoLez+rpVVtfDSZU2D+uICDGnDRah5AlIwRx25Rjkd qwjgTH5llq7Ck5jbhHKg4xlNRpXG2yNAaWMdRnvj3vI5r5ESAZCqBxN5Ks6/VMmTo1yG 36BoxmMVlnNOeK/7oAgGV6uauoWZyYA/gfbTTq2u9lR6Uyizye0S1RLbZVedXLo+T+9G jRTYP8qX1ROLmY/r1jpHpIMkOi07DC0n3DvoRSvqoaYQhows1SrKqq/wY+0Jds0HQs1U JBhw== MIME-Version: 1.0 Received: by 10.182.54.114 with SMTP id i18mr5776882obp.49.1332352230691; Wed, 21 Mar 2012 10:50:30 -0700 (PDT) Received: by 10.182.12.234 with HTTP; Wed, 21 Mar 2012 10:50:30 -0700 (PDT) In-Reply-To: <4F6A0A41.3050006@wonderhamster.org> References: <4F6A0A41.3050006@wonderhamster.org> Date: Wed, 21 Mar 2012 13:50:30 -0400 Message-ID: From: Bhumip Khasnabish To: Spencer Dawkins Content-Type: multipart/alternative; boundary=14dae93a122f6d130b04bbc46d8a Cc: dc@ietf.org, opsawg@ietf.org, cdni@ietf.org, tsvwg@ietf.org, apps-discuss@ietf.org Subject: Re: [dc] Announcing the i2aex BoF X-BeenThere: dc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Data Center Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2012 17:50:32 -0000 --14dae93a122f6d130b04bbc46d8a Content-Type: text/plain; charset=ISO-8859-1 Hi Spencer, Is this similar to Cloud Infrastructure Management Interface (CIMI) Model and REST Interface over HTTP An Interface for Managing Cloud Infrastructure( http://dmtf.org/standards/cloud)? What is the trigger for this?! Thanks for clarifying. Best. Bhumip On Wed, Mar 21, 2012 at 1:05 PM, Spencer Dawkins wrote: > Hi all, > > David Harrington asked me to act as BoF Shepherd for the > Infrastructure-to-application Information Exposure (i2aex) BoF, and I > wanted to make sure that a broad community of interest was aware of this > BoF, especially since the BoF is scheduled for Monday, Afternoon Session 1, > at 1300 PM. > > Preliminary discussion has been going on for some time now on the > altoext@ietf.org mailing list, mainly among people in some way involved > in the standardization the ALTO protocol. In order to have a conversation > that's as productive as possible in Paris, we would really like to invite > people who are involved on different sides of the same problem to bring > their perspective as well. > > Here's a short description, with the usual pointers. Follow-ups to > altoext@ietf.org, please. > > The goal of the (non-WG-forming) BoF is to investigate infrastructure- > to-application information exposure and communications requirements in > fully controlled (e.g., data centers) or partially controlled > environments (e.g. CDN). Existing mechanisms such as SNMP, IGP, BGP and > other protocols that monitor and manage infrastructure may reveal much > if not all of the possibly required information, but are typically only > accessible to the operators of the network infrastructure. CDNs and data > center applications have some requirements to operate over the Internet, > possibly between administrative domains. On the other hand, the ALTO > protocol was initially designed to address peer-to-peer application > requirements, but was designed to be extensible and could be quite > easily adapted to export the pieces of information that CDN and data > center applications would benefit from. > > The BoF will thus primarily seek an answer to the following questions: > > + do CDN and data center applications require (or benefit in a > significant way from) accessing to information that cannot be made > available through existing mechanisms in a practical way? > > + is an extension to the ALTO protocol (or to any other protocol) a > viable way to address such requirements? > > Additional information about the topic is available on the BoF wiki > entry: http://trac.tools.ietf.org/**bof/trac/#Transport > > The provisional agenda for the meeting is online at: > http://www.ietf.org/**proceedings/83/agenda/agenda-**83-i2aex.txt > ______________________________**_________________ > dc mailing list > dc@ietf.org > https://www.ietf.org/mailman/**listinfo/dc > --14dae93a122f6d130b04bbc46d8a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Spencer,
=A0
Is this similar to Cloud Infrastructure Management Interface (CIMI) Model and REST Interface= over HTTP An Interface for Managing Cloud In= frastructure (http://dmtf.org/standards/cloud)?
=A0
What is the trigger for this?!
=A0
Thanks for clarifying.
=A0
Best.
=A0
Bhumip
=A0

=A0



On Wed, Mar 21, 2012 at 1:05 PM, Spencer Dawkins= <spencer= @wonderhamster.org> wrote:
Hi all,

David Harrington asked= me to act as BoF Shepherd for the Infrastructure-to-application Informatio= n Exposure (i2aex) BoF, and I wanted to make sure that a broad community of= interest was aware of this BoF, especially since the BoF is scheduled for = Monday, Afternoon Session 1, at 1300 PM.

Preliminary discussion has been going on for some time now on the altoext@ietf.org maili= ng list, mainly among people in some way involved in the standardization th= e ALTO protocol. In order to have a conversation that's as productive a= s possible in Paris, we would really like to invite people who are involved= on different sides of the same problem to bring their perspective as well.=

Here's a short description, with the usual pointers. Follow-ups to = altoext@ietf.org,= please.

The goal of the (non-WG-forming) BoF is to investigate infr= astructure-
to-application information exposure and communications requirements in
f= ully controlled (e.g., data centers) or partially controlled
environment= s (e.g. CDN). Existing mechanisms such as SNMP, IGP, BGP and
other proto= cols that monitor and manage infrastructure may reveal much
if not all of the possibly required information, but are typically only
= accessible to the operators of the network infrastructure. CDNs and datacenter applications have some requirements to operate over the Internet, possibly between administrative domains. On the other hand, the ALTO
pro= tocol was initially designed to address peer-to-peer application
require= ments, but was designed to be extensible and could be quite
easily adapt= ed to export the pieces of information that CDN and data
center applications would benefit from.

The BoF will thus primarily = seek an answer to the following questions:

=A0+ do CDN and data cent= er applications require (or benefit in a
=A0 =A0significant way from) ac= cessing to information that cannot be made
=A0 =A0available through existing mechanisms in a practical way?

=A0= + is an extension to the ALTO protocol (or to any other protocol) a
=A0 = =A0viable way to address such requirements?

Additional information a= bout the topic is available on the BoF wiki
entry: http://trac.tools.ietf.org/bof/trac/#Transport

T= he provisional agenda for the meeting is online at:
htt= p://www.ietf.org/proceedings/83/agenda/agenda-83-i2aex.txt
_______________________________________________
dc mailing listdc@ietf.org
https://w= ww.ietf.org/mailman/listinfo/dc


=A0 --14dae93a122f6d130b04bbc46d8a-- From ietfdbh@comcast.net Thu Mar 22 09:51:07 2012 Return-Path: X-Original-To: dc@ietfa.amsl.com Delivered-To: dc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 066CA21F86A0 for ; Thu, 22 Mar 2012 09:51:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.019 X-Spam-Level: X-Spam-Status: No, score=-102.019 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, J_CHICKENPOX_62=0.6, USER_IN_WHITELIST=-100] 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 bm8IRjg+JyfB for ; Thu, 22 Mar 2012 09:50:55 -0700 (PDT) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by ietfa.amsl.com (Postfix) with ESMTP id 414F621F866E for ; Thu, 22 Mar 2012 09:50:55 -0700 (PDT) Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta09.westchester.pa.mail.comcast.net with comcast id ogow1i0061HzFnQ59gqvqj; Thu, 22 Mar 2012 16:50:55 +0000 Received: from [192.168.1.33] ([71.233.85.150]) by omta14.westchester.pa.mail.comcast.net with comcast id ogqd1i0073Ecudz3agqlo1; Thu, 22 Mar 2012 16:50:55 +0000 User-Agent: Microsoft-MacOutlook/14.14.0.111121 Date: Thu, 22 Mar 2012 12:50:34 -0400 From: David Harrington To: Bhumip Khasnabish , Spencer Dawkins Message-ID: Thread-Topic: [dc] Announcing the i2aex BoF In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Cc: apps-discuss@ietf.org, opsawg@ietf.org, cdni@ietf.org, Tsvwg , dc@ietf.org Subject: Re: [dc] Announcing the i2aex BoF X-BeenThere: dc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Data Center Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 16:51:07 -0000 Hi Bhumip, Your input would be more helpful if you did the research to answer the question your self and prepared a detailed analysis for the community to review (I.e., write a draft). Is this similar to dmtf's CIMI? I suggest you read the documents on the agenda and read the CIMI spec and compare them to see if they are or are not similar. My experience has been that DMTF works top-down - they tend to develop and abstract architecture first and then encourage implementers to develop detailed specs that fit within the architecture. That sometimes leads to abstract systems that implementers choose not to implement, because the architecture is too all-inclusive, or implementers cherry-pick the features, with the result that different implementations choose different feature sets and then do not interoperate. The IETF uses a bottom-up model; we prefer detailed proposals based on actual experience in the field, and developing highly focused specifications with a small number of mandatory-to-implement features, to ensure cross-vendor interoperation. The result can be messy as compared to a nice top-down architecture, but the IETF has been very successful using this approach, and the Internet community seems to want to keep using this approach. Is the REST interface similar to interfaces being proposed in i2aex? Have you done a feature comparison between the i2aex proposals and the DMTF proposals? I have a concern that the DMTF REST interface might be based on a DMTF abstract architectural model that may or may not actually be used by operators in real-world deployments. A major part of this BOF is to get feedback from real-world operators about what bottom=up technologies they actually use in real-world deployments to mitigate the problems of CDN and DC optimization, and whether operators would benefit from IETF standardization of these bottom-up optimization approaches. Ultimately, the i2aex BOF is about understanding whether IETF should develop extensions to Internet protocols to meet CDN and DC optimization needs when running over the Internet. It is not about developing an abstract all-encompassing architecture for managing clouds. So I have doubts about how much actual overlap exists between the DMTF proposals and the i2aex proposals. I do encourage people involved in this effort to consider whether there is overlap, but they should avoid being sidetracked into some mission that is not an IETF or i2aex BOF mission. My $.04 as Responsible AD for this BOF. -- David Harrington Director, Transport Area Internet Engineering Task Force (IETF) Ietfdbh@comcast.net +1-603-828-1401 On 3/21/12 1:50 PM, "Bhumip Khasnabish" wrote: >Hi Spencer, > >Is this similar to Cloud Infrastructure Management Interface (CIMI) Model >and REST Interface over HTTP An Interface for Managing Cloud >Infrastructure (http://dmtf.org/standards/cloud)? > >What is the trigger for this?! > >Thanks for clarifying. > >Best. > >Bhumip > > > > >On Wed, Mar 21, 2012 at 1:05 PM, Spencer Dawkins > wrote: > >Hi all, > >David Harrington asked me to act as BoF Shepherd for the >Infrastructure-to-application Information Exposure (i2aex) BoF, and I >wanted to make sure that a broad community of interest was aware of this >BoF, especially since the BoF is scheduled for Monday, Afternoon Session >1, at 1300 PM. > >Preliminary discussion has been going on for some time now on the >altoext@ietf.org mailing list, mainly among people in some way involved >in the standardization the ALTO protocol. In order to have a conversation >that's as productive as possible in Paris, we would really like to invite >people who are involved on different sides of the same problem to bring >their perspective as well. > >Here's a short description, with the usual pointers. Follow-ups to >altoext@ietf.org, please. > >The goal of the (non-WG-forming) BoF is to investigate infrastructure- >to-application information exposure and communications requirements in >fully controlled (e.g., data centers) or partially controlled >environments (e.g. CDN). Existing mechanisms such as SNMP, IGP, BGP and >other protocols that monitor and manage infrastructure may reveal much >if not all of the possibly required information, but are typically only >accessible to the operators of the network infrastructure. CDNs and data >center applications have some requirements to operate over the Internet, >possibly between administrative domains. On the other hand, the ALTO >protocol was initially designed to address peer-to-peer application >requirements, but was designed to be extensible and could be quite >easily adapted to export the pieces of information that CDN and data >center applications would benefit from. > >The BoF will thus primarily seek an answer to the following questions: > > + do CDN and data center applications require (or benefit in a > significant way from) accessing to information that cannot be made > available through existing mechanisms in a practical way? > > + is an extension to the ALTO protocol (or to any other protocol) a > viable way to address such requirements? > >Additional information about the topic is available on the BoF wiki >entry: http://trac.tools.ietf.org/bof/trac/#Transport > >The provisional agenda for the meeting is online at: >http://www.ietf.org/proceedings/83/agenda/agenda-83-i2aex.txt >_______________________________________________ >dc mailing list >dc@ietf.org >https://www.ietf.org/mailman/listinfo/dc > > > > > > From linda.dunbar@huawei.com Thu Mar 22 12:43:09 2012 Return-Path: X-Original-To: dc@ietfa.amsl.com Delivered-To: dc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5638621E8028; Thu, 22 Mar 2012 12:43:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.553 X-Spam-Level: X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599] 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 pM24XEoCbLuy; Thu, 22 Mar 2012 12:43:08 -0700 (PDT) Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id EBA3121F85D6; Thu, 22 Mar 2012 12:43:07 -0700 (PDT) Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AEP68367; Thu, 22 Mar 2012 15:43:06 -0400 (EDT) Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 22 Mar 2012 12:41:57 -0700 Received: from DFWEML505-MBX.china.huawei.com ([10.124.31.100]) by dfweml404-hub.china.huawei.com ([10.193.5.203]) with mapi id 14.01.0323.003; Thu, 22 Mar 2012 12:42:00 -0700 From: Linda Dunbar To: Spencer Dawkins , "apps-discuss@ietf.org" , "opsawg@ietf.org" , "tsvwg@ietf.org" , "cdni@ietf.org" , "dc@ietf.org" Thread-Topic: [dc] Announcing the i2aex BoF Thread-Index: AQHNB4Tsxr8YheQTEUmLhaS9a9PrIpZ2th0g Date: Thu, 22 Mar 2012 19:42:00 +0000 Message-ID: <4A95BA014132FF49AE685FAB4B9F17F632E4F713@dfweml505-mbx> References: <4F6A0A41.3050006@wonderhamster.org> In-Reply-To: <4F6A0A41.3050006@wonderhamster.org> Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.47.144.61] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: Re: [dc] Announcing the i2aex BoF X-BeenThere: dc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Data Center Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 19:43:09 -0000 Are there specific applications in mind for the Intra-structure to expose t= o?=20 Linda > -----Original Message----- > From: dc-bounces@ietf.org [mailto:dc-bounces@ietf.org] On Behalf Of > Spencer Dawkins > Sent: Wednesday, March 21, 2012 12:05 PM > To: apps-discuss@ietf.org; opsawg@ietf.org; tsvwg@ietf.org; > cdni@ietf.org; dc@ietf.org > Subject: [dc] Announcing the i2aex BoF >=20 > Hi all, >=20 > David Harrington asked me to act as BoF Shepherd for the > Infrastructure-to-application Information Exposure (i2aex) BoF, and I > wanted to make sure that a broad community of interest was aware of > this > BoF, especially since the BoF is scheduled for Monday, Afternoon > Session > 1, at 1300 PM. >=20 > Preliminary discussion has been going on for some time now on the > altoext@ietf.org mailing list, mainly among people in some way involved > in the standardization the ALTO protocol. In order to have a > conversation that's as productive as possible in Paris, we would really > like to invite people who are involved on different sides of the same > problem to bring their perspective as well. >=20 > Here's a short description, with the usual pointers. Follow-ups to > altoext@ietf.org, please. >=20 > The goal of the (non-WG-forming) BoF is to investigate infrastructure- > to-application information exposure and communications requirements in > fully controlled (e.g., data centers) or partially controlled > environments (e.g. CDN). Existing mechanisms such as SNMP, IGP, BGP and > other protocols that monitor and manage infrastructure may reveal much > if not all of the possibly required information, but are typically only > accessible to the operators of the network infrastructure. CDNs and > data > center applications have some requirements to operate over the Internet, > possibly between administrative domains. On the other hand, the ALTO > protocol was initially designed to address peer-to-peer application > requirements, but was designed to be extensible and could be quite > easily adapted to export the pieces of information that CDN and data > center applications would benefit from. >=20 > The BoF will thus primarily seek an answer to the following questions: >=20 > + do CDN and data center applications require (or benefit in a > significant way from) accessing to information that cannot be made > available through existing mechanisms in a practical way? >=20 > + is an extension to the ALTO protocol (or to any other protocol) a > viable way to address such requirements? >=20 > Additional information about the topic is available on the BoF wiki > entry: http://trac.tools.ietf.org/bof/trac/#Transport >=20 > The provisional agenda for the meeting is online at: > http://www.ietf.org/proceedings/83/agenda/agenda-83-i2aex.txt > _______________________________________________ > dc mailing list > dc@ietf.org > https://www.ietf.org/mailman/listinfo/dc From yry@cs.yale.edu Fri Mar 23 10:12:25 2012 Return-Path: X-Original-To: dc@ietfa.amsl.com Delivered-To: dc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD9B21F85D9; Fri, 23 Mar 2012 10:12:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.835 X-Spam-Level: X-Spam-Status: No, score=0.835 tagged_above=-999 required=5 tests=[AWL=3.434, BAYES_00=-2.599] 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 eHeJ6fkxeNc8; Fri, 23 Mar 2012 10:12:21 -0700 (PDT) Received: from vm-emlprdomr-05.its.yale.edu (vm-emlprdomr-05.its.yale.edu [130.132.50.146]) by ietfa.amsl.com (Postfix) with ESMTP id DEFBA21F857F; Fri, 23 Mar 2012 10:12:20 -0700 (PDT) Received: from dhcp-128-36-169-151.central.yale.edu (dhcp-128-36-169-151.central.yale.edu [128.36.169.151]) (authenticated bits=0) by vm-emlprdomr-05.its.yale.edu (8.14.4/8.14.4) with ESMTP id q2NHCIDp010234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 23 Mar 2012 13:12:18 -0400 Message-ID: <4F6CAEF2.1030204@cs.yale.edu> Date: Fri, 23 Mar 2012 13:12:18 -0400 From: "Y. Richard Yang" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "dc@ietf.org" , SDNP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.71 on 130.132.50.146 Cc: IETF ALTO Subject: [dc] i2aex DC use case draft slides X-BeenThere: dc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Data Center Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 17:12:25 -0000 Hi all, As you may have seen from the IETF i2aex BoF announcement, we are working on a deck of slides for the DC bucket. Our current draft slides are at: https://datatracker.ietf.org/meeting/83/materials.html (please search for i2aex and then the DC Use Case). Any comments, suggestions from the DC/SDN/ALTO communities are greatly appreciated. Thanks. Richard