IEEE P802.11 Wireless LANs LB 190 PHY CIDs (Comment Resolution for D4.0) Date: 8 November 2012 Author(s): Name Affiliation Address Phone email Eldad Perahia Intel Corporation eldad.perahia@intel.com Clause 22 comments: CID Page Clause Comment Proposed Change Resn Resolution Status 7317 208.00 22 It should be allowed to not Allow this J Rejected - transmit anything to an receiver MU PPDU recipient, after implementations the APEP, rather than would likely be having to transmit padding negatively affected by an option to not transmit anything on some portions of some streams within a single PPDU, e.g. consider the effect of the ensuing power change at the receiver. 7320 208.00 22 The block size/througput Steal the HT terminology REJECTED - J per BCC encoder should and adjust the numbers There is no need be specified, as they were to block for HT, to justify the N_ES size/throughput values given in the tables per BCC encoder (in HT you can easily used to choose verify that in the tables in N_ES. 20-6, all MCSes where the Implementers LGI rate is >= 300 Mbps only require the have N_ES = 2, else actual values in N_ES = 1) the tables to build
IEEE P802.11 Wireless LANs LB 190 PHY CIDs (Comment Resolution for D4.0) Date: 8 November 2012 Author(s): Name Affiliation Address Phone email Eldad Perahia Intel Corporation eldad.perahia@intel.com Clause 22 comments: CID Page Clause Comment Proposed Change Resn Status Resolution 7317 208.00 22 It should be allowed to not transmit anything to an MU PPDU recipient, after the APEP, rather than having to transmit padding Allow this J Rejected - receiver implementations would likely be negatively affected by an option to not transmit anything on some portions of some streams within a single PPDU, e.g. consider the effect of the ensuing power change at the receiver. 7320 208.00 22 The block size/througput per BCC encoder should be specified, as they were for HT, to justify the N_ES values given in the tables (in HT you can easily verify that in the tables in 20-6, all MCSes where the LGI rate is >= 300 Mbps have N_ES = 2, else N_ES = 1) Steal the HT terminology and adjust the numbers J REJECTED - There is no need to block size/throughput per BCC encoder used to choose N_ES. Implementers only require the actual values in the tables to build
11-12-1296-00-00ac-lb190-phy-cids.docx