Hi Alfred,
After good discussion with a number of interested members, could you please schedule time to consider the following straw polls?
SP1:
Do you support adding the following to 11bn SFD?
11bn defines a Seamless Mobility Domain (SMD, exact name TBD) that covers multiple AP MLDs, where a non-AP MLD can use the UHR seamless roaming procedure to roam between the AP MLDs of the SMD?
- A logical SMD Management Entity (SMD-ME, exact name TBD) provides association, IEEE 802.1X Authenticator (except for the management of 802.1X control ports which is TBD) and RSNA Key management for non-AP MLDs across all AP MLDs of the SMD.
- A non-AP MLD transitions between AP MLDs within the SMD while maintaining its association and security association with the SMD-ME.
- The non-AP MLD can transition from one SMD to another SMD that are part of the same MD (Mobility Domain) using FT.
SP2:
Do you support adding the following to 11bn SFD?
11bn defines that within a Seamless Mobility Domain (SMD, exact name TBD) the data path includes either one MAC-SAP for the SMD or a separate MAC-SAP per AP MLD of the SMD.
- In the case of a separate MAC-SAP per AP MLD, the DS mapping is updated when the non-AP MLD roams to another AP MLD within the SMD.
- In the case of a separate MAC-SAP per AP MLD, the component of the 802.1X Authenticator in the SMD-ME interacts with an 802.1X Authenticator component in the AP MLD that manages the 802.1X controlled port for the non-AP MLD.
- In the case of a single MAC-SAP for the SMD, the 802.1X Authenticator in the SMD-ME manages the 802.1X controlled port for the non-AP MLD.
The text is based on numerous contributions and thanks to all who contributed.
Note that I have a conflict with the meeting on Wednesday PM2.
Thanks,
Mike
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1