| Hi, Thank you for the discussion. Here are my comments.
I would keep EPP element optional for both CPE and BPE. This is inline with the current spec 802.11bi D2.1 (no changes needed).
802.11bi spec can define a default value (64) for the AID Storage Size. The default AID Storage Size value would be in use, if the EPP element is not included to the association signaling.
A CPE STA may change its Epoch group in associated state. Handling the epoch groups signaling after association may make the association faster, reducing the delays for the transmitted traffic and STA power consumption.
A BPE AP operates only a single EPP group. All STAs associated with BPE AP MLD use this single group. Thus, there is no need for STA specific signaling on EPP Group parameters, because they will just join to BPE APs group. The only need for the element may be the AID Storage Size signaling, if the default size is not optimal for the STA.
Cheers, Jarkko On Oct 15, 2025, at 4:54 AM, NEZOU Patrice <Patrice.Nezou@xxxxxxxxxxxx> wrote:
Hi Antonio and Domenico, Thanks for initiating the discussion on the reflector. I think that the initial issue was the fact that the “AID Storage Size” field is included in the EPP Epoch Settings element. I thank that this is an error to mix information related to AID and Epoch in the same element, because it is very difficult to harmonize the behavior of the AIDs and the Epochs for different scenarios such as CPE and BPE. For me, the Duration is mandatory to define an Epoch. A solution could be to separate AID information and Epoch settings in different element. As Domenico proposed, I would be also supportive of an alternative solution specifying the contents of the EPP element included in a (Re)Association request frame such as: - CPE shall include (1) Epoch Duration, (2) AID storage size in EPP Epoch Settings Field in EPP Element in Assoc Req
- BPE shall include AID Storage size and GroupID set to 0 (meaning that STA accepts to join the default group) in EPP Epoch Settings field in EPP Element in Assoc Req
Regards Patrice | BEWARE: This email originated outside of our organization. DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe.
Please report all suspicious emails to the ISS department as an attachment. |
thanks for bringing this up. I think the direction we’re going is to have different BPE and CPE subclauses to clarify BPE vs CPE specific behaviours. I have some concerns if we do not include the EPP Element because that would enforce defining some default value or a different behavior for AID storage size determination which might not work for all scenarios and all STAs. At this point, I would be supportive of your option (1). An alternative would be a slight variation of (1) where: - CPE shall include (1) Epoch Duration, (2) AID storage size in EPP Epoch Settings Field in EPP Element in Assoc Req
- BPE shall include AID Storage size only in EPP Epoch Settings field in EPP Element in Assoc Req
We are having a parallel discussion about the mandatory use of the EPP element in (Re)Association Request frames. We need this to agree on the BPE and CPE operation in clause 10.71.2.2. - it is true that in the (Re)Association Request frame definition, the EPP element is defined as optional. - yesterday we agreed on having the EPP element sent (with a shall) in (Re)Association request frames due to the need of sending always the AID storage size in section 10.71.2.2. We need to make this coherent with the definition of the (Re)Association Request frame if we keep it like that. - the EPP element includes the epoch duration as a mandatory field. When designing this element we decided to always send the most important information for an epoch, its duration. The non-AP declares a will to join a group with this duration, while the AP states the actual duration of the group it assigns the non-AP to. Now, we have an issue with BPE. It looks like BPE aims at having the EPP element included in the (Re)Association Request frame, but only with the AID storage size (if I understood correctly). I see four options to this, and we need to decide soon since we need to have the text ready asap: 1- We change the EPP Epoch Settings field to not have the Epoch duration as a mandatory field. 2- We declare the EPP element is optional in (Re)Association request frames for BPE and mandatory for CPE. 3- We do not have the EPP element mandatory in (Re)Association Request frames no matter the CPE or BPE. 4- BPE learns to live with the Epoch duration in the EPP element for (Re)Association request frames I would go for #2 to be honest.
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
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
|