[Capwap] RFC 5833 on Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Base MIB
rfc-editor@rfc-editor.org Thu, 06 May 2010 00:51 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 6D2A23A69C5 for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 5 May 2010 17:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.455
X-Spam-Level:
X-Spam-Status: No, score=-2.455 tagged_above=-999 required=5 tests=[AWL=1.144, 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 lEgaJS1AEUuW for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 5 May 2010 17:51:20 -0700 (PDT)
Received: from lists.tigertech.net (lists.tigertech.net [64.62.209.34]) by core3.amsl.com (Postfix) with ESMTP id 3FB783A6978 for <capwap-archive@lists.ietf.org>; Wed, 5 May 2010 17:51:20 -0700 (PDT)
Received: from zoidberg.tigertech.net (localhost [127.0.0.1]) by zoidberg.tigertech.net (Postfix) with ESMTP id 81DDBE1809D for <capwap-archive@lists.ietf.org>; Wed, 5 May 2010 17:51:07 -0700 (PDT)
Received: from mx4.tigertech.net (mx4.tigertech.net [74.114.88.34]) by lists.tigertech.net (Postfix) with ESMTP id 4A0E9E24105 for <capwap@lists.tigertech.net>; Wed, 5 May 2010 17:51:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.tigertech.net (Postfix) with ESMTP id 2F052E4722B for <capwap@frascone.com>; Wed, 5 May 2010 17:51:03 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hypnotoad.tigertech.net
Received: from mx4.tigertech.net (localhost [127.0.0.1]) by mx4.tigertech.net (Postfix) with ESMTP id CDFE0E4B23D for <capwap@frascone.com>; Wed, 5 May 2010 17:50:59 -0700 (PDT)
X-TigerTech-Content-Filter: SpamAssassin score -0.001 (SPF_HELO_PASS)
X-TigerTech-Spam-Status: Level 2 (High) (P0); Accepted (Neutral)
Received: from rfc-editor.org (rfc-editor.org [64.170.98.47]) by mx4.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Wed, 5 May 2010 17:50:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5F50CE0649; Wed, 5 May 2010 17:50:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100506005059.5F50CE0649@rfc-editor.org>
Date: Wed, 05 May 2010 17:50:59 -0700
Cc: capwap@frascone.com, rfc-editor@rfc-editor.org
Subject: [Capwap] RFC 5833 on Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Base MIB
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
A new Request for Comments is now available in online RFC libraries.
RFC 5833
Title: Control and Provisioning of Wireless
Access Points (CAPWAP) Protocol Base MIB
Author: Y. Shi, Ed.,
D. Perkins, Ed.,
C. Elliott, Ed.,
Y. Zhang, Ed.
Status: Informational
Stream: IETF
Date: May 2010
Mailbox: rishyang@gmail.com,
dperkins@dsperkins.com,
chelliot@pobox.com, yzhang@fortinet.com
Pages: 73
Characters: 143911
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-capwap-base-mib-09.txt
URL: http://www.rfc-editor.org/rfc/rfc5833.txt
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular, it
describes the managed objects for modeling the Control And
Provisioning of Wireless Access Points (CAPWAP) Protocol. This MIB
module is presented as a basis for future work on the SNMP management
of the CAPWAP protocol. This document is not an Internet Standards Track
specification; it is published for informational purposes.
This document is a product of the Control And Provisioning of Wireless Access Points Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap
Archives: http://lists.frascone.com/pipermail/capwap