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

Hi Binita,

 

Thanks for sharing the SP. I have a few concerns/comments on the SP.

 

  1. The SP seems to be indicating that the preparation is done with ‘a’ target AP MLD. Does it mean that the STA has already chosen a target AP MLD by this stage and can do preparation with only one target AP MLD? This can be a little inefficient if the non-AP MLD has to go one by one with each AP MLD to do preparation individually.
  2. I like the indication in the second bullet. Provides some extra flexibility on the non-AP MLD side.
  3. I think before agreeing to the third and the fourth bullet, I would like to see what a ‘transfer’ of context would mean and the resulting behavior. E.g., if an SCS (with QoS char IE) is setup with the current AP, the current AP is setup to trigger/serve the STA as per its needs. When SCS is transferred to the target AP, does it mean that the target AP is also setup to trigger the STA despite the fact that the STA has not yet roamed to the target AP MLD? This seems very inefficient as an AP is allocating resources for a non-existing STA. I feel that terms transferability check or a feasibility of context transfer would be better or a clarification of what transfer means is required.

 

Thanks.

Peshal

 

From: Binita Gupta <bingupta.ieee@xxxxxxxxx>
Sent: Wednesday, January 15, 2025 1:59 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Seamless Roaming framework straw polls

 

Caution: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

Hi Alfred,

 

Could you please add these two roaming SPs on the MAC Agenda. it would be great if you can add these after Giovanni's SPs on roaming in Thu AM1 session.

 

SP5:

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 at a target AP MLD.
  • The request frame can indicate the context to be transferred or renegotiated with the target AP MLD.
  • The links of the non-AP MLD are set up with the target AP MLD and the context is transferred to the target AP MLD (if applicable).
  • After the link setup and context transfer (if applicable), the current AP MLD sends a TBD response frame to the non-AP MLD.
  • TBD on whether/how the renegotiation of context is performed in these request/response frames.

 

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]

 

SP6:

 

Do you agree to add the following text to 11bn SFD?

As part of seamless roaming procedure, a non-AP MLD in state 4 can perform roaming transition through a target AP MLD.

  • TBD on the conditions and details for performing roaming through target AP MLD

 

Supporting list:[24/0398, 24/1812] 

 

Thanks,

Binita

 

 

On Wed, Jan 15, 2025 at 8:44 AM Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:

Hi Alfred,

 

Could you please add these two SPs on Roaming on MAC agenda? It would be great if you can add after the SPs requested by Mike since they are also based on those SPs (I believe these are schedule for Thu AM1).

 

SP3

  • Do you support the following 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

SP4

  • Do you support the following 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]

 

Thanks!

Giovanni

 

From: Binita Gupta <bingupta.ieee@xxxxxxxxx>
Sent: Monday, January 13, 2025 10:10 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Seamless Roaming framework straw polls

 

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

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

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