1. Proposed changes to the 802.11v Draft
Month Year
July 2006
Nov 2006
Proposed changes to the v Draft
Authors:
Date:
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
Cha et al.
Jokela et al

2. Agenda Overview Proposed changes Comments Nov 2006 Month Year
July 2006
Nov 2006
Agenda
Overview
Proposed changes
Comments
Cha et al.
Jokela et al

3. Overview Objective Motivations
Month Year
July 2006
Nov 2006
Overview
Objective
To reduce the time to acquire FBMS and achieve the efficient power saving operation
Motivations
A client may already use multicast service prior to entering WLAN
e.g., Roaming between WLAN and other mobile networks (vertical handoff)
A client may want to use multicast service immediately after turned on
Reducing control overhead, time to acquire FBMS, efficient power saving,
To allow an STA to acquire FBMS at association stage, it is possible to reduce the time to acquire FBMS and achieve the efficient power saving operation
Cha et al.
Jokela et al

4. Nov 2006
Proposed Changes
Allow Association request/response frame to include FBMS request IE/FBMS response IE
In effect, non-AP STA can request FBMS during Association procedure
Association Request
FBMS Request IE
Association Response
FBMS Response IE
Cha et al.

5. Association Response +
Month Year
July 2006
Nov 2006
Possible Flows
Existing Message Flow
Proposed Message Flow AP
Non-AP STA AP
Non-AP STA
Beacon +
AID 0 IE
Beacon +
AID 0 IE
Association Request
Association Request +
FBMS Request IE
Association Response
Association Response +
FBMS Response IE
FBMS Request
FBMS Response
Cha et al.
Jokela et al

6. Association Request/Response Messages
Nov 2006
Association Request/Response Messages
Association Request Frame Body
Association Response Frame Body
Order
Information 10
Wireless Network Management Capability 11
FBMS Request
1112
Supported Regulatory Classes
Order
Information 8
Wireless Network Management Capability 9
FBMS Response
910
Supported Regulatory Classes
Cha et al.

7. Comments The following modification of text is necessary
Nov 2006
Comments
The following modification of text is necessary
Peer-to-Peer Link Event Log Report
The purpose of the RSNAPeer-to-Peer Link Event Log report is to provide the AP with a historical view of the previous peer to peer connectivity.
Syslog Event Log Report
The purpose of the RSNASyslog Event Log report is to provide the AP with a vendor specific event log or “human” readable log for a given client STA.
Cha et al.

8. Nov 2006
Questions/Feedback
Cha et al.

9. Month Year
July 2006
Nov 2006
Motion
Move to include normative text in document v-Proposed changes to the v into the TGv draft.
Mover:
Seconder:
Results:
Cha et al.
Jokela et al