Client Management Protocol Details July 2005 doc.: IEEE 802.11-05/0927r2 July 2005 Client Management Protocol Details Date: 2005-09-21 Authors: 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 <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, 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 <stuart.kerry@philips.com> 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 <patcom@ieee.org>. Tim Olson, Cisco Systems Tim Olson, Cisco Systems

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

Possible Services to Support July 2005 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 Tim Olson, Cisco Systems

Action Frames TGh introduced the concept of Action Frames July 2005 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): Category: Radio measurement Measurement Request Measurement Report 1 Neighbor Request 4 Neighbor Report 5 Tim Olson, Cisco Systems

TGk Measurement Request July 2005 TGk Measurement Request Measurement Request frame contains one or more Measurement Request Elements Category Action Dialog Token Number of Repetitions Measurement Request Elements Octets: 1 2 variable Measurement Request frame Element ID Length Measurement Token Measurement Request Mode Measurement Type Measurement Request Octets: 1 variable Measurement Request Element Tim Olson, Cisco Systems

Action Frame Category Name Value See clause Spectrum Management 7.4.1 July 2005 Action Frame Category Name Value See clause Spectrum Management 7.4.1 QoS 1 7.4.2 DLP 2 7.4.3 Block Ack 3 7.4.4 Reserved 4 - Radio Measurement 5 7.4.5 Wireless Network Management 6 7.4.? Tim Olson, Cisco Systems

Action Frames Action field value Description Managed Object Request 1 July 2005 Action Frames Action field value Description Managed Object Request 1 Managed Object Response 2 Control Request 3 Diagnostic Request 4 Diagnostic Response 3-255 Reserved Tim Olson, Cisco Systems

Managed Object Request July 2005 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 Tim Olson, Cisco Systems

Managed Object Request Frame July 2005 Managed Object Request Frame Category Action Dialog Token Managed Object Request Elements Octets: 1 variable Managed Object Request Frame reuses basic Action frame by including: Category, Action, Dialog Token Provides a generic wrapper for all MIB requests Tim Olson, Cisco Systems

Possible Managed Object Request Elements July 2005 Possible Managed Object Request Elements GetRequest SetRequest GetBulkRequest VarBindList is the list of objects to be accessed represented by VarBind IEs Request Type Non Repeaters Max Repetitions VarBindList Security IE ? Request Type VarBindList Security IE ? Element ID Length Object 1 Name Object Type Object 1 Value Object 2 Name Object 2 Value Tim Olson, Cisco Systems

Managed Object Response Frame July 2005 Managed Object Response Frame Category Action Dialog Token Management Request Elements Octets: 1 variable Managed Object Response Frame reuses basic Action frame by including: Category, Action, Dialog Token Provides a generic wrapper for all MIB responses Tim Olson, Cisco Systems

Possible Managed Object Response Elements July 2005 Possible Managed Object Response Elements GetResponse GetBulkResponse Set Response Trap Response Type Error Status Error Index VarBindList Security IE ? Response Type Timestamp Notification Type VarBindList Tim Olson, Cisco Systems

Management Request Elements July 2005 Control Request Frame Category Action Dialog Token Management Request Elements Octets: 1 variable Control Request Frame reuses basic Action frame by including: Category, Action, Dialog Token Provides a generic wrapper for all client control requests Tim Olson, Cisco Systems

Possible Control Request Elements July 2005 Possible Control Request Elements Roaming Request Power Change Request Other? Tim Olson, Cisco Systems

Proposed MLME Interface July 2005 Proposed MLME Interface SME – MLME Interface MLME-MO-REQUEST MLME-MO-RESPONSE MLME-CTL-REQUEST MLME-DIAG-REQUEST MLME-DIAG-RESPONSE Tim Olson, Cisco Systems

Client Management Protocol Landscape July 2005 Client Management Protocol Landscape SME SME Mgmt Action Logic MIB Mgmt Action Logic MIB MOREQ MOREQ CTLREQ CTLREQ MLME MLME MORSP MORSP Action Frames MIB MIB Mgmt Action Logic Mgmt Action Logic Managed Object Request Managed Object Response STA A STA B Control Request Tim Olson, Cisco Systems

Message Flow July 2005 IEEE 802.11 STA A IEEE 802.11 STA B SME MLME MLME SME MLME-MOREQ.req Managed Object Request frame MLME-MOREQ.ind MLME-MOREQ.cfm MLME-MOREQ.req Process Management Action MLME-MOREQ.cfm MLME-MORSP.ind Managed Objectt Response frame MLME-MORSP.req MLME-MORSP.cfm Tim Olson, Cisco Systems

July 2005 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 Tim Olson, Cisco Systems

Other Options? RFC 1089 – SNMP over Ethernet July 2005 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 Tim Olson, Cisco Systems

July 2005 Straw Poll In order to facilitate STA to STA 802.11 MIB access, should TGv provide an Action Frame based protocol or should TGv support the use of RFC 1089 (SNMP over Ethernet)? Action Frame : SNMP over Ethernet: Tim Olson, Cisco Systems