| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hello Pooya. To give a brief history on how we came up with the Collocated AP MLD Set, in roaming, we consider a case where the non-AP STA roams between the AP MLDs that are not co-located. Therefore, a non-AP STA should be able to identify the AP MLDs that are not co-located and provided by the serving AP MLD.. However, as I mentioned in my contribution (1907), there is no method to identify the AP MLDs that are not collocated. While thinking of the method on the identification of the non-collocated AP MLDs, we also wanted to take the multiple BSSID set case into the consideration as well where the APs affiliated with different AP MLDs included in the same multiple BSSID set. This is the reason that we created a co-located AP MLD set that groups the AP MLDs that are co-located and set an ID to overcome the identification limitation. On the other hand, we do not have a firm opinion on creating the co-located AP MLD set and we are open to roaming between AP MLDs individually. If any of the other members have their thoughts on this, I would be welcomed to hear from you. Best Regards, Yelin Yoon From: Pooya Monajemi [mailto:pmonajemy@xxxxxxxxx] Hello Yelin and thanks again for the contribution. On the question of why we need the definition of a co-located AP MLD set, you mentioned cases where two AP MLDs are co-located and STA is roaming from one to another. I believe today if two co-located APs are advertising the same SSID (~same ESS) they generally belong to the same AP MLD, do you see the case of same SSID on different but co-located AP MLDs today or in future? 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 |