RFC 5833: Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Base MIB
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5833
- Published
- May 2010
- Authors
- Y. Shi; D. Perkins; C. Elliott; Y. Zhang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 73
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5834Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding MIB for IEEE 802.11Current
May 2010
- RFC 5650Definitions of Managed Objects for Very High Speed Digital Subscriber Line 2 (VDSL2)Current
September 2009
- RFC 6340Textual Conventions for the Representation of Floating-Point NumbersCurrent
August 2011
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 6615Definitions of Managed Objects for IP Flow Information ExportCurrent
June 2012
- RFC 6727Definitions of Managed Objects for Packet SamplingCurrent
October 2012
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
- RFC 4706Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2)Current
November 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?