1. Resource Request/Response Discussion
Month Year
doc.: IEEE yy/xxxxr0
September 2005
Resource Request/Response Discussion
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
Michael Montemurro, Chantry Networks
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
September 2005
Abstract
Review of requirements for the Mobility Domain for the purpose of BSS Transition.
Propose changes to the TGr draft which combine the Resource Mobility Domain and Security Mobility Domain concepts.
The text changes for Mobility Domain are included in Document 11-05/0867r0
Michael Montemurro, Chantry Networks
John Doe, Some Company

3. September 2005
Background
Currently, the TGr draft introduces Resource Mobility Domain and Security Mobility Domain.
Practically speaking, the security domain is really governed by the R0 Key Holder (or possibly a set of R0 key holders).
A STA can only BSS-Transition to:
Another BSS in the ESS
A BSS that advertises the same R0KeyHolder
Michael Montemurro, Chantry Networks

4. Mobility Domain Requirements
September 2005
Mobility Domain Requirements
Allow a STA to determine which AP’s are BSS-transition targets.
Identify the AP as reachable over the DS.
A STA can only BSS-Transition to a target AP only if the AP is part of the same Mobility Domain and shares the same R0KeyHolder.
This implies that the Security Domain is the same as the Mobility Domain.
Michael Montemurro, Chantry Networks

5. Mobility Domain Definition
September 2005
Mobility Domain Definition
A set of BSSs, within the same ESS, identified by a Mobility Domain Identifier that provide the following assurances to the STA:
fast transition is possible between any two BSSs using either "over the DS" or "over the air" procedures.
a common key infrastructure is accessible at all BSSs
common network services are accessible through all BSSs.
Michael Montemurro, Chantry Networks

6. Protocol Requirements
September 2005
Protocol Requirements
The Mobility Domain will be advertised by the Mobility Domain IE.
The Mobility Domain IE will be included by the AP in the Beacon and Probe Response messages.
Michael Montemurro, Chantry Networks

7. Mobility Domain IE Element ID Length Mobility Domain Identifier
September 2005
Mobility Domain IE
Element ID
Length
Mobility Domain Identifier
Octets: 1 1 6
The Mobility Domain Identifier is unique for each network and specified with 6 octets.
The Mobility Domain Identifier is included in the Beacon and Probe Response messages.
Michael Montemurro, Chantry Networks

8. Summary of Text Changes
September 2005
Summary of Text Changes
Change all references to Resource Mobility Domain and Security Mobility Domain to Mobility Domain.
Remove all references to Resource Mobility Domain Identifier and Security Mobility Domain Identifier.
Add the definition of Mobility Domain IE and add the IE to the Beacon and Probe Response messages.
The changes are captured in Document 11-05/xxxxr0
Michael Montemurro, Chantry Networks

9. September 2005
Motion
Instruct the editor to incorporate the changes into the TGr draft as described in document 11-05/0867r0.
Michael Montemurro, Chantry Networks