| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Best Regards,
Hi You-weiThanks for your efforts in resolving these comments. Regarding the comment in CID 4484, I have some questions.1. I not sure whether the problem “ In the TxOP containing a pair of UHT Co-BF BFer, if the preceding frames (e.g. Co-BF inviate/response, NDPA, NDP...) do not carry Duration/ID field to cover the BFRP Trigger frame, the BFPR Trigger will typically need carry Duration/ID field upto the end of the TxOP according to the exsiting multiple protection rule......” does exist. According to Clause 9.2.5.2 ("Setting for single and multiple protection under enhanced distributed channel access (EDCA)"), the Duration field value is merely defined as a range, rather than a mandatory fixed endpoint.And if this problem does exist, we may also need to consider the NAV setting of the following frames: BFRP Trigger frames transmitted by AP2 during the sequential NDP sounding initiated by AP1, as well as BFRP Trigger frames transmitted within the duration granted by AP1.2. In addition, I find the proposed Note somewhat unclear: "The NAV set by the Co-BF sounding initiating AP might not cover the UHR Co-BF sounding sequence initiated by the Co-BF sounding responding AP." The issue is that the baseline specification never explicitly states that the NAV set by the Co-BF sounding initiating AP does cover the sounding sequence initiated by the responding AP. Without such an affirmative statement, a Note saying it "might not" cover seems logically unmotivated. Perhaps " ... might cover or not cover .... " is better.3. By the way, I still recommend reconsidering the NAV setting in this scenario, because the sounding process initiated by AP2 may not be well protected without another Co-BF sounding invite or response, especially with regard to frames such as the NDPA sent by AP1.OriginalFrom: You-WeiChen <ywchen77115@xxxxxxxxx>Date: 2026年05月09日 02:31Subject: Re: [STDS-802-11-TGBN] CRs for subclause 37.13 (Co-BF sounding)Dear all,
Thanks for the comments and suggestions. I uploaded 26/847r2. The changes are highlighted in blue.
There are some clarification questions. I draft a figure at the end of the draft for visualization.
Best Regards,
You-Wei ChenYou-Wei Chen <ywchen77115@xxxxxxxxx> 於 2026年5月7日週四 下午10:07寫道：Dear all,Thanks for suggestions. I uploaded 26/847r1. The changes are highlighted in yellow.
2026 847 1 TGbn LB291 CRs for subclause 37.13.3-part2 You-Wei Chen (Mediatek) Download
Best Regards,
You-Wei ChenYou-Wei Chen <ywchen77115@xxxxxxxxx> 於 2026年5月7日週四 上午10:01寫道：Dear all,Below are CRs for subclause 37.13.Please let me know if any comments or suggestions. Many thanks.
2026 849 0 TGbn LB291 CRs for subclause 37.13.5-part3 You-Wei Chen (Mediatek) Download 2026 848 0 TGbn LB291 CRs for subclause 37.13.4-part3 You-Wei Chen (Mediatek) Download 2026 847 0 TGbn LB291 CRs for subclause 37.13.3-part2 You-Wei Chen (Mediatek) Download 2026 846 0 TGbn LB291 CRs for subclause 37.13.2-part2 You-Wei Chen (Mediatek) Download 2026 845 0 TGbn LB291 CRs for subclause 37.13.1-part2 You-Wei Chen (Mediatek) Download
Best Regards,
You-Wei ChenTo unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1