[Capwap] Thanks all of you
Richard <rishyang@gmail.com> Tue, 09 February 2010 15:21 UTC
Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48DE83A709A for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 9 Feb 2010 07:21:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.169
X-Spam-Level:
X-Spam-Status: No, score=-2.169 tagged_above=-999 required=5 tests=[AWL=1.429, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 oCaU-I-rm65c for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 9 Feb 2010 07:21:08 -0800 (PST)
Received: from lists.tigertech.net (lists.tigertech.net [64.62.209.34]) by core3.amsl.com (Postfix) with ESMTP id 7D37B3A71D4 for <capwap-archive@lists.ietf.org>; Tue, 9 Feb 2010 07:21:08 -0800 (PST)
Received: from zoidberg.tigertech.net (localhost [127.0.0.1]) by zoidberg.tigertech.net (Postfix) with ESMTP id 879BAE18079 for <capwap-archive@lists.ietf.org>; Tue, 9 Feb 2010 07:22:15 -0800 (PST)
Received: from mx3.tigertech.net (morbo.tigertech.net [67.131.251.53]) by lists.tigertech.net (Postfix) with ESMTP id B25D4E240BE for <capwap@lists.tigertech.net>; Tue, 9 Feb 2010 07:22:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id 9A1E619E838 for <capwap@frascone.com>; Tue, 9 Feb 2010 07:22:10 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at morbo.tigertech.net
Received: from mx3.tigertech.net (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id 287D719E5B7 for <capwap@frascone.com>; Tue, 9 Feb 2010 07:22:10 -0800 (PST)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (High) (P0); Whitelisted TTSSA (rishyang@gmail.com whitelisted)
Received: from mail-pz0-f185.google.com (mail-pz0-f185.google.com [209.85.222.185]) by mx3.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Tue, 9 Feb 2010 07:22:10 -0800 (PST)
Received: by pzk15 with SMTP id 15so3571449pzk.11 for <capwap@frascone.com>; Tue, 09 Feb 2010 07:22:09 -0800 (PST)
MIME-Version: 1.0
Received: by 10.115.135.5 with SMTP id m5mr2399036wan.8.1265728929541; Tue, 09 Feb 2010 07:22:09 -0800 (PST)
Date: Tue, 09 Feb 2010 23:22:09 +0800
Message-ID: <8556013e1002090722oda1bfc0r205f1c6874b81f97@mail.gmail.com>
From: Richard <rishyang@gmail.com>
To: capwap@frascone.com, mmani@avaya.com, dromasca@avaya.com, mrw@lilacglade.org, dbharrington@comcast.net, bertietf@bwijnen.net, dperkins3600@gmail.com, yozhang@gmail.com, Dorothy.Gellert@gmail.com
Subject: [Capwap] Thanks all of you
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Post: <mailto:capwap@frascone.com>
X-Tigertech-Mailman-Hint: 636170776170
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=subscribe>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
Content-Type: multipart/mixed; boundary="===============0941226826=="
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com
Hi, Thanks Dan, Chairs, my coeditors, all the expert in the mailing list. CAPWAP WG is the first one I involved in the IETF. Before that, I never imagine I could do some contribution in the IETF. Besides the editors' hard work in years, your guidance and help let the dream come true. Thanks again. Regards Richard 2010/2/9 <capwap-request@frascone.com> > Send Capwap mailing list submissions to > capwap@frascone.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.frascone.com/mailman/listinfo/capwap > or, via email, send a message with subject or body 'help' to > capwap-request@frascone.com > > You can reach the person managing the list at > capwap-owner@frascone.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Capwap digest..." > > > Today's Topics: > > 1. Document Action: 'CAPWAP Protocol Binding MIB for IEEE > 802.11' to Informational RFC (The IESG) > 2. FW: Document Action: 'CAPWAP Protocol Binding MIB for > IEEE802.11' to Informational RFC (Romascanu, Dan (Dan)) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 8 Feb 2010 09:08:49 -0800 (PST) > From: The IESG <iesg-secretary@ietf.org> > Subject: [Capwap] Document Action: 'CAPWAP Protocol Binding MIB for > IEEE 802.11' to Informational RFC > To: IETF-Announce <ietf-announce@ietf.org> > Cc: capwap chair <capwap-chairs@tools.ietf.org>, Internet > Architecture > Board <iab@iab.org>, capwap mailing list <capwap@frascone.com>, > RFC > Editor <rfc-editor@rfc-editor.org> > Message-ID: <20100208170849.749B228C0DE@core3.amsl.com> > > The IESG has approved the following document: > > - 'CAPWAP Protocol Binding MIB for IEEE 802.11 ' > <draft-ietf-capwap-802dot11-mib-06.txt> as an Informational RFC > > > This document is the product of the Control And Provisioning of Wireless > Access Points Working Group. > > The IESG contact persons are Dan Romascanu and Ron Bonica. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-capwap-802dot11-mib-06.txt > > Technical Summary > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols. In particular, it > describes managed objects for modeling the Control And Provisioning > of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless > binding. > > Working Group Summary > > The Working Group was initially chartered to define a Proposed > Standard but there was not enough working group involvement with this > document to warrant publication as a Proposed Standard. The document > is complete, went through full MIB Docotrs reviews, and there is no > disagreement about publishing it as Informational. > > > Document Quality > > There is at least one implementation of this protocol underway. > At various phases of development the work was advised and reviewed by > David Harrington, Dan Romascanu, and Bert Wijnen for the MIB Doctors > team. > > Personnel > > Margaret Wassermann is the document shepherd. Dan Romascanu is > the responsible AD. Bert Wijnen is the MIB Doctor. > > RFC Editor Note > > 1. In the Abstract section: > > OLD: > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols. In particular, it > describes managed objects for modeling the Control And Provisioning > of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless > binding. > > NEW: > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols. In particular, it > describes managed objects for modeling the Control And Provisioning > of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless > binding. This MIB module is presented as a basis for future work on > the management of the CAPWAP protocol using the Simple Network > Management Protocol (SNMP). > > 2. In the Introduction Section: > > OLD: > > This document defines a MIB module that can be used to manage CAPWAP > implementations for IEEE 802.11 wireless binding. This MIB module > covers both configuration for Wireless Local Area Network (WLAN) and > a way to reuse the IEEE 802.11 MIB module [IEEE.802-11.2007]. > > NEW: > > This document defines a MIB module that can be used to manage CAPWAP > implementations for IEEE 802.11 wireless binding. This MIB module > covers both configuration for Wireless Local Area Network (WLAN) and > a way to reuse the IEEE 802.11 MIB module [IEEE.802-11.2007]. It is > presented as a basis for future work on the SNMP management of the > CAPWAP protocol. > > > > ------------------------------ > > Message: 2 > Date: Mon, 8 Feb 2010 18:11:49 +0100 > From: "Romascanu, Dan (Dan)" <dromasca@avaya.com> > Subject: [Capwap] FW: Document Action: 'CAPWAP Protocol Binding MIB > for IEEE802.11' to Informational RFC > To: <capwap@frascone.com> > Message-ID: > < > EDC652A26FB23C4EB6384A4584434A0401F0DC3D@307622ANEX5.global.avaya.com> > > Content-Type: text/plain; charset="us-ascii" > > Congratulations to the editors, chairs and the whole WG for meeting > this deadline. > > Dan > > > -----Original Message----- > From: The IESG [mailto:iesg-secretary@ietf.org] > Sent: Monday, February 08, 2010 7:09 PM > To: IETF-Announce > Cc: capwap chair; Internet Architecture Board; capwap mailing list; RFC > Editor > Subject: [Capwap] Document Action: 'CAPWAP Protocol Binding MIB for > IEEE802.11' to Informational RFC > > The IESG has approved the following document: > > - 'CAPWAP Protocol Binding MIB for IEEE 802.11 ' > <draft-ietf-capwap-802dot11-mib-06.txt> as an Informational RFC > > > This document is the product of the Control And Provisioning of Wireless > Access Points Working Group. > > The IESG contact persons are Dan Romascanu and Ron Bonica. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-capwap-802dot11-mib-06.tx > t<http://www.ietf.org/internet-drafts/draft-ietf-capwap-802dot11-mib-06.tx%0At> > > Technical Summary > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols. In particular, it > describes managed objects for modeling the Control And Provisioning > of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless > binding. > > Working Group Summary > > The Working Group was initially chartered to define a Proposed > Standard but there was not enough working group involvement with this > > document to warrant publication as a Proposed Standard. The document > is complete, went through full MIB Docotrs reviews, and there is no > disagreement about publishing it as Informational. > > > Document Quality > > There is at least one implementation of this protocol underway. > At various phases of development the work was advised and reviewed > by > David Harrington, Dan Romascanu, and Bert Wijnen for the MIB Doctors > > team. > > Personnel > > Margaret Wassermann is the document shepherd. Dan Romascanu is > the responsible AD. Bert Wijnen is the MIB Doctor. > > RFC Editor Note > > 1. In the Abstract section: > > OLD: > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols. In particular, it > describes managed objects for modeling the Control And Provisioning > of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless > binding. > > NEW: > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols. In particular, it > describes managed objects for modeling the Control And Provisioning > of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless > binding. This MIB module is presented as a basis for future work on > the management of the CAPWAP protocol using the Simple Network > Management Protocol (SNMP). > > 2. In the Introduction Section: > > OLD: > > This document defines a MIB module that can be used to manage CAPWAP > implementations for IEEE 802.11 wireless binding. This MIB module > covers both configuration for Wireless Local Area Network (WLAN) and > a way to reuse the IEEE 802.11 MIB module [IEEE.802-11.2007]. > > NEW: > > This document defines a MIB module that can be used to manage CAPWAP > implementations for IEEE 802.11 wireless binding. This MIB module > covers both configuration for Wireless Local Area Network (WLAN) and > a way to reuse the IEEE 802.11 MIB module [IEEE.802-11.2007]. It is > presented as a basis for future work on the SNMP management of the > CAPWAP protocol. > > _________________________________________________________________ > To unsubscribe or modify your subscription options, please visit: > http://lists.frascone.com/mailman/listinfo/capwap > > Archives: http://lists.frascone.com/pipermail/capwap > > > ------------------------------ > > _________________________________________________________________ > To unsubscribe or modify your subscription options, please visit: > http://lists.frascone.com/mailman/listinfo/capwap > > Archives: http://lists.frascone.com/pipermail/capwap > > End of Capwap Digest, Vol 51, Issue 1 > ************************************* >
_________________________________________________________________ To unsubscribe or modify your subscription options, please visit: http://lists.frascone.com/mailman/listinfo/capwap Archives: http://lists.frascone.com/pipermail/capwap
- Re: [Capwap] Thanks all of you Mani, Mahalingam (Mani)
- [Capwap] Thanks all of you Richard
- [Capwap] Thanks all of you young