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

Re: [STDS-802-11-TGBN] [EXT] RE: [STDS-802-11-TGBN] MAC PDT 11-26/1765 for subclause 37.17.2.2 (DPS operation for non-AP STAs)



Hi Liwen,

 

Thanks for the deferral.

 

Best regards,

Qing

 

From: Liwen Chu <liwen.chu@xxxxxxx>
Sent: Thursday, October 15, 2026 2:01 PM
To: Qing Xia (Nokia) <qing.xia@xxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: RE: [EXT] RE: [STDS-802-11-TGBN] MAC PDT 11-26/1765 for subclause 37.17.2.2 (DPS operation for non-AP STAs)

 

 

CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.

 

Hi Qing,

 

Thanks. I will defer the CID.

 

Best Regards,

Liwen

 

 

NXP Confidential

From: Qing Xia (Nokia) <qing.xia@xxxxxxxxx>
Sent: Wednesday, October 14, 2026 1:16 PM
To: Liwen Chu <liwen.chu@xxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [EXT] RE: [STDS-802-11-TGBN] MAC PDT 11-26/1765 for subclause 37.17.2.2 (DPS operation for non-AP STAs)

 

Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button

 

Hi Liwen,

 

I would like to further clarify CID 14700, as I may not have fully understood the rejection rationale.

 

  • My understanding is that a BSRP Trigger frame used as an ICF may contain an RA-RU User Info field under the baseline rules.
  • If the rationale refers to a Multi-STA BA transmitted by the AP after the TB PPDU, that is not the BSRP/BSR procedure that CID 14700 is intended to address.
  • If the rejection rationale refers to the Multi-STA BA used as part of the ICF/ICR procedure, the STA’s TB PPDU can itself contain a Multi-STA BA carrying the ICR context. In that case, I am not sure how this addresses the ambiguity caused by the RA-RU User Info field during the HC-to-LC switch-back checking.

 

Would it make sense to explicitly specify that an RA-RU User Info field shall not be considered addressed to a DPS non-AP STA for the purpose of the DPS HC-to-LC switch-back condition?

 

Many thanks,

Qing

 

From: Qing Xia (Nokia)
Sent: Monday, October 12, 2026 11:26 AM
To: Liwen Chu <liwen.chu@xxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBN] MAC PDT 11-26/1765 for subclause 37.17.2.2 (DPS operation for non-AP STAs)

 

Hi Liwen,

 

CID 17067 and CID 14702 are commenting on the same issue. Since CID 17067 has already been scratched out from 11-26/1765, could you please also scratch out CID 14702 from the comment resolution?

 

Thanks,
Qing

 

 

From: Liwen Chu <liwen.chu@xxxxxxx>
Sent: Sunday, October 11, 2026 8:18 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] MAC PDT 11-26/1765 for subclause 37.17.2.2 (DPS operation for non-AP STAs)

 

 

CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.

 

Hi all,

 

Please find the comment resolutions for subclause 37.17.2.2 in 11-26/1765.

https://mentor.ieee.org/802.11/dcn/26/11-26-1765-00-00bn-lb296-subclause-37-17-2-2-cids.docx

If you have comments, please let me know.

 

Hi Alfred,

 

Please add it to the agenda.

 

Best Regards,

Liwen

 

 

 

NXP Confidential


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