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

Re: [STDS-802-11-TGBN] SP request for 11bn MAC

Hi Alfred,

Could you please add one more harmonised roaming SP (SP3 below) to the MAC SP queue:

SP3 (Roaming through a target AP MLD)

Do you agree to define in 11bn that a non-AP MLD in state 4 can initiate request/response exchange for roaming transition through the current AP MLD or through a target AP MLD?

Supporting list: 24/0398, 24/0052, 23/1884, 23/1996, 24/830, 24/0083, 24/0101, 24/0396, 24/0655, 23/2157, 24/679, 24/1425, 24/1883


For SP1 (Definition of an SMD), please update the Supporting list to below:

Supporting list: 24/0052, 23/1884, 23/1996, 24/830, 24/0083, 24/0101, 24/0396, 24/0655, 23/2157, 24/679, 24/1425, 24/881, 24/1883


For SP2 (Roaming Preparation), please update the Supporting list to below:

Supporting list: 24/0052, 23/1884, 23/1996, 24/830, 24/0083, 24/0101, 24/0396, 24/0655, 23/2157, 24/679, 24/1425, 24/881, 24/1882, 24/1883


Thanks,

Binita






On Tue, Nov 12, 2024 at 9:05 PM Binita Gupta <bingupta.ieee@xxxxxxxxx> wrote:
Hi Alfred,

For these roaming SPs, could you please update to add the supporting documents listed below.:

SP1 (Definition of an SMD)

Do you agree to define in 11bn a Seamless Mobility Domain (SMD, exact name TBD), covering multiple AP MLDs, where a non-AP MLD can use the UHR seamless roaming procedure to roam between the AP MLDs of the SMD?

Supporting list: 24/0052, 23/1884, 23/1996, 24/830, 24/0083, 24/0101, 24/0396, 24/0655, 23/2157, 24/679

SP2 (Roaming Preparation)

Do you agree to define in 11bn that as part of seamless roaming procedure, before the request/response exchange requesting the roaming transition from a current AP MLD to a target AP MLD, a roaming preparation procedure can be performed that includes:

  • Transfer of context to a target AP MLD, and
  • Setting up the link(s) with a target AP MLD . The link(s) become available for data transmission after the request/response exchange for the roaming transition is completed.
  • Details on what context can be transferred is TBD
Supporting list: 24/0052, 23/1884, 23/1996, 24/830, 24/0083, 24/0101, 24/0396, 24/0655, 23/2157, 24/679, 24/1425

Thanks,
Binita


On Tue, Nov 12, 2024 at 2:21 PM Binita Gupta <bingupta.ieee@xxxxxxxxx> wrote:
Hi Alfred,

Could you please help add following Roaming SPs to the MAC queue:

SP1 (Definition of an SMD)

Do you agree to define in 11bn a Seamless Mobility Domain (SMD, exact name TBD), covering multiple AP MLDs, where a non-AP MLD can use the UHR seamless roaming procedure to roam between the AP MLDs of the SMD?

  

SP2 (Roaming Preparation)

Do you agree to define in 11bn that as part of seamless roaming procedure, before the request/response exchange requesting the roaming transition from a current AP MLD to a target AP MLD, a roaming preparation procedure can be performed that includes:

  • Transfer of context to a target AP MLD, and
  • Setting up the link(s) with a target AP MLD . The link(s) become available for data transmission after the request/response exchange for the roaming transition is completed.
  • Details on what context can be transferred is TBD

Thanks,
Binita

On Tue, Nov 12, 2024 at 12:25 PM Huang, Po-kai <po-kai.huang@xxxxxxxxx> wrote:

Hi Alfred,

 

              Can you help to add the following SP in the queue?

 

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, the same PMKSA is used to communicate with the current AP MLD and the target AP MLD

Supporting list: 24/0052, 23/1884, 23/1996, 24/830, 24/0083, 24/0101, 24/0396, 24/0655, 23/2157

 

Best,

Po-Kai

 

From: Cariou, Laurent <laurent.cariou@xxxxxxxxx>
Sent: Monday, November 11, 2024 8:13 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] SP request for 11bn MAC

 

Hi Alfred,

Please add the following SP to the queue as well:

 

Do you agree to add to the 11bn SFD:

  • Periodic unavailability announcements from a STA are performed in UHR with enhancing the P2P TWT mechanism.

[23-2002]

 

Thanks,

Laurent

 

 

From: Cariou, Laurent <laurent.cariou@xxxxxxxxx>
Sent: Monday, November 11, 2024 1:20 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] SP request for 11bn MAC

 

Hi Alfred,

 

Please queue the following SPs to the MAC queue for NPCA:

  • Do you support that the event that triggers switching to the NPCA primary channel shall be
    • OBSS Control frame exchange (e.g., (MU-)RTS/CTS) or
    • OBSS HE/EHT/UHR PPDU

[24/0495r0]

 

  • Do you support that the NPCA operation shall use the same EDCA parameters ((MU) EDCA Parameter Set, EPCS EDCA Parameters), on both the BSS primary channel and the NPCA primary channel.

]24/0495r0]

 

 

Please queue the following SPs to the MAC queue for Coex:

  • Do you support that a non-AP STA that is a TXOP responder can indicate in a response frame 1) for how long it will be available, if known and/or 2) whether it will be unavailable after a specific point in time and, if known, for how long
    • the response frame is a Multi-STA BlockAck frame sent by the non-AP STA in response to the initial control frame or to MPDUs that solicit an immediate response

[23-2002]

 

  • Do you support that a non-AP STA can request its associated AP to initiate TXOPs/frame exchanges with the STA with an initial control frame that enables the non-AP STA to include unavailability feedback in the initial response frame?

[23-2002]

 

Please queue the following SP for power save to the MAC queue:

  • Do you support that if a UHR non-AP MLD operates in the eMLSR mode, then its associated UHR AP MLD, that supports transmitting intermediate FCS, shall include an intermediate FCS, if needed by the non-AP MLD, in every Initial Control Frames for eMLSR transmitted to the non-AP MLD through its affiliated APs on the eMLSR links?
    • Mandatory/optional support for transmitting intermediate FCS is TBD
    • The field that carries the Intermediate FCS shall be designed to be ignored by legacy STAs if they are scheduled in the same initial control frame
    • Note: intermediate FCS may not be needed, for instance, if the STA requires no padding. It is TBD whether an intermediate FCS can be avoided if a MIC is present.

[24-1227r1]

 

Thanks,

Laurent

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: 90-92 route de la Reine, 92100 Boulogne, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 5 208 026.16 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: 90-92 route de la Reine, 92100 Boulogne, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 5 208 026.16 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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