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

Re: [STDS-802-11-TGBN] Seamless Roaming framework straw polls


Dear Mike,

Thank you for the SPs.

Dear Alfred, Could you add  to the list of supporting documents below one,
[24/0881]

Thank you,
Tuncer

  

On Tue, Jan 14, 2025 at 1:10 AM Binita Gupta <bingupta.ieee@xxxxxxxxx> wrote:
Hi Mike,

Thank you for requesting these harmonized SPs on Seamless roaming framework.

@Alfred Asterjadhi  - could you please add following list of  supporting contributions for these two SPs:

Reference documents:[24/2072, 24/1894, 24/0052, 23/1884, 23/1937, 23/1996, 24/830, 24/0083, 24/0101, 24/0396, 24/1812, 24/0398, 24/0412, 24/0655, 23/2157, 24/679, 24/1425, 24/881, 24/1882,  24/1883, 24/1897, 24/0349, 24/0480, 23/1416]

All - If you have any other contributions to be added to the supporting list, please request here.

Thanks,
Binita

On Tue, Jan 14, 2025 at 1:46 PM M Montemurro <montemurro.michael@xxxxxxxxx> wrote:
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


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