Hi Jarkko,
Thank you for your email. As I stated in my previous email, the text is not proposing any new rules. The clarification
consistent with what is already there in the TGbe draft (since D2.3).
I received additional offline feedback from a couple of members and based on their inputs, the NOTE (see inline
below) is tweaked a bit to better align with the existing rules in the draft.
Regards,
Abhi
From: Jarkko Kneckt <jkneckt@xxxxxxxxx>
Sent: Thursday, August 24, 2023 3:49 PM
To: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Resolution for CID 19792
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Abhi,
Thank you for opening the discussion.
This R-TWT schedules parsing from Multiple-BSSID Beacon is complicated (in my mind).
Do I understand correctly, that all R-TWT schedules are listed in the Transmitted BSS? And additionally there is also possibility that R-TWT streams are present in the non-transmitted BSSID. The R-TWT streams present in non-transmitted
BSSID are only known by the STA associated with the non-transmitted BSS, right?
To me it sounds that the R-TWT streams are listed in two locations and I do not understand the reason why they should be listed in multiple locations. I would list the r-TWT schedules only in transmitted BSS.
We discussed the resolution for CID 19792 during this morning’s TGbe joint call and there was a request to defer the resolution so that members could review it offline. I am initiating this email as a follow-up and to answer any questions
members may have.
The resolution is not proposing anything new. The text is consistent with the rules in clause 35.3.8.4 (see below snippet). The current spec states that an rTWT capable non-AP STA that is associated with a nonTxBSSID determines the rTWT
schedule of all the APs in the set by parsing the TWT IE carried in the TxBSSID’s Beacon/Probe. As a result, the proposed text is clarifying that the baseline inheritance rule will not apply to the TWT IE carried outside the MBSSID IE.
I have copied the proposed text to help with your review. I made a couple of minor tweaks based on offline feedback:
An R-TWT scheduled STA (see 35.8.1) that is associated with an AP corresponding to the nontransmitted BSSID in a multiple BSSID set shall not apply inheritance rules specified
in 11.1.3.8.4 to the TWT element(s) carried outside the Multiple BSSID element in a Beacon frame or a Probe Response frame transmitted by the AP corresponding to the transmitted BSSID in the same multiple BSSID set.
NOTE: An R-TWT scheduled STA that is associated with any AP in a multiple BSSID set determines the R-TWT schedule(s) belonging to other APs in the same multiple BSSID set by parsing the R-TWT
parameter set(s) carried within the TWT element(s) outside the Multiple BSSID element (see 35.8.4.1).
Please let me know if you have any suggestions to improve the above text.
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
|