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

Hello Wes George,

Thanks for your kind comments,
for 1) your comments is right, same as other comment as well, we will
update capwap-extension to standard track other than informational document
once submit to 00 WG document if it is adopted. Since it is only about 11n
part other than update original 5416document, so we didn't use "bis".
for 2)  RFC 5415 has recommended Split and Local, capwap-hybrid-mac is not
trying to obsolete them, but define a new model in the middle, it does
not write the normaltive text, so it won't belongs to the scope of standard.

Anyway,  we appreciate your comments.

Best regards,

-Rong
On Mon, Apr 29, 2013 at 11:24 PM, George, Wes <wesley.george@twcable.com>wrote:

> 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.
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>