Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGBN] Further Discussion on 26/302



Typo.

 

From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Sent: Monday, April 27, 2026 12:25 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Further Discussion on 26/302

 

Hi Sherief,

 

 

I have the following suggestions:

 

  • Align with the EMLSR transition rules section in baseline and make it clear that STAs only care about the CF-end seen from their associated AP i.e., do not introduce any additional logic for STAs that requires them to trust a CF-end not sent by their own AP for this termination purpose. For example,

 

“(#6530)  The non-AP MLD may be switched back to the listening operation on the EMLSR link(s) after the

EMLSR transition delay time most recently indicated by the non-AP MLD if the MAC of the non-AP STA affiliated with the non-AP MLD is applying the extended timeout period and has received the CF-End frames from their associated AP The non-AP MLD STA(s) associated with the coordinating AP or the coordinated AP, and that is applying the extended timeout period may interrupt that extended timeout period and switch to either LC mode for DPS STAs or listen mode for EMLSR STAs after the EMLSR transition delay time most recently indicated by the non-AP MLD once they receive any of the CF-End frames from their associated AP.”

 

Add similar line for HC to LC transitions or append the above to cover that case.

 

  • Have an explicit text about what AP considers the STAs’ EMLSR mode to be after sending the CF-end so there is no ambiguity resulting in diminished EMLSR performance for STAs. For example,

 

“The AP MLD considers an associated non-AP MLD to have switched back to the listening operation on the EMLSR link(s) after the

EMLSR transition delay time indicated by the non-AP MLD following the transmission of the CF-end frame by an AP affiliated with the AP MLD”

 

Regards,

Dibakar

 

 

 

From: Sherief Helwa <00002dded7ae4daf-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, April 21, 2026 6:28 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] Further Discussion on 26/302

 

Hi CoBF/CoSR PoCs and TTTs,

 

Thanks for the feedback you all provided on 26/302. I wanted to initiate this thread to summarize the feedback and explore possible ways forward.

 

In this CR document, we proposed a signaling scheme to help eMLSR/DPS STAs switch back to listen/LC mode earlier at the end of CoBF/CoSR TXOPs. The main idea was to achieve this using a baseline scheme/frame with minimal changes to the current spec.

 

The proposed scheme can be summarized in 3 points:

  • The coordinating AP shall transmit a CF-End frame to end the CoBF sequence.
  • The coordinated AP may transmit a CF-End frame following that of the coordinating AP.
  • The non-AP STA may switch back immediately once receiving any of the CF-End frames.

 

The majority of feedback I received can be summarized under two directions:

  • Some members recommended stronger language on the coordinated AP à Use a “shall” condition.
  • Some members recommended softer language on the coordinating AP à Use a “should” condition.

 

As it is clear, the recommendations are conflicting, hence I suggest that we find a middle ground where it is mandated with a “shall” on the coordinating AP while keeping the flexibility on the coordinated AP with a “may”.

 

 

Please let me know your thoughts.

 

Regards,

Sherief


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


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