Re: [STDS-802-11-TGBE] CR doc 22/1838r5

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

Hi Arik,

Thanks for your comments.

I had further offline discussions with Pooya, Vishnu, Abhi and Po-kai and have revised the text as below, clarifying that the text is applicable only for TID-To-Link Mapping Negotiation Support subfield value 1 (as per the scope in D2.3). The point of the NOTE is to clarify that if all TIDs are mapped to more than one link, then after a setup link is removed, all TIDs are still mapped to at least one setup link, so both AP MLD and non-AP MLD shall continue to operate with that mapping on remaining setup links (as captured by the Otherwise condition).

(#10021) If a non-AP MLD supporting TID-To-Link Mapping Negotiation Support subfield value 1 removes a setup link locally from its multi-link setup as a result of the removal of an AP affiliated with its associated AP MLD, and the removed link was the only link which had all the TIDs mapped in both UL and DL, then the non-AP MLD and the AP MLD shall operate with all TIDs mapped to all remaining setup links (if exists) in both UL and DL, excluding any link(s) disabled by the Advertised TID-to-Link mapping (clause 35.3.7.1.7), until a new TID-to-link mapping is established. Otherwise, for that non-AP MLD, both the AP MLD and the non-AP MLD shall continue to operate based on the currently established TID-to-Link mapping on the remaining setup links, after removal of the setup link.

(#10021) NOTE: If a non-AP MLD supporting TID-To-Link Mapping Negotiation Support subfield value 1 has all TIDs mapped to more than one setup links and removes a setup link locally from its multi-link setup as a result of the removal of an AP affiliated with its associated AP MLD, all the TIDs are still mapped to another setup link for that non-AP MLD since the non-AP MLD had all TIDs mapped to multiple setup links before removal of the setup link.

Hope this addresses your comment.

All, please let me know if you have any further comments on this CID or any other CID in 22/1838r5 attached.

Thanks,

Binita

From: Arik Klein <arik.klein@xxxxxxxxxx>
Sent: Wednesday, January 11, 2023 1:56 PM
To: Binita Gupta <binitagupta@xxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: CR doc 22/1838r5

Hi Binita, Thanks for sharing the updated doc. Regarding the Note below (cited here for convenience): (#10021) NOTE: If a non-AP MLD which has more that one enabled links removes a setup link from its multi-link setup as a result of the removal

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

ZjQcmQRYFpfptBannerEnd

Hi Binita,

Thanks for sharing the updated doc.

Regarding the Note below (cited here for convenience):

(#10021) NOTE: If a non-AP MLD which has more that one enabled links removes a setup link from its multi-link setup as a result of the removal of an AP affiliated with its associated AP MLD, then all the TIDs which were mapped to the removed link are also mapped to another setup link, since TID-To-Link Mapping Negotiation Support subfield can only be set to 1.

Can you clarify the above highlighted sentence, in case that there are 3 enabled links between the non-AP MLD and the AP MLD and one link is removed as a result of the affiliated AP removal, for which of the “another setup link” the TIDs are mapped (there are 2 remaining links)?

Maybe consider rephrasing to “then all the TIDs which were mapped to the removed link are ~~also~~ mapped to all remaining setup links, since TID-To-Link Mapping Negotiation Support subfield can only be set to 1”

Please let me know if you are OK with the suggested text above.

Another editorial comment: in the first sentence, please replace “that” with “than” in the sentence “(#10021) NOTE: If a non-AP MLD which has more that one enabled links removes a setup link from its multi-link setup..”

Regards,

Arik

From: Binita Gupta <00001d96db2c011d-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: יום ד 11 ינואר 2023 23:28
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] CR doc 22/1838r5

Hi all,

I presented CR doc 22/1838r4 in MAC Ad-hoc AM1 session. I received online and further offline feedback on resolution for CID 10021. Vishnu mentioned that TID-To-Link Mapping Negotiation Support subfield can not be set to 3 per current draft text approved in Bangkok meeting.

“An MLD (#10213)shall not set the (#14054)TID-To-Link Mapping Negotiation Support subfield of MLD
Capabilities field of the Basic Multi-Link element to 3.”

I have updated resolution to account for that in the proposed text below.

(#10021) If a non-AP MLD removes a setup link from its multi-link setup as a result of the removal of an AP affiliated with its associated AP MLD and that was the only link which had all the TIDs mapped in both UL and DL (for TID-To-Link Mapping Negotiation Support subfield value 1), then the non-AP MLD and the AP MLD shall operate with all the TIDs mapped to all remaining setup links (if exists) in both UL and DL, excluding any link which has been disabled by the Advertised TID-to-Link mapping by the AP MLD.

Please let me know if you have any further comments.

@Alfred, @Liwen – could you please reschedule CR doc 22/1838r5 for running SP in MAC Ad-hoc.

Thanks,

Binita

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