doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 1 P802.11v report to EC on request for conditional approval to proceed to RevCom Date: Authors:

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 2 Introduction This document contains the report to the IEEE 802 Executive Committee in support of a request for conditional approval to send IEEE P802.11v to RevCom. This document (11-10/0800rx) was approved during the closing plenary session of the working group on July 16, –Passed in the Working Group x-x-x

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 3 IEEE 802 Sponsor Ballot Results – P802.11v DraftOpenedClosed Day s Ballot Type PoolApproveDisapproveAbstainReturn D Initial [81%]25 [19%]*6 [4%]137 [85%] D st Recirc [84%]22 [16%]*6 [4%]141 [88%] D nd Recirc [87%]18 [13%]6 [4%]146 [91%] D rd Recirc [92%]11 [8%]6 [4%]147 [91%] D th Recirc [94%]8 [6%]**7 [5%]148 [92%] D12.0 a th Recirc [96.5%] 5 [3.5%]**7 [5%]148 [92%] * Includes one commenter with no comments ** D12.0a indicates post ballot vote changes

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 4 Mandatory Coordination Coordination EntityDraftDateStatus IEEE-SA Editorial (MEC)D7.0Oct 09“Meets all editorial requirements. “ Quantities, Units and Letter Symbols (SCC14) Not required Terms and Definitions (SCC10) Not required Registration Authority Committee (RAC) Not required

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 5 Comments by Ballot – P802.11v DraftBallot Not Required Satisfied Known Unsatisfied Assumed Unsatisfied Total D7.0Initial D9.0Recirc D10.0Recirc D11.0Recirc D12.0Recirc Total Comment totals reflect current voter status

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 6 CommenterD7.0D9.0D10.0D11.0D12.0Total R. Roy (SRA) 4* 4 R. Miller (AT&T) J. Kwak (Interdigital) 7512 H. Worstell (AT&T) Clint Chaplin (Samsung) 246** Total Unsatisfied Comments by Commenter *Assumed unsatisfied, no response to repeated s to commenter ** Commenter has indicated that the proposed resolutions satisfy his comments

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 7 CommenterD7.0D9.0D10.0D11.0D12.0Total H. Worstell (AT&T) Total Unsatisfied Comments 7 comments are expanded to 933 comments on the same subjects, and are re-iterated in subsequent ballots

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 8 Comments by Ballot – All other commenters

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 9 Unsatisfied Comments – Topics Topic#Comments Various16 MIB33 Location12 AP Collaboration9 Scope4055 Total4125

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 10 Vote changes since last ballot M. Fischer –From: Matthew Fischer Sent: Monday, July 12, :23 PM Subject: RE: TGv remaining "no" votes –I wish to change my vote to YES. C. Hansen –From: Christopher Hansen Sent: Monday, July 12, :30 PM Subject: Re: TGv remaining "no" votes –I’ll change my vote to "yes" D. Hunter –I herewith withdraw my one negative Sponsor Ballot comment and change my v Sponsor Ballot vote from "Disapprove" to "Approve"…I approve of the technologies specified in the v draft (including the one technology about which I made the comment) and would now like to vote to Approve the Draft for submission to the IEEE 802 LMSC and to IEEE-SA as an IEEE standard. Thanks, David Hunter

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 11 Unsatisfied comments The composite of all unsatisfied comments and the resolutions approved by the ballot resolution committee during sponsor ballot is attached. –Double click on the icon to the right to open this. A copy of the unsatisfied comments presented using MyBallot access database report format is attached. –Double click on the icon to the right to open this.

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 12 TGv Timeline Recirculation (TGv Draft 13.0) Open Close Recirculation (Unchanged 13.0) Revcom Submission

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide EC Motion – Conditional Approval to send P802.11v to RevCom Request the IEEE 802 Executive Committee for conditional approval to forward P802.11v D13.0 to RevCom. Moved: Bruce Kraemer 2 nd : –Yes No Abstain WG vote on the Motion Passed: xx y, x n, x a

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 14 Project Scope This amendment provides Wireless Network Management enhancements to the MAC, and PHY, to extend prior work in radio measurement to effect a complete and coherent upper layer interface for managing devices in wireless networks.

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 15 Project Purpose The purpose of this document is to provide amendments to the IEEE PHY/MAC layers that enables management of attached stations in a centralized or in a distributed fashion (e.g. monitoring, configuring, and updating) through a layer 2 mechanism. While the k Task Group is defining messages to retrieve information from the station, the ability to configure the station is not in its scope. The proposed Task Group will also create an Access Port Management Information Base (AP MIB).

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 16 Technical Issue -1 Essence of the issue in the 7 (4055) comments is a difference of opinion on interpretation of the PAR scope –Comment # :” ….Multiple BSSID Support is outside that scope, and is not an authorized change to the Standard.” –The Ballot Resolution Committee provided the following response: –Disagree….The TGv PAR includes the indicated feature, as the scope indicates "Wireless Network Management, "to extend prior work" "to effect a COMPLETE upper layer interface". The PAR does not indicate that it is limited to extending prior work in radio measurement. The PAR requires the group to both extend prior work and to provide a complete interface. –Multiple BSSID - Enables the AP to manage/reduce the RF resources consumed by beacon frames. Note that the base multiple BSSID capability is added by TGk, and is extended by TGv.

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 17 Technical Issue -2 Essence of the issue in the 7 (4055) comments is a difference of opinion on interpretation of the PAR scope –Comment # :” …. SSID List extension is outside that scope, and is not an authorized change to the Standard..” –The Ballot Resolution Committee provided the following response: –Disagree….The TGv PAR includes the indicated feature, as the scope indicates "Wireless Network Management, "to extend prior work" "to effect a COMPLETE upper layer interface". The PAR does not indicate that it is limited to extending prior work in radio measurement. The PAR requires the group to both extend prior work and to provide a complete interface. –SSID LIST - Enables the station to send fewer Probe Request frames, reducing the RF resources used, enabling improved radio management.

doc.: Submission July 2010 D. Stanley (Aruba), B.Kraemer (Marvell) Slide 18 Comment Expansion Each of 7 Draft 7.0 comments, for example –# :” The PAR for TGv authorized the Task Group to make certain changes to the Standard, "to extend prior work in radio measurement to effect a complete and coherent upper layer interface for managing devices in wireless networks." Multiple BSSID Support is outside that scope, and is not an authorized change to the Standard.” Has a proposed resolution of –“Delete this phrase, and all refs to Multiple BSSID Support in the document” and Becomes multiple Draft 9.0 Comments, each of which restate and expand the comment, and indicate specific text changes (# becomes 106 comments), for example: –Delete the figure at page 300 line 1 and all other references to Multiple BSSID Support –Delete the figure at page 299 line 33 and all other references to Multiple BSSID Support –Delete the paragraph at page 299 line 18 and all other references to Multiple BSSID Support –Delete the figure at page 299 line 1 and all other references to Multiple BSSID Support –Delete the paragraph at page 298 line 56 and all other references to Multiple BSSID Support –Delete the figure at page 298 line 40 and all other references to Multiple BSSID Support –Delete the paragraph at page 298 line 29 and all other references to Multiple BSSID Support –etc