Straw Polls and Motions on 256 QAM and BW: Optional-Mandatory Features Month Year doc.: IEEE 802.11-yy/xxxxr0 Straw Polls and Motions on 256 QAM and BW: Optional-Mandatory Features Date: 2010-07-12 Authors: Vinko Erceg, Broadcom John Doe, Some Company

256 QAM Support We propose for the 256QAM modulation to be optional mode in TGac for the following reasons: Design flexibility Lower cost implementations Stringent requirements: EVM Required SNR 6 dB more than 64 QAM with equivalent coding rate PAPR Vinko Erceg et al.

BW Support (1) We propose that 20/40/80 MHz contiguous BW modes are mandatory in TGac for the following reasons: Differentiation from 802.11n Most 802.11n devices support 40MHz already Higher datarate/throughput Efficiency of the system Fast data transfers Enablement of new applications Vinko Erceg et al.

BW Support (2) We propose that 160MHz BW contiguous and non-contiguous modes are optional in TGac for the following reasons: Advanced feature Design flexibility Lower cost implementations Vinko Erceg et al.

Straw Polls Vinko Erceg, Broadcom

Straw Poll #1 Would you support 256 QAM as a mandatory device feature in TGac and indicate in the Specification Framework document? Yes: 0 No: 57 Abs: 7 Slide 6 Vinko Erceg, Broadcom

Straw Poll #2 Would you support 256 QAM as an optional device feature in TGac and indicate in the Specification Framework document? Yes: 73 No: 2 Abs: 2 Slide 7 Vinko Erceg, Broadcom

Straw Poll #3 Would you support 40 MHz BW as a mandatory transmit and receive device capability in TGac and indicate in the Specification Framework document? Yes: 71 No: 0 Abs: 15 Slide 8 Vinko Erceg, Broadcom

Straw Poll #4 Would you support 40 MHz BW as an optional transmit and receive device capability in TGac and indicate in the Specification Framework document? Yes: No: Abs: Slide 9 Vinko Erceg, Broadcom

Straw Poll #5 Would you support 80 MHz BW as a mandatory transmit and receive device capability in TGac and indicate in the Specification Framework document? Yes: 59 No: 0 Abs: 8 Slide 10 Vinko Erceg, Broadcom

Straw Poll #6 Would you support 80 MHz BW as an optional transmit and receive device capability in TGac and indicate in the Specification Framework document? Yes: No: Abs: Slide 11 Vinko Erceg, Broadcom

Straw Poll #7 Would you support contiguous 160 MHz BW as a mandatory transmit and receive device capability in TGac and indicate in the Specification Framework document? Yes: 0 No: 72 Abs: 2 Slide 12 Vinko Erceg, Broadcom

Straw Poll #8 Would you support contiguous 160 MHz BW as an optional transmit and receive device capability in TGac and indicate in the Specification Framework document? Yes: 67 No: 0 Abs: 1 Slide 13 Vinko Erceg, Broadcom

Straw Poll #9 Would you support non-contiguous 160 MHz BW as a mandatory transmit and receive device capability in TGac and indicate in the Specification Framework document? Yes: 0 No: 71 Abs: 2 Slide 14 Vinko Erceg, Broadcom

Straw Poll #10 Would you support non-contiguous 160 MHz BW as an optional transmit and receive device capability in TGac and indicate in the Specification Framework document? Yes: 67 No: 0 Abs: 7 Slide 15 Vinko Erceg, Broadcom

Motion Move to accept the following text in the Specification Framework document 11-09/0992 : A VHT STA shall be capable of transmitting and receiving frames using 20 MHz, 40 MHz, and 80 MHz channel width. Contiguous and non-contiguos 160 MHz channel width transmission and reception capability is optional as well as 256 QAM modulation capability. Slide 16 Vinko Erceg, Broadcom