Thanks for this, Stephen.
I'm not sure "an RSNE that is compatible" is defined. How about:
“h) Both mesh STAs have dot11MeshSecurityActivated equal to false or both mesh STAs have dot11MeshSecurityActivated equal to true and the neighbor mesh STA advertises an RSNE that is compatible with that of the scanning mesh STA (see 14.5.2 (Security capabilities selection)).”
? However, 14.5.2 only covers the pairwise and group ciphers.
What about the compatibility of other things in the RSNE, e.g.
capabilities, group management?
Thanks,
Mark
--
Mark RISON, Standards Architect, WLAN English/Esperanto/Français
Samsung Cambridge Solution Centre Tel: +44 1223 434600
Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601
ROYAUME UNI WWW: http://www.samsung.com/uk
From: Stephen McCann <mccann.stephen@xxxxxxxxx>
Sent: Tuesday, 23 August 2022 23:11
To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx; Mark Rison <m.rison@xxxxxxxxxxx>; Harkins, Daniel <daniel.harkins@xxxxxxx>
Subject: Proposed resolution to CID 1651
Dear all,
during the REVme ad-hoc, the following resolution was proposed for this CID.
==
Revised
A non-mesh STA can associate with an AP that has a different RSNE, the requirement is that there is a non-null intersection of ciphers and AKM.
Change the cited text to:
“h) Both mesh STAs have dot11MeshSecurityActivated equal to false or both mesh STAs have dot11MeshSecurityActivated equal to true and the neighbor mesh STA advertises an RSNE that is compatible with that of the scanning mesh STA”
Note to editor. This is at P3330L34 in D1.3
==
Any further comments would be welcome.
Kind regards
Stephen