Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Abhi, I support to specifically call out the form.
For me, this is important because “STA” in the baseline are often used when it applies to both AP and non-AP STAs. If we are talking about “non-AP MLD”, then the affiliated STA is “non-AP STA”. I will also provide another experience that I have during 11ax days. 11ax introduces Trigger frame and Trigger frame can only be sent by AP and triggered non-AP STA. For this specific technical reason, we call out AP/non-AP STA in basically all the places to clarify this confusion rather
than just using “STA” and using the fact that we only have Trigger frame sent from AP to take care of this.
Best, Po-Kai From: M Montemurro <montemurro.michael@xxxxxxxxx> Hi Abhi, Thanks. For MLO according to the state machines defined in clause 11.3, connectivity state is established between a non-AP MLD and an AP MLD. These entities communicate over links between an affiliated STA and affiliated AP. Yes this phraseology is used throughout TGbe but I'd like those commenting on the ambiguity to review the draft and call out specific locations where the meaning is ambiguous. Perhaps we could address those areas where the context isn't clear. Thanks, Mike On Thu, Aug 11, 2022 at 1:00 PM Abhishek Patil <appatil@xxxxxxxxxxxxxxxx> wrote:
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 |