Yang Shi, Chris Elliott, Yong Zhang IETF 73 rd 18 Nov 2008, Minneapolis CAPWAP WG MIB Drafts Report

 Current Work Status  CAPWAP Base MIB  CAPWAP Dot11 Binding MIB  Open Issue  Next Step Agenda

Since IETF 72th meeting, we have published three versions for CAPWAP base MIB. Now, latest version is 03. Also, we have published two versions for Dot11 binding MIB. Now, latest version is 02. Yong Zhang has joined MIB work and became one of co-editors. Current Work Status

 Current Work Status  CAPWAP Base MIB  CAPWAP Dot11 Binding MIB  Open Issue  Next Step Agenda

Changes between 00 and 01 The main work is to make MIB model consistent with base protocol and improve draft’s readability. 1)Closed all review comments from Dan. 2)To improve readability, we updated the section 5 Overview, 7.2 Relationship to the IF-MIB, 7.3 Relationship to the ENTITY-MIB. CAPWAP Base MIB (1/7) For example: Add some words to make the relationship with ENTITY-MIB more clear. "By combining the MIBs, operators could query AC and WTP's status and properties. For example, they could get WTP's current status through CAPWAP-BASE-MIB, and WTP's software revision information through ENTITY-MIB. " 3) Remove 6.1. Textual Conventions section as it is redundant with MIB definition

4) Updated the MIB definition CAPWAP Base MIB (2/7) Change module name from CAPWAP-MIB to CAPWAP-BASE-MIB Use capwapBase as prefix for all MIB objects and TC. For TCs, they are changed with "TC" characters as suffix. Add DISPLAY-HINT for TCs such as CapwapBaseWtpIdTC. As per latest protocol draft, update the reference part, DESCRIPTION part, value scope and so on for MIB objects required to modify To improve readability of MIB object name, we replace "WTP" with "Wtp","AC"with "Ac"..... For example, we rename "capwapWTPState" as "capwapBaseWtpState"

CAPWAP Base MIB (3/7) We used to use capwapWTPACNameList to provide AC name list info. Now, we use capwapBaseAcNameListTable to replace it and it is able to support more AC name items. Fix some syntax error, for example, capwapBaseStationVlanName should use SnmpAdminString type. All notification objects use capwapBaseNtf as prefix.

Changes between 01 and 02 The main work is to close one open issue: Update access right for MIB object, especially writable objects CAPWAP Base MIB (4/7) Also, made the Alignment format consistent in the definition section 1)Make capwapBaseAcNameListTable support create, modify and delete operation. 2)Add capwapBaseMacAclTable table to support station ACL configuration function. 3)Add new objects to support functions such as control Channel’s security policy configuration.

Changes between 02 and 03 The main work is to close one open issue: To able to manage CAPWAP protocol’s timer and variables To manage CAPWAP protocol’s timer and variables 1) Add MIB objects for timer and variables in the capwapBaseParameters group and capwapBaseWtpTable. For example, we define capwapBaseAcEchoInterval object for echo request interval variable. 2) To retrieve WTP's CAPWAP protocol timers and variables information, the following capwap message element extensions are defined using VendorSpecific Payload message element. CAPWAP Base MIB (5/7)

CAPWAP Base MIB (6/7) CAPWAP Protocol TimersCAPWAP Protocol Variables The extensions will be carried by Configuration Status Response Message or Configuration Update Response Message

Besides above changes, we update Section 11 for capwapBaseParameters group, capwapBaseAc group and capwapBaseMacAclTable to describe the security considerations for them. Also, we added an appendix section to log changes between versions. CAPWAP Base MIB (7/7)

 Current Work Status  CAPWAP Base MIB  CAPWAP Dot11 Binding MIB  Open Issue  Next Step Agenda

Changes between 00 and 01 The main work is to make MIB model consistent with dot11 binding protocol and improve draft’s readability. 1) Close all review comments from Dan. 2) To improve readability, we updated the section 5 Overview, 7. Relationship to Other MIB Modules, 8. Example of CAPWAP-DOT11-MIB Usage 3) To make it more clear, we replace “IEEE MIBs” with “MIBs defined in IEEE standard and its amendments” CAPWAP Dot11 Binding MIB (1/4) 4) Remove 6.1. Textual Conventions section as it is redundant with MIB definition

4) Emphasize the reuse scope of Dot11 binding MIB In the 7.4. Relationship to the MIBs defined in IEEE standard and it samendments, we added: In the binding document [I-D.ietf-capwap-protocol-binding-ieee80211], it involves a part of MIB objects defined by IEEE standard and its amendments. Although CAPWAP-DOT11-MIB uses the binding document as a reference, it could reuse all the MIB objects defined by IEEE standard and its amendments, and Not limited by the scope of the binding document. CAPWAP Dot11 Binding MIB (2/4) 5) Clarify the function of 'WLAN Service Interface' and 'WLAN BSS Interface' in the section 7.2. Relationship to the IF-MIB and section 8. Example of CAPWAP-DOT11-MIB Usage

6) Updated the MIB definition CAPWAP Dot11 Binding MIB (3/4) For TCs, they are changed and use "TC" characters as suffix. Add DISPLAY-HINT for CapwapDot11WlanIdTC TCs As per latest protocol draft, update the reference part, DESCRIPTION part, value scope and so on for MIB objects required to modify Ensure all MIB objects and TC use capwapDot11 as prefix. To improve readability of MIB object name, we replace "WTP" with "Wtp", “ WLAN"with “ Wlan"..... For example, we rename "capwapWTPMACType " as "capwapDot11WtpMacType "

Changes between 02 and 01 CAPWAP Dot11 Binding MIB (4/4) Made the Alignment format consistent in the definition section

 Current Work Status  CAPWAP Base MIB  CAPWAP Dot11 Binding MIB  Open Issue  Next Step Agenda

Open Issues

 Current Work Status  CAPWAP Base MIB  CAPWAP Dot11 Binding MIB  Open Issue  Next Step Agenda

Next Step

Questions? Comments?