Hi All,
I had presented doc 11-20/0356 during last week’s 11be call and deferred the SPs for further discussion.
I have made a few updates to the SPs based on offline feedback that I receive so far.
Could you please take a look at the revised SPs and let me know if you have additional feedback/suggestions?
SP1:
- Do you agree to define mechanism(s) to include MLO information that
a STA an AP of an MLD provides in its mgmt. frames, during discovery and ML setup, as described below?
- MLD (common) Information
- Information common to all the STAs of the MLD
- Per-link information
- Capabilities and Operational parameter of other STAs of the MLD other than the advertising STA
SP2:
- Do you support that the MLO framework should follow an inheritance model to prevent frame bloating when advertising complete information of other links?
- Note: inheritance mechanism is similar to that defined in 11ax for multiple BSSID feature
- For example, if an element is not carried in the profile for a link, the value of the element is the same as that of the advertising link
SP3:
- Do you support that an AP of an AP MLD may advertise complete or partial information of other links when possible?
- 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
- Exact content of partial information is TBD
SP4:
- Do you support that a STA of non-AP MLD shall include in its Probe Request an indication that it supports MLO operation?
- Note: Exact signaling TBD
SP5:
- Do you support that an AP of an AP MLD shall include MLO information when responding, with an individually addressed Probe Response frame, to a Probe Request frame from a non-AP STA that has indicated
support for MLO?
Regards,
Abhi
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
|