| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Dear Seamless Roaming TTT members, I’ve uploaded a new version (11-25/1993r1)
based on comments. Please review and share any feedback in this email thread. Regards 发件人: huangguogang
Hi Ryuichi, Thanks for your comments. Please find my response inline. Regards Guogang Huang 发件人:
Ryuichi.Hirata@xxxxxxxx [mailto:Ryuichi.Hirata@xxxxxxxx]
Hi Guogang, Thank you for preparing a document. For signaling forwarding capability, do we need to inform the type of DL Data Forwarding (whether it's only MSDUs or not) in the SMD Information element? [HGG]The non-AP MLD’s behaviors are different under these two DL data forwarding types. Specifically, the non-AP MLD shall
discard the subsequent MSDUs/A-MSDUs behind a hole if only MSDU forwarding is supported. If the A-MSDU forwarding is supported, the non-AP MLD needs to keep its reordering buffer when all the links with the current AP MLD are removed.
If necessary, could we consider increasing the DL Data Forwarding bit from 1 to 2? This way, we wouldn't need the sentence stating, "The DL Data Forwarding field and the Simplified DL Data Forwarding field in the SMD Information element shall not
be simultaneously set to 1." [HGG] I’m not sure whether it’s good to change the existing signaling format at this stage. But I’m open to further discussion.
For the description of "37.16.10 Downlink Data forwarding", is the resolution for #5021 only applied when the DL Data Forwarding field is set to 1 and A-MSDU forwarding will occur? [HGG] The resolution for CID 5021 is applied to both of these two cases. Based on the current Spec., individually addressed
MSDUs with the same TID value and addressed to the same destination shall not be reordered. The essence of this ‘shall’ requirement is MSDUs generated from a traffic stream shall be in-order delivery, i.e. the same order of the data delivery to the next MAC
process of the receiver as the one arrived at the MAC SAP of the transmitter (regardless it is the current AP MLD or the target AP MLD). Best regards, Ryuichi 差出人: huangguogang <000017b1384624cd-dmarc-request@xxxxxxxxxxxxxxxxx> Dear Seamless Roaming TTT members, I’ve
prepared a CR document to address the comments on the data forwarding. Please review and share any feedback in this email thread. 11-25/1993: LB291 CR for data forwarding (6 CIDs) Regards Guogang Dear Seamless Roaming TTT members, I’ve prepared a CR document to address the
comments on the data forwarding.
Please review and share any feedback in this email thread.
Regards Guogang Huang 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 |