[OPSAWG] 答复: Call for adoption, two capwap-related documents

"Hening (A)" <hening@huawei.com> Fri, 12 April 2013 06:58 UTC

Return-Path: <hening@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4B2521F8AA8 for <opsawg@ietfa.amsl.com>; Thu, 11 Apr 2013 23:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.788
X-Spam-Level: **
X-Spam-Status: No, score=2.788 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
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 imOp+YV-0pbH for <opsawg@ietfa.amsl.com>; Thu, 11 Apr 2013 23:58:45 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9922F21F8A3F for <opsawg@ietf.org>; Thu, 11 Apr 2013 23:58:44 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQH71403; Fri, 12 Apr 2013 06:58:43 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 12 Apr 2013 07:58:06 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 12 Apr 2013 07:58:40 +0100
Received: from NKGEML505-MBS.china.huawei.com ([169.254.2.63]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.01.0323.007; Fri, 12 Apr 2013 14:58:36 +0800
From: "Hening (A)" <hening@huawei.com>
To: Melinda Shore <melinda.shore@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Call for adoption, two capwap-related documents
Thread-Index: AQHONsIEa0crF6v62kmaGS+5P4QwtpjR+77g
Date: Fri, 12 Apr 2013 06:58:36 +0000
Message-ID: <EBBC5BAEECCB144D9ACD1F831B473CA72D578079@nkgeml505-mbs.china.huawei.com>
References: <5166CA78.1070504@gmail.com>
In-Reply-To: <5166CA78.1070504@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.67.17]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [OPSAWG] 答复: Call for adoption, two capwap-related documents
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2013 06:58:45 -0000

Hi, all
A good protocol should be optimized along with the development of new technology. 802.11n is well-supported in draft-chen-opsawg-capwap-extension-00.txt.
A good protocol should also be optimized with new requirement. draft-shao-opsawg-capwap-hybridmac-00.txt will solve the problem of coordination of different manufacturers.

So, I support the adoption of these two drafts.

Best regards
Hening

-----邮件原件-----
发件人: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] 代表 Melinda Shore
发送时间: 2013年4月11日 22:37
收件人: opsawg@ietf.org
主题: [OPSAWG] Call for adoption, two capwap-related documents

This is a call for working group adoption of two drafts
related to capwap use for 802.11n.

http://www.ietf.org/id/draft-shao-opsawg-capwap-hybridmac-00.txt
http://www.ietf.org/id/draft-chen-opsawg-capwap-extension-00.txt

Since the IETF 86 meeting the authors have gotten expert review
of their documents and feel that the documents are ready for
working group adoption.

We'll be assessing consensus on 25 April 2013.  Please indicate
which draft or drafts you're supporting or not supporting.

Thanks,

Melinda, Scott, and Chris
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg