[Capwap] FW: Document Action: 'CAPWAP Protocol Base MIB' toInformational RFC

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 11 February 2010 17:33 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 3D8FA3A7747 for <ietfarch-capwap-archive@core3.amsl.com>; Thu, 11 Feb 2010 09:33:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.007
X-Spam-Level:
X-Spam-Status: No, score=-3.007 tagged_above=-999 required=5 tests=[AWL=0.592, BAYES_00=-2.599, 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 5ktgMUrjj0dq for <ietfarch-capwap-archive@core3.amsl.com>; Thu, 11 Feb 2010 09:33:05 -0800 (PST)
Received: from lists.tigertech.net (lists.tigertech.net [64.62.209.34]) by core3.amsl.com (Postfix) with ESMTP id 127EC3A776E for <capwap-archive@lists.ietf.org>; Thu, 11 Feb 2010 09:33:05 -0800 (PST)
Received: from zoidberg.tigertech.net (localhost [127.0.0.1]) by zoidberg.tigertech.net (Postfix) with ESMTP id 8B819E1807B for <capwap-archive@lists.ietf.org>; Thu, 11 Feb 2010 09:34:20 -0800 (PST)
Received: from mx3.tigertech.net (morbo.tigertech.net [67.131.251.53]) by lists.tigertech.net (Postfix) with ESMTP id BE142E240BE for <capwap@lists.tigertech.net>; Thu, 11 Feb 2010 09:34:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id A8B931D5402 for <capwap@frascone.com>; Thu, 11 Feb 2010 09:34:16 -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 0AEE21D540C for <capwap@frascone.com>; Thu, 11 Feb 2010 09:34:16 -0800 (PST)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (High) (P0); Whitelisted TTSSA (dromasca@avaya.com whitelisted)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by mx3.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Thu, 11 Feb 2010 09:34:15 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,453,1262581200"; d="scan'208";a="176096991"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 11 Feb 2010 12:34:12 -0500
X-IronPort-AV: E=Sophos;i="4.49,453,1262581200"; d="scan'208";a="430503675"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 11 Feb 2010 12:33:35 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 11 Feb 2010 18:33:12 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401F0E562@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Capwap] Document Action: 'CAPWAP Protocol Base MIB' toInformational RFC
Thread-Index: AcqrP+ILYIPOnGCaQL6qo5FI+C/JCQAADsxQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: capwap@frascone.com
Subject: [Capwap] FW: Document Action: 'CAPWAP Protocol Base MIB' toInformational 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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

 Thanks and Congratulation to the editors, chairs, and the whole WG for
completing this charter item. 

Regards,

Dan


-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org] 
Sent: Thursday, February 11, 2010 7:28 PM
To: IETF-Announce
Cc: capwap chair; Internet Architecture Board; capwap mailing list; RFC
Editor
Subject: [Capwap] Document Action: 'CAPWAP Protocol Base MIB'
toInformational RFC

The IESG has approved the following document:

- 'CAPWAP Protocol Base MIB '
   <draft-ietf-capwap-base-mib-09.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-base-mib-09.txt

Technical Summary

   The CAPWAP Protocol defines a standard, interoperable
   protocol, which enables an Access Controller (AC) to manage a
   collection of Wireless Termination Points(WTPs).

   This document defines a MIB module that can be used to manage the
   CAPWAP implementations.  This MIB module covers both configuration
   and WTP status-monitoring aspects of CAPWAP, and provides a way to
   reuse MIB modules for any wireless technology.

Working Group Summary

   The Working Group was initially chartered to issue 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.

_________________________________________________________________
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