TGn LB84 – Frame Format Ad Hoc Status and Motions Month Year doc.: IEEE 802.11-06/0689r0 July 2006 TGn LB84 – Frame Format Ad Hoc Status and Motions Motion Date: 2006-07-20 Authors: 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 <http:// 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 <stuart.kerry@philips.com> 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 <patcom@ieee.org>. Peter Loc, Marvell Matthew Fischer, Broadcom

Frame Format Ad Hoc Progress Update July 2006 Frame Format Ad Hoc Progress Update Peter Loc, Marvell

Frame Formats Ad Hoc Motions July 2006 Frame Formats Ad Hoc Motions Motions to approve comment resolutions that have been agreed in the Frame Formats ad hoc. Peter Loc, Marvell

Frame Formats Ad Hoc Motions July 2006 Frame Formats Ad Hoc Motions 3 Motions to approve for the following categories of Resolutions: ACCEPTED COUNTERED with proposed changes REJECTED (with reasons) Peter Loc, Marvell

Month Year doc.: IEEE 802.11-06/0689r0 July 2006 Motion To Accept the Comment Resolutions of the following CIDs except CID 3700 as contained in Doc 11-06-0717-20 Peter Loc, Marvell Matthew Fischer, Broadcom

Month Year doc.: IEEE 802.11-06/0689r0 July 2006 Motion To Accept the Comment Resolutions of the following CIDs as contained in Doc 11-06-0717-20 Peter Loc, Marvell Matthew Fischer, Broadcom

Month Year doc.: IEEE 802.11-06/0689r0 July 2006 Motion To Accept the Comment Resolutions of the following CIDs plus 1740, 2007, 4281 as contained in Doc 11-06-0717-20 Peter Loc, Marvell Matthew Fischer, Broadcom

Resolution to deferred CIDs 1149 , 7582, 11993 Requires a submission Month Year doc.: IEEE 802.11-06/0689r0 July 2006 Resolution to deferred CIDs 1149 , 7582, 11993 Requires a submission CID 11993 Add capability of HTC support CID 7582 All the features of the HTC are optional. It should therefore be possible to simplify the implementation of a device that does not support any of the HTC features. CID 1149 Is there any restriction on the use of the QOS NULL + HTC + MA? Peter Loc, Marvell Matthew Fischer, Broadcom

11-06-1026-01-000n-tgn-lb84-htc-capabilty submission.doc Month Year doc.: IEEE 802.11-06/0689r0 July 2006 Motion Motion: Instruct the editor to make modification to the draft based on submission 11-06-1026-01-000n-tgn-lb84-htc-capabilty submission.doc Peter Loc, Marvell Matthew Fischer, Broadcom

Submission to Support Resolution July 2006 Submission to Support Resolution By Solomon Trainin 11-06-1026-00-000n-tgn-lb84-htc-capabilty submission.doc Peter Loc, Marvell

Modified Version of Previous Motion July 2006 Modified Version of Previous Motion Peter Loc, Marvell

Month Year doc.: IEEE 802.11-06/0689r0 July 2006 Motion To Accept the Comment Resolutions of the following CIDs plus 1740 (without 2007, 4281) as contained in Doc 11-06-0717-20 Peter Loc, Marvell Matthew Fischer, Broadcom

CID 1740 Comment Proposed change July 2006 CID 1740 Comment "The setting of the Order field determines whether the HT Control field is present, as specified in 7.1.3.1.10. The HT Control field is defined in 7.1.3.8." Do not use order bit to signal the presence of HT Control field Proposed change Use other bit in the Frame Control field. Rejected - inadequate justification. Peter Loc, Marvell

CID 2007 Comment Proposed change July 2006 CID 2007 Comment Beacon bloat. You've added two huge information elements to beacons, and specified that they be sent over a/b/g channels if the AP also supports 11n. Proposed change Reduce the number of options, and reduce the size of the HT Capabilities information element and the Additional HT Information information element Rejected - The distribution of the number of options over the 2 information elements have been carefully designed and considered to be what needed Peter Loc, Marvell

CID 4281 Comment Proposed change July 2006 CID 4281 Comment Why do we have separate elements for "HT Capabilities" and "Additional HT Information"? Seems like they should be combined into "HT Capabilities". Proposed change Merge "Additional HT Information" into "HT Capabilities". Rejected - The distribution of the number of options over the 2 information elements have been carefully designed and considered to be what needed Peter Loc, Marvell