Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGBE] 11-21/1591 (Multi-link association terminology)

Hi all – appreciate your feedback on this document (support, or no support with reasons) to help march toward the straw poll.

Summary table from the document is copied below. Thanks.



Draft 1.1 term

Proposed term

Examples of text change (Draft 1.1)

multi-link setup


(when referring to the procedure)

“multi-link association”, or,


“multi-link association procedure” if there is need to emphasize the procedure (the same as how “association procedure” is used in baseline)



The Link ID subfield of the STA Control field of the Per-STA Profile subelement for the corresponding non-AP STA that requests a link for multi-link setup association with the AP MLD is set to the link ID of an AP MLD that is operating on that link. The link ID is obtained during discovery.




The main MAC features in an EHT STA that are not present in HE STA or VHT STA or HT STA are the following:

—Mandatory support for GCMP-256

—In an MLD, mandatory support for multi-link discovery procedure

—In an MLD, mandatory support for multi-link (re)setup association procedure

“has multi-link setup with ...”


(less common poor wording meaning  associated at MLD-level)

“associated with”


(context is clear because of the MLD references)



A non-AP MLD shall maintain a record of the most recently received BSS Parameters Change Count subfield value for each AP in affiliated with the AP MLD with which it has multi-link setup it is associated with.

“STA association”

“MLD association”


(technical terms formally defined in the draft: “Association between two STAs is called STA association. Association between a non-AP MLD and an AP MLD is called MLD association.”)

“association” wherever the context is clear – this seems to be almost always (if not always) the case.



If contrast needs to be made between STA and MLD associations (uncommon), use descriptive language (preferred),


“association between two STAs”

“association between two MLDs”


or (not preferred) short qualifiers (i.e., without formal definition)


“STA level association”

“MLD level association”

P49L27 (Note: Even in these cases the term “association” by itself is clear; this is a suggestion to accommodate different preferences)


The reassociation service (see 11.3.6 (Association, reassociation, and disassociation)) is invoked to “move”:


—a current STA association (see (Association)) of a non-AP STA from one AP to the same AP or another AP.

—or a current MLD association (see (Association)) of a non-AP MLD from one AP MLD to the same AP MLD or another AP MLD

—or a current (STA level) association of a non-AP STA with an AP to an (MLD level) association of a non-AP MLD with an AP MLD, where the MAC address of the non-AP STA is the same as the MLD MAC address of the non-AP MLD

—or a current (MLD level) association of a non-AP MLD with an AP MLD to a (STA level) association of a non-AP STA with an AP, where the MLD MAC address of the non-AP MLD is the same as the MAC address of the non-AP STA.

“setup link”

“link” wherever the context is clear – this is almost always the case (the sentence does not make any sense if the link has not been set up).


In some cases, descriptive language such as


“the link that has been set up …”, or the shorter (and grammatically correct)

“the link set up”


Examples where link having been set up is obvious (e.g., the sentence is about something that is only possible after association),




If a STA is affiliated with a non-AP MLD, the non-AP MLD shall have the same U-APSD Flag value for each AC across all setup links (see 35.3.5).




A setup link is defined as enabled if at least one TID is mapped to that link and is defined as disabled if no TIDs are mapped to that link. At any point in time, a TID shall always be mapped to at least one setup link, unless admission control is used. By default, as TIDs are mapped to all setup links, all setup links shall be enabled (see (Default mapping mode)).


P261L10 (sentence saying


If beacon protection is enabled, the R1KH shall derive and distribute the BIGTK and BIPN to all connected STAs. If an R1KH identifies an AP MLD, the R1KH shall derive and distribute the BIGTKs and BIPNs for all setup links to all connected non-AP MLDs.



P261L10 (style, arguable – but grammatically correct),


The TID-to-link mapping mechanism allows an AP MLD and a non-AP MLD that performed multi-link setup association to determine how TIDs are mapped to the setup links set up in DL and in UL.





From: Payam Torab <torab@xxxxxxxx>
Date: Monday, September 27, 2021 at 3:12 PM
To: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>, STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>
Subject: 11-21/1591 (Multi-link association terminology)

Hi Alfred – Could you please add 11-21/1591 (multi-link association terminology) to the MAC contributions queue.



To unsubscribe from the STDS-802-11-TGBE list, click the following link: