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

Re: [STDS-802-11-TGBE] [EXT] [STDS-802-11-TGBE] Reassociation



Hi Young Hoon,

 

Thanks for the clarification! I assumed resetup with same AP MLD meant changing the set of setup links (e.g. removing a link due to out of coverage).

 

In your below example, I am not sure if it can be considered resetup as establishing separate associations does not retain multi-link operation.

 

Thanks,

Sharan

 

From: Young Hoon Kwon [mailto:younghoon.kwon@xxxxxxx]
Sent: Thursday, June 4, 2020 11:07 PM
To: Sharan Naribole <n.sharan@xxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [EXT] [STDS-802-11-TGBE] Reassociation

 

Hi Sharan,

 

Thank you very much for your comment.

I agree with you that if a non-AP MLD just wants to disable a link, it’s better to go through TID-link remapping process instead of resetup/reassociation process.

The reason I mentioned resetup was that the example mentioned was not just disabling a link but instead a non-AP MLD switches from a single multi-link setup to two separate associations (one association on 2.4GHz, and another association on 5/6GHz).

 

Best,

Young Hoon

 

From: Sharan Naribole <n.sharan@xxxxxxxxxxx>
Sent: Thursday, June 4, 2020 8:33 PM
To: Young Hoon Kwon <younghoon.kwon@xxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [EXT] [STDS-802-11-TGBE] Reassociation

 

Hi Young Hoon,

 

Thanks for your contribution!

 

In this case of “resetup” with same AP MLD, the overhead involved in ML teardown and ML resetup including all the agreements would be significant and is concerning from non-AP point of view. It would be better for non-AP MLD to initiate disabling of that link instead and possibly no “negotiation” overhead in such an update.

 

Thanks,

Sharan

 

From: Young Hoon Kwon [mailto:younghoon.kwon@xxxxxxx]
Sent: Thursday, June 4, 2020 8:21 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] [EXT] [STDS-802-11-TGBE] Reassociation

 

Hi Tomo,

 

Thank you very much for the clarification!

 

Best regards,

Young Hoon

 

From: Tomo Adachi <tomo.adachi@xxxxxxxxxxxxx>
Sent: Thursday, June 4, 2020 7:42 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [EXT] [STDS-802-11-TGBE] Reassociation

 

Caution: EXT Email

 

Hi all,

 

There was a question during Q&A on 20/386 whether BA agreements are valid and no re-setup is required after reassociation.

 

In REVmd D3.0, 11.3.5.4, it says the following:

If the MLME-REASSOCIATION.request primitive has the new AP’s or PCP’s(#2582) MAC address in the CurrentAPAddress parameter (reassociation to the same AP or PCP(#2582)), the following states, agreements and allocations shall be deleted or reset to initial values:

1) All EDCAF state

2) Any block ack agreements that are not GCR agreements(#2228)

 

Best regards,

tomo

 


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


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


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