1. doc.: IEEE 802.11-06/860r0 Submission June 2006 Bjorn A. Bjerke, Qualcomm, Inc.Slide 1 LB84 Resolution of Selected Comments 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, 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 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at.http:// ieee802.org/guides/bylaws/sb-bylaws.pdfstuart.kerry@philips.compatcom@ieee.org Date: 2006-06-21 Authors:

2. doc.: IEEE 802.11-06/860r0 Submission June 2006 Bjorn A. Bjerke, Qualcomm, Inc.Slide 2 Abstract Suggested resolution of LB84 comments (PHY) with CIDs 318, 388 4000, 182, 7382 356, 357, 360, 4869, 384

3. doc.: IEEE 802.11-06/860r0 Submission June 2006 Bjorn A. Bjerke, Qualcomm, Inc.Slide 3 Space Time Stream Numbering CIDs 318, 388 Issue: inconsistent numbering of space time streams throughout Clause 20 Resolution: let space time stream indices always run from 1 to 4. By doing this, most equations can be left as is, and the number of changes is limited to just a few. Changes needed: –Page 205, lines 6 and 22: change “i SS =0, 1,…, N SS -1” to “i SS =1, 2,…, N SS ” –Page 208, Table n76: add 1 to all entries in the second column –Page 209, Table n77: add 1 to all entries in the second column

4. doc.: IEEE 802.11-06/860r0 Submission June 2006 Bjorn A. Bjerke, Qualcomm, Inc.Slide 4 First Description of Staggered Preamble CIDs: 4000, 182, 7382 Issue: clarification and illustration of what is meant by staggered preamble is needed Resolution: distinguish between Data HT-LTFs and Extension HT-LTFs in Figure n49 Changes needed: new Figure n49 (page 169) and accompanying text, as suggested in the contribution –11-06-0845-00-000n-lb84-replacement-text-plcp-frame-format (embedded here for convenience)

5. doc.: IEEE 802.11-06/860r0 Submission June 2006 Bjorn A. Bjerke, Qualcomm, Inc.Slide 5 Introduction of N CBPSS (i), N BPSCS (i) CID: 356, 357, 360, 4869, 384, 402 Issue: in 802.11 N CBPS denotes the number of coded bits per OFDM symbol, and N BPSC denotes the number of coded bits per subcarrier. In D1.0 these are also used for the corresponding per-stream values, which creates confusion Resolution: introduce two new variables for the corresponding per-stream values, –N CBPSS (i): number of coded bits per OFDM symbol in stream i –N BPSCS (i): number of coded bits per subcarrier in stream i

6. doc.: IEEE 802.11-06/860r0 Submission June 2006 Bjorn A. Bjerke, Qualcomm, Inc.Slide 6 Introduction of N CBPSS (i), N BPSCS (i) (2) Changes needed: –Page 172, line 36: change “k) Divide each of the N SS encoded and parsed spatial streams of bits into groups of N CBPS bits.” to “k) Divide each of the N SS encoded and parsed spatial streams of bits into groups of N CBPSS (i) bits, where i is the index of the spatial stream.” –Page 172, line 38: change N BPSC to N BPSCS (i) –Page 172, line 40: change N BPSC (i) to N BPSCS (i) –Page 175, Table n63: change N CBPSS to N CBPSS (i), and add a row with “N BPSCS (i) | Number of coded bits per single carrier per spatial stream”

7. doc.: IEEE 802.11-06/860r0 Submission June 2006 Bjorn A. Bjerke, Qualcomm, Inc.Slide 7 Introduction of N CBPSS (i), N BPSCS (i) (3) –Pages 203-206, clause 20.3.4.4 Data Interleaver: use the newly introduced parameters, as suggested in the contribution 11-06-0592-00-000n-lb84-replacement-text-data-interleaver (embedded here for convenience) –Pages 258-264, Tables n97-n102: use N BPSC instead of N TBPS for consistency –Pages 255-258, Tables n89, n90, n91, n93, n94, n95: correct the values in the N BPSC column to the reflect the total number of coded bits per subcarrier, i.e., summed across all streams