Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Jinyoung, Thank you for your suggestion. “feedback-requested RU/MRU size” does not sound grammatically correct. How about using “feedback RU/MRU size” as indicated in Table 9-42c? The revised sentence is given
as follows: The EHT beamformer shall set the TXVECTOR parameter CH_BANDWIDTH or CH_BANDWIDTH_IN_NON_HT, the Partial BW Info subfield of the EHT NDP Announcement frame, depending on the operating channel width
of the beamformee, the operating channel width of the beaformer or the feedback RU/MRU size, as defined in Table 9-42c (Settings for BW, Partial BW Info subfield in the EHT NDP Announcement frame(#8157)). Thanks, Zinan From: Jinyoung Chun <jiny.chun@xxxxxxx>
Hi Zinan, Thank you for your comment. Basically I agree with you. And how about ‘feedback-requested RU/MRU size’ instead of ‘requested RU/MRU size’ for more clarification? Best regards, Jinyoung From: Zinan Lin [mailto:Zinan.Lin@xxxxxxxxxxxxxxxx]
Resend the email to fix the format issue: Hi Jinyoung, Thanks for discussing CID 8370 in 11-21/2014r1. I have one comment on the sentence (P294L56 in 802.11be D1.0 which is in P430L27 in 802.11be D1.4): The EHT beamformer shall set the TXVECTOR parameter CH_BANDWIDTH or CH_BANDWIDTH_IN_NON_HT, the Partial BW Info subfield of the EHT NDP Announcement frame, depending on
the operating channel width, as defined in Table 9-42c (Settings for BW, Partial BW Info subfield in the EHT NDP Announcement frame(#8157)). I do not think the operating channel width is clearly stated. The value of the bandwidth of the EHT NDPA Announcement frame, i.e., the TXVECTOR parameter CH_BANDWIDTH or CH_BANDWIDTH_IN_NON_HT, depends on different parameters in different
scenarios:
Therefore, I would suggest to re-write the sentence as follows: The EHT beamformer shall set the TXVECTOR parameter CH_BANDWIDTH or CH_BANDWIDTH_IN_NON_HT, the Partial BW Info subfield of the EHT NDP Announcement frame, depending on the operating channel
width of the beamformee, the operating channel width of the beaformer or the requested RU/MRU size, as defined in Table 9-42c (Settings for BW, Partial BW Info subfield in the EHT NDP Announcement frame(#8157)). Thanks, Zinan From: Zinan Lin <Zinan.Lin@xxxxxxxxxxxxxxxx>
Hi Jinyoung, Thanks for discussing CID 8370 in 11-21/2014r1. I have one comment on the sentence (P294L56 in 802.11be D1.0 which is in P430L27 in 802.11be D1.4): The EHT beamformer shall set the TXVECTOR parameter CH_BANDWIDTH or CH_BANDWIDTH_IN_NON_HT, the Partial BW Info subfield of the EHT NDP Announcement frame, depending on
the operating channel width, as defined in Table 9-42c (Settings for BW, Partial BW Info subfield in the EHT NDP Announcement frame(#8157)). I do not think the operating channel width is clearly stated. The value of the bandwidth of the EHT NDPA Announcement frame, i.e., the TXVECTOR parameter CH_BANDWIDTH or CH_BANDWIDTH_IN_NON_HT, depends on
different parameters in different scenarios:
Therefore, I would suggest to re-write the sentence as follows: The EHT beamformer shall set the TXVECTOR parameter CH_BANDWIDTH or CH_BANDWIDTH_IN_NON_HT, the Partial BW Info subfield of the EHT NDP Announcement frame, depending on the operating channel
width of the beamformee, the operating channel width of the beaformer or the requested RU/MRU size, as defined in Table 9-42c (Settings for BW, Partial BW Info subfield in the EHT NDP Announcement frame(#8157)). Thanks, Zinan To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |