legacy PPDU behaviour that is described in the baseline. TGax editor makes changes as shown in 11-17/1286r0 that are marked with CID 4801. 4802 Alfred It seems BQR Trigger As in Rejected- Asterjadhi frame is not allowed comment. in the A-MPDU The purpose of BQR is for AP content (See 9.7.3). I to learn the channel don't think it is the availability of the STAs to case. Please amend help the following DL or UL to fix the data transmission. inconsistency. Aggregating BQR with data doesn’t provide benefits while complicating the implementation. TGax editor no changes on CID 4802. 4803 Alfred This is a way to As in Revised- Asterjadhi say that reception of comment. the BQR Trigger Agree in principle. frames is optional. Find a less weird way TGax editor makes changes to say the same. as shown in 11-17/1286r0 that are marked with CID 4803 4804 Alfred QoS Data cannot be As in Rejected- Asterjadhi added because the comment. BQR variant Trigger Control when aggregatd frame does not have in an A-MPDU doesn’t need TID AGG limit and to comply the MU Minimum MU Minimum Start Start Spacing requirement. Spacing indications, TID AGG limit only apply etc. Please remove multi-TID aggregation. QoS Data from the sentence. Also no TGax editor makes no need to indicate that changes on this CID. "when the AP has indicated its support in the A-BQR Support... because the AP sends the BQR variant Trigger frame only if it supports Rx of the info. 5179 Dorothy Regarding "Downlink make field Revised- Stanley MU-MIMO On Partial naming Bandwidth Rx", consistent Agree in principle. Per Figure 9-589cl and proposed resolution of CID Table 9-262aa have 4804, this sentence will be "DL MUMIMO On removed. Partial Bandwidth" TGax editor makes changes as shown in 11-17/1286r0
legacy PPDU behaviour that is described in the baseline. TGax editor makes changes as shown in 11-17/1286r0 that are marked with CID 4801. 4802 Alfred Asterjadhi It seems BQR Trigger frame is not allowed in the A-MPDU content (See 9.7.3). I don't think it is the case. Please amend to fix the inconsistency. As in comment. Rejected- The purpose of BQR is for AP to learn the channel availability of the STAs to help the following DL or UL data transmission. Aggregating BQR with data doesn’t provide benefits while complicating the implementation. TGax editor no changes on CID 4802. 4803 Alfred Asterjadhi This is a way to say that reception of the BQR Trigger frames is optional. Find a less weird way to say the same. As in comment. Revised- Agree in principle. TGax editor makes changes as shown in 11-17/1286r0 that are marked with CID 4803 4804 Alfred Asterjadhi QoS Data cannot be added because the BQR variant Trigger frame does not have TID AGG limit and MU Minimum Start Spacing indications, etc. Please remove QoS Data from the sentence. Also no need to indicate that "when the AP has indicated its support in the A-BQR Support... because the AP sends the BQR variant Trigger frame only if it supports Rx of the info. As in comment. Rejected- Control when aggregatd in an A-MPDU doesn’t need to comply the MU Minimum Start Spacing requirement. TID AGG limit only apply multi-TID aggregation. TGax editor makes no changes on this CID. 5179 Dorothy Stanley Regarding "Downlink MU-MIMO On Partial Bandwidth Rx", Figure 9-589cl and Table 9-262aa have "DL MUMIMO On Partial Bandwidth" make field naming consistent Revised- Agree in principle. Per proposed resolution of CID 4804, this sentence will be removed. TGax editor makes changes as shown in 11-17/1286r0