Hi all,
As promised, I open this thread if there are questions on the inheritance rules defined as in 390r3 for an ML element (used in association frame for instance).
Let me know if there are questions.
- Do you agree to define a new Multi-Link element (MLE) to report/describe multiple STAs of an MLD with at least the following characteristics?
- MLD-level information may be included
- A STA profile subelement is included for each reported STA (if any) and is made of a variable number of elements describing this STA
- SP2
- Do you support that, for the ML element, we define an inheritance model to prevent frame bloating when advertising complete information of other links?
- Define the inheritance mechanism, similar to 11ax, so that the value of an element of a reported STA that is not present in a STA profile of a ML element in a frame sent by a reporting STA is the same as
the element of the reporting STA, present elsewhere in the frame.
- Define the inheritance mechanism, similar to 11ax, so that the value of an element of a reported STA that is not present in a STA profile of a ML element included in a non-transmitted BSSID profile of a
non-transmitted BSSID in a multiple BSSID element in a frame sent by a reporting STA is the same as the element of the non-transmitted BSSID, present elsewhere in the frame or as the element of the reporting STA, present elsewhere in the frame.
- Note: an “element of a STA” refers in the text above to the instance of the element describing the capabilities/operation/functionalities of that STA, in a frame where multiple instances of the element can
be found for other STAs.
- Note: some elements may not be inherited, signaling TBD
Thanks
Laurent
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
|