Small edit (“TGbn SFD”), and a note that these are MAC motions.
Best,
Giovanni
Move to add the following text to the TGbn SFD:
For security in seamless roaming,
when a non-AP MLD is in the process of roaming from the current AP MLD to a target AP MLD within the SMD, the same PMKSA, established with the SMD-ME, shall be used to protect communications with the current AP MLD and the target AP MLD.
Supporting list:[ 23/1416, 24/2072, 24/1894, 24/0052, 23/1884, 23/1937, 23/1996, 24/0083, 24/0101, 24/0396, 24/1812, 24/0398, 24/0412, 24/0655, 23/2157, 24/679, 24/1882, 24/1883]
SP Result: No objections
Move to add the following text to the TGbn SFD:
For security in seamless roaming,
when a non-AP MLD is in the process of roaming from the current AP MLD to a target AP MLD within the SMD, the same PTKSA, established with the SMD-ME, shall be used to protect communications with the current AP MLD and the target AP MLD.
Supporting list:[ 23/1416, 24/2072, 24/1894, 24/0052, 23/1884, 23/1937, 23/1996, 24/0083, 24/0101, 24/0396, 24/1812, 24/0398, 24/0412, 24/0655, 23/2157, 24/679, 24/1882, 24/1883]
SP Result: No objections
From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, January 15, 2025 5:30 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Motion request for Seamless Roaming SPs
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Alfred,
Could you please add the following two motions (SPs had no objections during AM1)?
Best,
Giovanni
Move to add the following text to the SFD:
For security in seamless roaming,
when a non-AP MLD is in the process of roaming from the current AP MLD to a target AP MLD within the SMD, the same PMKSA, established with the SMD-ME, shall be used to protect communications with the current AP MLD and the target AP MLD.
Supporting list:[ 23/1416, 24/2072, 24/1894, 24/0052, 23/1884, 23/1937, 23/1996, 24/0083, 24/0101, 24/0396, 24/1812, 24/0398, 24/0412, 24/0655, 23/2157, 24/679, 24/1882, 24/1883]
SP Result: No objections
Move to add the following text to the SFD:
For security in seamless roaming,
when a non-AP MLD is in the process of roaming from the current AP MLD to a target AP MLD within the SMD, the same PTKSA, established with the SMD-ME, shall be used to protect communications with the current AP MLD and the target AP MLD.
Supporting list:[ 23/1416, 24/2072, 24/1894, 24/0052, 23/1884, 23/1937, 23/1996, 24/0083, 24/0101, 24/0396, 24/1812, 24/0398, 24/0412, 24/0655, 23/2157, 24/679, 24/1882, 24/1883]
SP Result: No objections
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Alfred,
Could you please add motions for following SPs from AM1 session.
SP10:
Do you agree to add the following text to the TGbn SFD?
As part of seamless roaming procedure, a non-AP MLD can initiate a roaming preparation procedure with a target AP MLD by sending a TBD request frame to its current AP MLD.
• The request frame indicates the set of links to be set up with the target AP MLD.
• The request frame indicates the context to be transferred or renegotiated with the target AP MLD.
• The current AP MLD sends a TBD response frame to the non-AP MLD to indicate the status (accept/reject) of the link setup.
•
If the link setup is accepted, the transferable context is transferred to the target AP MLD.
• TBD on whether/how the renegotiation of context is performed in these request/response frames
•
TBD – multiple candidate target AP MLDs selection
Supporting list:[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, 23/1897,
24/0349, 24/0480, 23/1416, 24/1824]
SP result: 149Y, 4N, 52A
SP11:
Do you agree to add the following text to 11bn SFD?
•As part of seamless roaming procedure, a non-AP MLD in state 4 with the SMD-ME can perform roaming transition through a target
AP MLD that is a part of the SMD.
•TBD on the conditions and details for performing roaming through target AP MLD
Supporting list:[24/0398, 24/1812]
SP result: No objection
Thanks,
Binita
Hello Alfred,
I'd like to request a motion or motions to approve the following straw poll text. The straw polls in the MAC adhoc received unanimous support.
SP3 – Mike Montemurro – Roaming: ( Result: No objection)
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 with improvements
SP4 – Mike Montemurro – Roaming: ( Result: No Objection)
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.
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, 23/1897, 24/0349, 24/0480, 23/1416, 24/0881, 23/1897, 24/0349, 24/1746]
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
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
|