Hi,
Jouni pointed out to me that mac80211 currently requires the BSS
Parameter Change Count in the (Re)Association response multi-link
element per-STA profile(s), and via sharing the code, also in Link
Reconfiguration response, as you note in hostap commit ce8a121287bf ("AP
MLD: Include BPCC only in (Re)Associtiation Response frames").
Also, as you note there, the spec seems to suggest this should not be
the case, per section 9.4.2.322.2.4, where it is only in (re)association
response frames.
However, in the spec it seems to be explicitly required in section
35.3.6.4:
If the AP MLD accepts link additions for one or more links, it
shall include [...] For each Per-STA Profile subelement included
in the BSS Multi-Link Element, [...] and the STA Profile field
corresponding to that AP shall be complete and consists of all the
elements and fields that would be included in the STA Profile
field for that AP in a Reassociation Response frame that includes
the corresponding AP as a reported AP [...].
We had some discussion about this internally and think that this is
inconsistent in the spec, and also that the 35.3.6.4 text (that suggests
including the field) makes more sense, so we'd suggest clarifying the
spec in section 9.4.2.322.2.4.
It seems to me that your commit was more meant to fix the ML Probe
response (no disagreement here with that, I believe) than the Link
Reconfiguration response, so two questions:
1) Did you actually look into the various texts about it and decide
that despite the seeming spec inconsistency, it should _not_ be
present in Link Reconfiguration responses? As I said above, we
think it makes more sense to have it present.
2) Are you aware of any APs that don't include it, which would mean
regardless of that, mac80211 should accept both?
Thanks,
johannes
