80 likes | 86 Views
CAPWAP Working Group MIB documents IETF 65. David T. Perkins. MIB Work. From the CAPWAP charter: Deliverable - A MIB Document to support the CAPWAP protocol Mar 2006 - Issue first Internet-Draft of CAPWAP MIB Aug 2006 - WGLC for CAPWAP MIB
E N D
CAPWAP Working GroupMIB documentsIETF 65 David T. Perkins
MIB Work • From the CAPWAP charter: • Deliverable - A MIB Document to support the CAPWAP protocol • Mar 2006 - Issue first Internet-Draft of CAPWAP MIB • Aug 2006 - WGLC for CAPWAP MIB • Sep 2006 - Submit CAPWAP MIB to IESG as Proposed Standard RFC • Observations • First I-D for CAPWAP protocol has been issued • No discussions yet on the WG mailing list on MIB work • The "CAPWAP Objectives" document does not directly address MIB requirements
Dilemma • Have milestone at end of month, but do not have requirements. • Have not seen WG mailing list discussions, nor have seen posting of MIB modules from CAPWAP vendors, which are needed to move forward. • Can create a MIB module (or modules), but may cause thrashing on WG mailing list. • However, need MIB requirements because they will affect definition of CAPWAP protocol.
Suggested Approach • Ask for vendor submission of MIB modules, and post on www.capwap.org WEB site (or post URLs to documents) • Post a list of relevant MIB modules (such as IEEE 802.11, IETF Entity, IETF Interface, etc) on www.capwap.org WEB site • Creation of two documents: • CAPWAP management model, which describes use of existing MIB modules • CAPWAP MIB module, which defines new objects and notifications
Proposed CAPWAP Tables • Configured WTPs containing configuration attributes • Radios for configured WTPs containing configuration attributes • Current and past WTP connections containing current status, statistics, and running configuration • Radios on connected WTPs containing current status, statistics, and running configuration • Configuration for each WLAN
Tables (continued) • For each WTP, for each radio, each WLAN, the status, statistics, and running configuration • STA sessions containing current status, statistics, and configuration • Configured STA identifiers (user or MAC) containing configuration attributes • Configured neighbor and rogue APs and STAs • Detected rogue, neighbor, and unknown APs and STAs containing current status, statistics, and configuration
Proposed CAPWAP Notifications • WTP session (started, stopped, failed) • STA session (started, stopped, failed) • Rogue AP detected • Rogue STA detected • Power and/or Channel changed on WTP radio(s)
Wrap up • Questions • Suggestions