Re: [STDS-802-11-TGBI] What happens when an epoch finishes

[Jerome Henry <jhenry@xxxxxxxx>]

Dear Antonio,

Thank you for initiating this dialog!

Just to make sure I understand, when you say "an epoch finishes", you are not talking about the end of an epoch (with another epoch right after), but rather about an epoch sequence, correct?  Similarly, by 'default epoch' you mean the default group (group 0), correct?

If these assumptions are correct, my thinking is that if an AP terminates a group and its sequence, it should move the non AP MLDs to a new or existing group with parameters closest to that of the ending group, not to the default group (there is no reason to suppose that the default group would be any better than another group... I see the AP sending the non AP MLD to the default group only if it is the only group available.  But I agree that we should say what should happen. In my mind, the AP should/shall advertise the other groups before the end of the last epoch, and move the non-AP MLD before the end of the last epoch. At the same time, as the AP has advertised the other groups, the non AP MLD should make its decision, like drop off the BSS or join/create another group... 

My 2 cents

Jerome 

---- On Mon, 27 Oct 2025 11:10:20 -0400 Antonio DeLaOlivaDelgado <aoliva@xxxxxxxx> wrote ---

Dear all 

We need to define the behaviour when an epoch finishes and the non-AP MLD does not receive a new configuration. My take is that it should go into the default epoch. If this is the choice, then we should define that the AP must always send new epoch configuration at least for the default epoch before it finishes its sequence.

Any other idea?

Thanks

---

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

---

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