1. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 1 Client Management Protocol Details 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-09-21 Authors:

2. doc.: IEEE 802.11-05/0927r0 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/0927r0 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: –MIB Access –Client Diagnostics –Dynamic channel selection –Improved power saving –AP firmware update –AP Load balancing –Deferral management –Access point coordination

4. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 4 Action Frames TGh introduced the concept of Action Frames Action Frames are implemented as a new Management Frame subtype Action Frames are segmented into a two level hierarchy: Action Category and Action [frame] Example (from TGk): Measurement Request0 Measurement Report1 Neighbor Request4 Neighbor Report5 Category: Radio measurement

5. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 5 TGk Measurement Request Measurement Request frame contains one or more Measurement Request Elements CategoryActionDialog Token Number of Repetitions Measurement Request Elements Octets:111 2 variable Element ID LengthMeasurement Token Measurement Request Mode Measurement Type Measurement Request Octets:111 11 variable Measurement Request Element Measurement Request frame

6. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 6 Action Frame Category NameValueSee clause Spectrum Management07.4.1 QoS17.4.2 DLP27.4.3 Block Ack37.4.4 Reserved4- Radio Measurement57.4.5 Client Management67.4.?

7. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 7 Action Frames Action field valueDescription 0Managed Object Request 1Managed Object Response 2Control Request 3Diagnostic Request 4Diagnostic Response 3-255Reserved

8. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 8 Managed Object Request A Managed Object Request frames are sent from STA to STA for the purpose of communicating ASN.1 MIB data A Managed Object Request may be sent from any combination of AP or client STA The information elements within the Managed Object Request frame specify the desired MIB data and security info if required A Managed Object Request may be rejected only if not supported or proper security credentials were not supplied

9. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 9 Managed Object Request Frame CategoryActionDialog TokenManaged Object Request Elements Octets:111variable Managed Object Request Frame reuses basic Action frame by including: Category, Action, Dialog Token Provides a generic wrapper for all MIB requests

10. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 10 Possible Managed Object Request Elements GetRequest GetBulkRequest GetNextRequest SetRequest VarBindList IE is the list of objects to be accessed Element IDLengthRequest IDVarBindList IESecurity IE Object 1 NameObject 1 Value Object 2 NameObject 2 Value

11. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 11 Managed Object Response Frame CategoryActionDialog TokenManagement Request Elements Octets:111variable Managed Object Response Frame reuses basic Action frame by including: Category, Action, Dialog Token Provides a generic wrapper for all MIB responses

12. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 12 Possible Managed Object Response Elements GetResponse GetBulkResponse GetNextResponse Set Response Trap Element IDLengthRequest IDVarBindList IESecurity IE Element IDLengthVarBindList IE

13. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 13 Control Request Frame CategoryActionDialog TokenManagement Request Elements Octets:111variable Control Request Frame reuses basic Action frame by including: Category, Action, Dialog Token Provides a generic wrapper for all client control requests

14. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 14 Possible Control Request Elements Roaming Request Power Change Request Other?

15. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 15 Proposed MLME Interface SME – MLME Interface –MLME-MO-REQUEST –MLME-MO-RESPONSE –MLME-CTL-REQUEST –MLME-DIAG-REQUEST –MLME-DIAG-RESPONSE

16. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 16 Client Management Protocol Landscape Action Frames Managed Object Request Managed Object Response SME MLME MOREQ CTLREQ MORSP MIB SME MLME MOREQ CTLREQ MORSP MIB STA ASTA B Mgmt Action Logic Mgmt Action Logic Mgmt Action Logic Mgmt Action Logic MIB Control Request

17. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 17 Message Flow Managed Objectt Response frame MLME-MORSP.indMLME-MORSP.req MLME-MORSP.cfm MLME-MOREQ.cfm Managed Object Request frame MLME-MOREQ.ind MLME-MOREQ.req MLME-MOREQ.cfm SMEMLME IEEE 802.11 STA A MLMESME IEEE 802.11 STA B Process Management Action

18. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 18 Security Requirement Some Managed Object Requests need more than L2 authentication Multiple security mechanisms must be available A generic IE capable of multiple schemes would be great: –Community String –Shared Secret –Certificates –Other? IE can be included per Managed Object Request

19. doc.: IEEE 802.11-05/0927r0 Submission July 2005 Tim Olson, Cisco SystemsSlide 19 Other Options? RFC 1089 – SNMP over Ethernet –Ethernet Type 0x814c created to carry SNMP PDU’s –All other standard SNMP protocol definition used as is This would mean simply running SNMP between AP and client using data frames formed directly in the AP or client STA All existing SNMPv2 (or v3) protocol constructs could be supported