| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Abhi, No need for an ML element when receiving a beacon to know that the AP is part of an AP MLD, the RNR is already doing this. There are clear motions on the conditions for which ML element is present in beacons (for SAE to provide MLD MAC address). For other cases and before we generalize, we need further discussions. The first motion you refer below is not about ML element, it talks about partial information in a very general manner. Partial info in that motion actually is the RNR (and the MAC address in ML in some cases: SAE). Second motion is about defining the mechanism to provide info, not the rule if this is always included or not. Thanks, Laurent From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx> Hi Laurent, Young Hoon,
Regarding presence of ML IE in Beacon frame, I received offline feedback from a few members asking me to include ML IE in Beacon and Probe Response frames to aid the discovery
of an MLO AP. Further, I found we have two motions that support it:
·
Partial information to prevent frame bloating.
·
For example, frames exchanged during ML setup are expected to carry complete information
while Beacon frame is expected to carry partial information.
·
The exact set of elements/fields that constitute partial information is TBD.
[Motion 115, #SP93, [14] and [115]] 802.11be defines mechanism(s) to include MLO information that a STA of an MLD provides in its mgmt. frames,
during discovery and ML setup, as described below:
·
MLD (common) Information
o
Information common to all the STAs of the MLD.
·
Per-link information
o
Capabilities and Operational parameter of other STAs of the MLD other than the advertising STA.
[Motion 115, #SP91, [10] and [93]] Regards, From: Cariou, Laurent <laurent.cariou@xxxxxxxxx>
CAUTION: This email originated from outside of
the organization. Thanks Abhi, Still a few comments attached. Best Laurent From: Young Hoon Kwon <younghoon.kwon@xxxxxxx>
Hi Abhi, I have some comments on the text as attached. Thanks, Young Hoon From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Caution: EXT Email
Hi All,
https://mentor.ieee.org/802.11/dcn/20/11-20-1274-03-00be-mac-pdt-mlo-ml-ie-structure.docx Regards, Abhi From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Hi All, I’ve posted r2 which incorporates feedback from Laurent and Jay. https://mentor.ieee.org/802.11/dcn/20/11-20-1274-02-00be-mac-pdt-mlo-ml-ie-structure.docx Regards, From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
CAUTION: This email originated from outside of
the organization. Hi All, I have revised my PDT doc (on ML IE) based on feedback received so far.
https://mentor.ieee.org/802.11/dcn/20/11-20-1274-01-00be-mac-pdt-mlo-ml-ie-structure.docx Could you please review and let me know if you have any further inputs? Regards, Abhi From: Abhishek Patil Hello to all TTT members for MLO Discovery: ML IE Structure, I have posted document 11-20/1274 which provides draft text for MLO power save procedures. https://mentor.ieee.org/802.11/dcn/20/11-20-1274-00-00be-mac-pdt-mlo-ml-ie-structure.docx Could you please review and let me know if you have any inputs? Regards, 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 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 |