[Capwap] Document Action: 'CAPWAP Protocol Binding MIB for IEEE 802.11' to Informational RFC
The IESG <iesg-secretary@ietf.org> Mon, 08 February 2010 17:08 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 0F89128C146 for <ietfarch-capwap-archive@core3.amsl.com>; Mon, 8 Feb 2010 09:08:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 GaJEXImm8VS2 for <ietfarch-capwap-archive@core3.amsl.com>; Mon, 8 Feb 2010 09:08:54 -0800 (PST)
Received: from lists.tigertech.net (lists.tigertech.net [64.62.209.34]) by core3.amsl.com (Postfix) with ESMTP id BC2E928C154 for <capwap-archive@lists.ietf.org>; Mon, 8 Feb 2010 09:08:54 -0800 (PST)
Received: from zoidberg.tigertech.net (localhost [127.0.0.1]) by zoidberg.tigertech.net (Postfix) with ESMTP id 14517E180C5 for <capwap-archive@lists.ietf.org>; Mon, 8 Feb 2010 09:09:58 -0800 (PST)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31]) by lists.tigertech.net (Postfix) with ESMTP id 4B36DE240FE for <capwap@lists.tigertech.net>; Mon, 8 Feb 2010 09:09:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx1.tigertech.net (Postfix) with ESMTP id 2C9E73610002 for <capwap@frascone.com>; Mon, 8 Feb 2010 09:09:53 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from mx1.tigertech.net (localhost [127.0.0.1]) by mx1.tigertech.net (Postfix) with ESMTP id 0C78C3610004 for <capwap@frascone.com>; Mon, 8 Feb 2010 09:09:53 -0800 (PST)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (High) (P0); Whitelisted TTSSA (64.170.98.32 whitelisted by list.dnswl.org 9.2)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by mx1.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Mon, 8 Feb 2010 09:09:52 -0800 (PST)
Received: by core3.amsl.com (Postfix, from userid 30) id 749B228C0DE; Mon, 8 Feb 2010 09:08:49 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20100208170849.749B228C0DE@core3.amsl.com>
Date: Mon, 08 Feb 2010 09:08:49 -0800
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>
Subject: [Capwap] Document Action: 'CAPWAP Protocol Binding MIB for IEEE 802.11' to Informational RFC
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.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. _________________________________________________________________ To unsubscribe or modify your subscription options, please visit: http://lists.frascone.com/mailman/listinfo/capwap Archives: http://lists.frascone.com/pipermail/capwap