IEEE Standards Interpretations for IEEE Std 802.11g™-2003 Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Specific requirements — Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications AMENDMENT 4: Further Higher Data Rate Extension in the 2.4 GHz Band
Copyright © 2008 by the Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue New York, New York 10016-5997 USA All Rights Reserved.
This is an interpretation of IEEE Std 802.11g-2003.
Interpretations are issued to explain and clarify the intent of a standard and do not constitute an alteration to the original standard. In addition, interpretations are not intended to supply consulting information. Permission is hereby granted to download and print one copy of this document. Individuals seeking permission to reproduce and/or distribute this document in its entirety or portions of this document must contact the IEEE Standards Department for the appropriate license. Use of the information contained in this document is at your own risk.
IEEE Standards Department Copyrights and Permissions 445 Hoes Lane, Piscataway, New Jersey 08855-1331, USA
Interpretation Request #1
(1-01/05) Topic: (Service field content) Relevant Clause: Annex G Classification: Conflicts with Clause 17
Clause 188.8.131.52 states that within the SERVICE field "Bit b2 is used to indicate that the transmit frequency and symbol clocks are derived from the same oscillator. For all ERP systems, the Locked Clock Bit shall be set to 1."
However, clause 184.108.40.206 states "The 8-bit IEEE 802.11SERVICE field shall be reserved for future use. The value of X'00' signifies IEEE 802.11 device compliance."
Is a Clause 19 ERP device non-conformant if it sends a 1 or 2 Mbps frame without the SERVICE field bit B2 set?Interpretation Response #1
The standard is unambiguous in this case. A PHY implementing Clause 19 shall set bit B2 in the Service field, as required by 220.127.116.11 in all transmissions. A PHY implementing Clause 15 that is dependent upon a particular value in a reserved field for its correct operation is not compliant with the standard. All implementations must ignore values of reserved fields upon reception. The editor of the standard will be instructed to remove the sentence "The value of X'00' signifies IEEE 802.11 device compliance" from 18.104.22.168.
Interpretation Request #2
1-05/06 (short SYNC field value) Topic: Accuracy of material 802.11g Relevant Clauses: 22.214.171.124 (figure 153B), 126.96.36.199 Classification: Unambiguous
I think there is an error in "Figure 153B Short preamble PPDU format for DSSS-OFDM", page 23, of the document 802.11g-2003.pdf In this figure, it is written : SYNC (56 bits - Scrambled Ones) It's not coherent with the short preamble of 802.11b, which SYNC is (56 bits - Scrambled Zeros) and the text in the norm 802.11g is not coherent with the figure 153B. It should be SYNC (56 bits - Scrambled Zeros) in this figure. The text is : 188.8.131.52 The short PLCP preamble and header are used to maximize the throughput by reducing the overhead associated with the preamble and header. Figure 153B shows the short preamble PLCP PPDU format. As seen, the PSDU is appended to the PLCP Preamble and the PLCP header. The short PLCP Preamble is described in 184.108.40.206 and 220.127.116.11. In 18.104.22.168 (802.11b), the text is shortSYNC = 56 bits of scrambled "0" bits. So there is an error.
Interpretation Response #2
The standard is unambiguous on this issue. Figures are not normative and the description of the field occurs only once in the standard. Therefore the description of the short SYNC field is unambiguously defined to be scrambled zeros. The working group will consider correcting the figure during the next revision of the standard.