If the BSSBasicRateSet parameter the BSSBasicMCSSet parameter are empty (e.g., a scanning STA that is not yet associated with a BSS), the frame shall be transmitted in a non-HT PPDU using one of the mandatory PHY rates. Proposed resolution: See CID 3182 (11/1144r8). No change is necessary to D1.2 text. Comments (CID 3486, 2679 COEX) – 3486 73 17 T This statement is not Remove statement. Agree. needed. I think what it says is that there Removed can't be multiple the CH_BANDWIDTH statement parameters with different values when transmitting a MU PPDU. However, the TXVECTOR does not allow for multiple CH_BANDWIDTH parameters (this parameter is not flaged as 'MU' in the TXVECTOR column) and the PHY doesnt support it. 2679 Kim, 73 17 T There is only one Agree in principle. CH_BANDWIDTH parameter (common to all users) in Removed TXVECTOR even in the case of MU-MIMO TX. statement Hence, CH_BANDWIDTH parameter is inherently the same for all users in a PPDU. Discussion Agree. In Table 22-1 (TXVECTOR and RXVECTOR parameters), there is only one CH_BANDWIDTH parameter in TXVECTOR even in case of MU-MIMO transmission. Therefore, CH_BANDWIDTH parameter is the same for all users in MU-MIMO PPDU and the statement is not needed. Proposed resolution:
If the BSSBasicRateSet parameter the BSSBasicMCSSet parameter are empty (e.g., a scanning STA that is not yet associated with a BSS), the frame shall be transmitted in a non-HT PPDU using one of the mandatory PHY rates. Proposed resolution: See CID 3182 (11/1144r8). No change is necessary to D1.2 text. Comments (CID 3486, 2679 – COEX) 3486 73 17 T This statement is not needed. I think what it says is that there can't be multiple CH_BANDWIDTH parameters with different values when transmitting a MU PPDU. However, the TXVECTOR does not allow for multiple CH_BANDWIDTH parameters (this parameter is not flaged as 'MU' in the TXVECTOR column) and the PHY doesnt support it. Remove statement. Agree. Removed the statement 2679 Kim, 73 17 T There is only one CH_BANDWIDTH parameter (common to all users) in TXVECTOR even in case of MU-MIMO TX. Hence, CH_BANDWIDTH parameter is inherently the same for all users in a PPDU. Agree in principle. Removed the statement Discussion Agree. In Table 22-1 (TXVECTOR and RXVECTOR parameters), there is only one CH_BANDWIDTH parameter in TXVECTOR even in case of MU-MIMO transmission. Therefore, CH_BANDWIDTH parameter is the same for all users in MU-MIMO PPDU and the statement is not needed. Proposed resolution:
11-11-1467-00-00ac-d1-0-comment-resolutions-on-miscellaneous-coex-and-mac-cids.docx