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

"George, Wes" <wesley.george@twcable.com> Mon, 29 April 2013 15:24 UTC

Return-Path: <wesley.george@twcable.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 0CF7321F9D98 for <opsawg@ietfa.amsl.com>; Mon, 29 Apr 2013 08:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.463
X-Spam-Level:
X-Spam-Status: No, score=-1.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
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 T2JiRXCllpP2 for <opsawg@ietfa.amsl.com>; Mon, 29 Apr 2013 08:24:37 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 7956521F9D42 for <opsawg@ietf.org>; Mon, 29 Apr 2013 08:24:37 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.87,574,1363147200"; d="scan'208";a="66433020"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 29 Apr 2013 11:24:16 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Mon, 29 Apr 2013 11:24:07 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Melinda Shore <melinda.shore@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Date: Mon, 29 Apr 2013 11:24:06 -0400
Thread-Topic: [OPSAWG] Call for adoption, two capwap-related documents
Thread-Index: Ac42wgClGAxf9e6zTqyUk0L41CB/zQOKb33A
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230430C292B2@PRVPEXVS15.corp.twcable.com>
References: <5166CA78.1070504@gmail.com>
In-Reply-To: <5166CA78.1070504@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [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: Mon, 29 Apr 2013 15:24:38 -0000

Apologies on being a few days late...

In scanning through these documents, I'm left wondering why capwap-extension doesn't formally replace (-bis) 5416 or at least update it, and why it's an informational document. This seems more like a proposed standard update, making me wonder if it perhaps belongs elsewhere (i.e. not an ops group).

Similarly, capwap-hybrid-mac seems like an update to 5415 to correct the lack of clear distinction between AP and AC that has been proven necessary for interoperability. This also seems like a proposed standard since it is apparently necessary to implement this to improve interoperability.

I think we need to sort out the intent of these documents before we determine if OpsAWG is the right fit.

Thanks,

Wes George

> -----Original Message-----
> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf
> Of Melinda Shore
> Sent: Thursday, April 11, 2013 10:37 AM
> To: opsawg@ietf.org
> Subject: [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

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.