| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
HI all,
I've added more remaining CIDs in r5 of the CR, starting on page 6 - a couple about ST prep that were already resolved in D1.5 and a few about renegotiation (all resolved as "Revised" now) that were addressed by Giovanni's CR (11-26/0060r6) SP'ed earlier this
morning. I've also deferred the CID for the NOTE being discussed here.
Could you please check and let me know if you have any questions or comments?
Thanks,
Duncan
From: Duncan Ho <00002b3e54cff3e2-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, July 15, 2026 6:15 AM To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx> Subject: Re: [STDS-802-11-TGBN] Please review - the last few seamless roaming CIDs WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Guogang,
Thanks for the clarification and understood now. Let's work on the text more then.
BR,
Duncan
From: huangguogang <huangguogang1@xxxxxxxxxx>
Sent: Wednesday, July 15, 2026 5:33 AM To: Duncan Ho <dho@xxxxxxxxxxxxxxxx>; Pooya Monajemi <p_monajemi@xxxxxxxxx> Cc: stds-802-11-tgbn@xxxxxxxxxxxxxxxxx <stds-802-11-tgbn@xxxxxxxxxxxxxxxxx> Subject: 回复: [STDS-802-11-TGBN] Please review - the last few seamless roaming CIDs WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Duncan,
Good question!
In my understanding, the data forwarded from the current AP MLD to the target AP MLD is also from the DS. I’m not sure whether ‘the data from the DS’ can be used to differentiate ‘the data forwarded from the current AP MLD’. Maybe this description not accurate.
For the green part of the text, maybe we need to add another condition, e.g. the DL data forwarding is not supported. Maybe we need to have more discussion and improve the wording.
Regards Guogang Huang 发件人: Duncan Ho <dho@xxxxxxxxxxxxxxxx>
Hi Guogang,
Thanks for the discussion. If we remove the "from the DS" part, does that mean if there are forwarded DL packets to the target AP MLD, the target AP MLD cannot transmit those MSDUs/A-MSUDs until the target receives the Notify drain termination?
Thanks, Duncan
From: huangguogang <huangguogang1@xxxxxxxxxx>
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Pooya,
I’m not sure. What do you think about the following text?
"NOTE1 — If the amount of buffered or anticipated additional DL data in the current AP MLD for a TID exceeds the
block ack window size during the DL draining period, the next SN to be assigned for DL individually addressed Data frames (during context transfer) might be outside the non-AP STA's block ack window, in which case the target AP MLD will not be able to transmit
the new MSDUs/A-MSDUs "NOTE2 — If the amount of buffered or anticipated additional DL data in the current AP MLD for a TID exceeds the block ack window size during the DL draining period, the next SN to be assigned for DL individually addressed Data frames (during context transfer) might be rolled-over and within the non-AP STA's block ack window, in which case the current AP MLD needs to inform the target AP not to transmit the new MSDUs/A-MSDUs to the non-AP MLD until receiving from the non-AP STA a UHR Link Reconfiguration Notify frame with the Type field set to 2 and the DL Draining Completed field set to 1."
Regards Guogang Huang 发件人: Pooya Monajemi <p_monajemi@xxxxxxxxx>
Hi Guogang, thanks for the explanation. We should be able to add a clarification to handle the rollover case, do you have any suggestion for the text
Thanks Pooya
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 |