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

Re: [STDS-802-11-TGBE] 11-20/1554 ML reconfiguration

Hi Arik, some of your comments are not aligned with 802.1 operation and ecosystem. What you see is a baseline formulated by AP and non-AP community. I would hope that you can support this baseline and then separately propose additional pieces that you see fit.

 

Regards,

Payam

 

From: Arik Klein <arik.klein@xxxxxxxxxx>
Date: Sunday, January 17, 2021 at 4:31 AM
To: Payam Torab <torab@xxxxxxxx>, STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>
Subject: RE: 11-20/1554 ML reconfiguration

Hi Payam,

 

See my further comments inline

 

Regards,

Arik

 

From: Payam Torab <torab@xxxxxxxx>
Sent: יום ו 15 ינואר 2021 01:50
To: Arik Klein <arik.klein@xxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: 11-20/1554 ML reconfiguration

 

Hi Arik,

 

If a non-AP tells AP it doesn’t want a link (from the MLO link set that it set up during association), for any reason, it’s free money (resource) returned to AP with no fight. Non-AP shouldn’t ask for this if it has any intention of using that link again, but if it does, well, it doesn’t want it. Smaller IEs, fewer transmissions, coming with no arbitration.

 

Please note the concept of “link” applies to non-AP/client. Cases designated as AP-initiated are in the form of request to non-AP to add/remove its link. On the AP MLD side, it can add and remove AP STAs serving the whole network. With that said,

 

  • AP asking non-AP to add a link: Non-AP can reject, may be costly or any other reason
  • AP asking non-AP to remove a link (in the context of network wide optimization for example): Non-AP can reject (I want to keep the 6 GHz I was given)

[Arik Klein] I think that from system-wise perspective, such a “claim” that the non-AP STA is entitled to reject the AP MLD request to remove a link just because this resource has already been allocated for it is inefficient. I think the AP MLD has much broader perspective for the needs of all non-AP MLDs (due to dynamic changes in the traffic / network conditions), thus its request to remove a link with a specific non-AP MLD shall no be rejected (at least as long as we requires the AP MLD not to reject similar request from the non-AP MLD)

  • AP indicating to non-AP a link will not be there soon (because corresponding AP STA is going away, shutting down etc., similar to BTM disassociation imminent): This is a courtesy call similar to channel switch announcement

[Arik Klein] Agree with your point, but why shouldn’t it be “reciprocal” i.e. the non-AP MLD shall have courtesy indication for the time that the link will be removed (as an option)?
In any case this “courtesy indication” is unicast and not broadcast (as CSA), so it can be applied by both sides….

 

Regards,

Payam

 

From: Arik Klein <arik.klein@xxxxxxxxxx>
Date: Thursday, January 14, 2021 at 8:58 AM
To: Payam Torab <torab@xxxxxxxx>, STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>
Subject: RE: 11-20/1554 ML reconfiguration

Hi Payam,

 

Thanks for sharing the presentation.

 

I have questions regarding proposed SP1 and SP3

 

In the proposed Straw Poll 1, when the non-AP MLD requests the associated AP MLD to remove a link – the AP MLD can’t reject this request.

 

On the contrary, in proposed Straw Poll 3, when the AP MLD requests the associated non-AP MLD to remove a link you propose either of 2 options:

  • Option 1: this request is considered as a recommendation and the non-AP MLD can reject it.
  • Option 2: this request is mandatory and includes notification for the time that the link will actually be removed (and the non-AP can’t reject it).

 

My questions are:

  • If we take Option 1 (of SP3): can you explain the difference why the AP MLD can’t reject the request of the associated non-AP MLD, while the non-AP MLD can reject the request of the AP MLD?
  • If we take Option 2 (of SP3): why the proposed notification pointing to a future removal time can’t be applied for the case of link removal in SP 1 (i.e. when the non-AP MLD requests a link removal from the AP MLD)??  

 

Thanks for the swift reply.

 

Regards,

Arik

 

From: Payam Torab <torab@xxxxxxxx>
Sent: יום ד 13 ינואר 2021 21:11
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] 11-20/1554 ML reconfiguration

 

Hello all, we will likely have time in our next MAC call to run straw polls for the ML reconfiguration topic I presented today. It would be nice if you could share your comments and questions here.

 

Regards,

Payam

To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1

To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1