Preamble and Header Terminology October 2006 doc.: IEEE 802.11-06/1560r1 October 2006 Preamble and Header Terminology Date: 2006-10-31 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>. Eldad Perahia (Intel) Matthew Fischer (Broadcom)

Introduction CID 1537 makes the following comment: October 2006 doc.: IEEE 802.11-06/1560r1 October 2006 Introduction CID 1537 makes the following comment: Pages 168-169 - Clarify what is in the PLCP Preamble and the PLCP Header for each of the Frame PLCP Frame Formats. The reader should not have to wait until page 197 to determine where the SERVICE field is located. We have copied and pasted text from Clause 17 and incorporated both terms into Clause 21 What do we mean by preamble in Clause 21? What do we mean by header in Clause 21? Eldad Perahia (Intel) Matthew Fischer (Broadcom)

Clause 17 The preamble consists of the short and long training fields October 2006 doc.: IEEE 802.11-06/1560r1 October 2006 Clause 17 The preamble consists of the short and long training fields The header consists of the adjacent Signal field and Service fields This is clearly illustrated in Figure 249 11maD8.0 Eldad Perahia (Intel) Matthew Fischer (Broadcom)

Issues with Terminology in Clause 21 October 2006 doc.: IEEE 802.11-06/1560r1 October 2006 Issues with Terminology in Clause 21 There is no comparable figure to Figure 249 illustrating the preamble and header The terms seem to almost be used interchangeably or used as “preamble and header” In clause 21, the training fields are intermixed with signal fields In almost all cases, the HT signal field is not adjacent to the Service field The only text defining header “The HT portion of the HT Mixed Mode header consists of the HT-SIG field that supports HT operation, and the SERVICE field.” in 11nD1.05 pg 212 line 30 conflicts with Figures n68, n69, n71, and n72 which illustrate the Header as equivalent to the HT-SIG Furthermore, there is no definition of Header in GF Eldad Perahia (Intel) Matthew Fischer (Broadcom)

October 2006 doc.: IEEE 802.11-06/1560r1 October 2006 Resolution Remove the term header from Clause 21, except if necessary when referring to Clause 17 or 19 Header Name everything in the PPDU up to, but not including, the Service field to be “preamble” Treat Service field separately from the newly termed preamble We can still continue to use terminology we are all used to such as MM preamble, legacy part of preamble, HT part of preamble, GF preamble Instruct the editor to clean up the terminology accordingly in the Clause 21 text and figures Add Service field to the beginning of the Data field in Figure n50 to complete resolution of 1537 Eldad Perahia (Intel) Matthew Fischer (Broadcom)