MAC Layer FEC and 802.11e Functional Constraints January 2001 MAC Layer FEC and 802.11e Functional Constraints John M. Kowalski Sharp Laboratories USA Camas, Washington (360) 817-7520 kowalskj@sharplabs.com John M. Kowalski, Sharp
Functional Constraints (1) January 2001 Functional Constraints (1) FEC, if adopted, is an OPTION. ANY adopted MAC FEC MUST be a systematic code so that MAC header format is maintained & readable by non-FEC enabled MACs, and protected for FEC enabled MACS. ANY adopted MAC FEC must apply to 802.11a, 802.11b, and 802.11g PHYs. John M. Kowalski, Sharp
Functional Constraints (2) January 2001 Functional Constraints (2) FEC enabled MACS shall not send up errored frames to higher layers. The maximum MPDU of 802.11-1999 is maintained. Payload delivered to higher layers is reduced if MAC FEC is employed. John M. Kowalski, Sharp