1. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 1 Client Management Protocol Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at.http:// ieee802.org/guides/bylaws/sb-bylaws.pdfstuart.kerry@philips.compatcom@ieee.org Date: 2005-07-19 Authors:

2. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 2 Abstract The purpose of the presentation is to explore some of the architectural questions for a general protocol for managing 802.11 client stations.

3. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 3 Possible Services to Support Based on discussions and presentations here are list of some services that may need to be supported: –Dynamic channel selection –Improved power saving –AP firmware update –AP Load balancing –Deferral management –Access point coordination

4. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 4 Where are we today? 802.11 defines an ASN.1 MIB for management purposes Access to the MIB is generally via SNMP, CLI or in the case of a client via operating system calls SNMP is not very flexible and provides for the following functions: –GetRequest/SetRequest –GetResponse –GetNextRequest –Trap There is no easy way for the AP to access ASN.1 MIB

5. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 5 Is there anything close already? TGk created a measurement / report mechanism –Generic framework for providing STA to STA measurements –Measurement frames built on top of the Action frame structure –Only supports functionality that can be qualified as a measurement –Doesn’t easily support generic action requests STA Statistics Measurement –Measurement request/report for accessing peer statistics –Only capable of accessing specific statistic MIB values

6. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 6 Architectural Considerations Which portions of the reference model will be affected? –SME, MLME, PLME? Where will the processing reside? –SME, MLME, PLME? What type of frames should be used over the air? –Management, Data? Do we connect to the wired side and how? –ASN.1 MIB (w/SNMP)

7. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 7 Proposed Basic Constructs SME – PLME Interface –MLME-MGMT-REQUEST –MLME-MGMT-RESPONSE –MLME-MGMT-ACTION New Client Management Action Category –Management Request –Management Response

8. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 8 Client Management Protocol Landscape Action Frames Management Request Management Response SME MLME MMGMTREQ MMGMTACT MMGMTRSP MIB SME MLME MMGMTREQ MMGMTACT MMGMTRSP MIB STA ASTA B Mgmt Action Logic Mgmt Action Logic Mgmt Action Logic Mgmt Action Logic MIB

9. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 9 Message Flow Management Response frame MLME-MGMTRSP.ind MLME- MMGMTRSP.req MLME- MMGMTRSP.cfm MLME- MMGMTACT.cfm Management Request frame MLME- MMGMTREQ.ind MLME- MMGMTACT.req MLME-MMGMTREQ.req MLME-MMGMTREQ.cfm SMEMLME IEEE 802.11 STA A MLMESME IEEE 802.11 STA B Process Management Action

10. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 10 Management Request and Response Mgmt Req HeaderMgmt Req Element Management Request Frame Mgmt Rsp HeaderMgmt Rsp Element Management Response Frame

11. doc.: IEEE 802.11-05/0732r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 11 Possible Management Elements GetRequest – Retrieve any MIB parameter SetRequest – Set any MIB parameter Event – Generate asynchronous event SWDownload – Update the SW ????