1. Managed Object Request/Response
July 2005
doc.: IEEE /0927r2
May 2006
Managed Object Request/Response
Date:
Authors:
Notice: This document has been prepared to assist IEEE 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Tim Olson et alt.
Tim Olson, Cisco Systems

2. July 2005
doc.: IEEE /0927r2
May 2006
Abstract
The purpose of this presentation is to explain the MIB Managed Object Request/Response Protocol normative text proposal,
v-Managed-Object-Request-Response-Normative-Text
This presentation is based on,
v-Client-Management-Protocol-Details
Tim Olson et alt.
Tim Olson, Cisco Systems

3. May 2006
Summary
Introduction of a new action frame pair, Managed Object Request/Response
Generic wrapper for SNMP protocol units
Simple SNMP access to client even when no SNMP agent implemented
Think of it as “SNMP-Over-WLAN”
Can only be processed when,
when TGw Robust Management Frames implemented,
when in State 3, and
when dot11MIBObjectAccessEnabled is set to true
Tim Olson et alt.

4. New WNM Action Frame value
May 2006
New WNM Action Frame value
Action field value
Description 8
Managed Object Request 9
Managed Object Response
10-255
Reserved
Tim Olson et alt.

5. Managed Object Request
May 2006
Managed Object Request
A Managed Object Request frames is sent from AP to STA for the purpose of communicating ASN.1 MIB data
A Managed Object Request may be sent only with
TGw Robust Management Frames,
when in State 3, and
when dot11MIBObjectAccessEnabled is set to true
The information elements within the Managed Object Request frame specify the desired MIB data
Subject to above conditions, Managed Object Request may be rejected only if not supported
Tim Olson et alt.

6. Managed Object Request Frame
May 2006
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 et alt.

7. Possible Managed Object Request Elements
May 2006
Possible Managed Object Request Elements
GetRequest
SetRequest
GetBulkRequest
VarBindList is the list of objects to be accessed represented by VarBind IEs
Request Type
VarBindList
Request Type
Non Repeaters
Max Repetitions
VarBindList
Element ID
Length
Object 1 Name
Object Type
Object 1 Value
Object 2 Name
Object 2 Value
Tim Olson et alt.

8. Managed Object Response Frame
May 2006
Managed Object Response Frame
Category
Action
Dialog Token
Managed Object Response 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 et alt.

9. Managed Object Response Elements
May 2006
Managed Object Response Elements
GetResponse
GetBulkResponse
Set Response
Trap
Response Type
Error Status
Error Index
VarBindList
Response Type
Timestamp
Notification Type
VarBindList
Tim Olson et alt.

10. MLME Interface Primitives
May 2006
MLME Interface Primitives
SME
SME
Mgmt Action
Logic
MIB
Mgmt Action
Logic
MIB
MOREQ
MOREQ
MLME
MORSP
MLME
MORSP
Action Frames
MIB
MIB
Mgmt Action
Logic
Mgmt Action
Logic
Managed Object Request
Managed Object Response
STA A
STA B
Two new primitives for SME – MLME Interface
MLME-MO-REQUEST
MLME-MO-RESPONSE
Tim Olson et alt.

11. Message Flow May 2006 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
Managed Object Response frame
MLME-MORSP.ind
MLME-MORSP.req
MLME-MORSP.cfm
Tim Olson et alt.

12. Security Some Managed Object Requests need more than L2 authentication
May 2006
Security
Some Managed Object Requests need more than L2 authentication
Multiple security mechanisms must be available, i.e. simple association is not enough
Setting dot11MIBObjectAccessEnabled to on requires a non-standardized authentication on the client side that can be done by existing remote access procedures
Tim Olson et alt.

13. May 2006
Motion
“Instruct the editor to incorporate the normative text proposal in v-Managed-Object Request-Response-Normative-text” into TGv Draft 0.02”
Moved by:
Seconded:
Yes :
No:
Abstain:
Tim Olson et alt.