FEC Capability and Control

1. FEC Capability and Control Greg Chesson, greg@atheros.com Aman Singla, aman@atheros.com G. Chesson, A. Singla, Atheros

2. This document contains editing instructions for adding FEC capability and control indications to the Tge draft P802.11e/D1. G. Chesson, A. Singla, Atheros

3. Outline • Assign an FEC capability bit • ESTAs and EAPs learn whether FEC is possible • Assign an FEC bit in QoS Control field • Indicates whether frame is FEC-encoded • FEC-capable ESTA must optimistically apply FEC to all received frame headers • For frames >= 52 bytes (minimum size frame that could have FEC) • Must accurately validate the header • Retain No-ACK bit • No text changes needed. G. Chesson, A. Singla, Atheros

4. FEC Capability • Assign a bit for “FEC-Capable” from the set of reserved bits in the Capability Information Field defined in section 7.3.1.4. • Adjust the text in section 7.5 which also assigns an FEC-Capable in the Capability Information Field (bit-11) so that sections 7.5 and 7.3.1.4 are in agreement regarding the bit definition. • Add “FEC-Capable” to the list of subfields in the 3rd sentence of the first paragraph of clause 7.3.1.4. • Add the following to clause 7.3.1.4: • “EAPs and ESTAs that can decode FEC frames as described in section 7.5 may set the FEC-Capable subfield in all frames that include the Capability Information field.” G. Chesson, A. Singla, Atheros

5. FEC Control • Edit Figure 14.5 replacing “rsrv” (in the Bit 15 column) by “FEC” –or- if Bit 15 is unavailable because of other changes to the QoS Control field, then assign a different bit for this function. • Add new section 7.1.3.5.7 as follows: 7.1.3.5.7 FEC field The FEC field is one bit in length and is set to 1 in those QoS Data frames that are FEC-encoded as specified in section 7.5. G. Chesson, A. Singla, Atheros