Forum

P 410, Figure 10.47:

?Calibration possession? should read ? Calibration position?

Dave

P 416, Figure 10.52:

TXASSL should read TXASSI

P 418 text block under figure, second line down:

"reaming" should read "roaming"

P427, Fig 10.61

40 Mhz operation mode shown at far right of diagram ( after dual CF-End )

Should show 20 Mhz operation mode ( primary/secondary )

Dave

P 427, Fig 10.61

"Beginning/End" of the lines of the NAV timelines need to be adjusted slightly relative to the "blocks" above.

Dave

P 401, second from last line:

"PCO Transmission Time subfield" should read "PCO Transition Time subfield"

Dave

In keeping with the terminology used with reference to subfields, it may be more appropriate to change the term "MRQ subfield" ( P 402, 7th line down under the "MCS Feedback" header ) to something like:

"using the MCS request ( MRQ ) capabilities of the MAI subfield".

This is due to the fact that the actual MAI subfield can provide one of two functions:

MCS request

or

ASEL indicator mode

We might also say "using the MCS request ( MRQ ) capabilities of the MAI subfield of the Link Adaptation Control subfield of the HT Control field" .......... as the Link Adaptation Control subfield is in fact itself a subfield of the HT Control field,

Dave

P 384

Perhaps a note about Figure 10.19 having the ratified 802.11n HT Capabilities layout, re bit 13 ( reserved ), and Figure 10.20 showing a ( probably draft implementation ) where bit 13 is used for PSMP support indication.

Dave

P 383

Under the heading "HT Capabilities Element", 4th and 5th lines down:

Perhaps change "The HT Capabilities Element is 28 octets long and contains 8 fields used by the HT STA to advertise the optional HT capabilities it supports"

to

"The HT Capabilities Element is 28 octets long and contains 8 fields, six of which are used by the HT STA to advertise the optional HT capabilities it supports"

The first two fields ( Element ID and Length ) are common to all IEs and don't actually advertise any optional HT capabilities.

Dave

P 384 Figure 10.19

In the IEEE802.11n-2009 document, bit numbering usually begins at zero. The SM Power Save subfield actually contains two bits ( bits B2 and B3 in the ratified document ). Only one bit is shown in the diagram.

We can see the two bits in the protocol decode of Figure 10.20, with "11..Spatial Multiplexing Enabled"

Dave