| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Dear list,
On today’s 802.11bi call, we discussed fixes to clause 10.71.2.3 (with doc 24/1371).
The previous clause (10.71.2.2 discusses how a
non-AP MLD may be put in a default group (or not), or request to join
another group or start its own group.
Then this clause 10.71.2.3 discusses how the
AP/non AP MLD expresses support, and the AP MLD sends unicast frames
with the Enhanced Group Privacy Availability element (defined in
9.4.2.339, if you want to have a look) so the STA knows what is available in the BSS (groups, associated epoch settings, optional number of participating STAs.)
Now the question (coming from CID 1113) for
which I would like more input is: is that clause 10.71.2.3 looking at
EDP groups, or at EDP epochs? For now, both words are used in a sort of
bundle. But this creates confusion.
My personal impression is that there is a
hierarchy: EDP groups, that are defined with parameters, such as a group
ID, an associated set of epoch parameters, possibly a current group-member count. The STA is assigned to a
group (not to an epoch), and the Ap advertises groups and their specs.
Others expressed that the epoch is the most
important parameter of the group, and that this clause should focus on
epochs more than groups (but I may be mis-representing the input, I am
sure the contributors to this idea will chime in).
Please note that the clause ends with an
illustrations of the epoch, as you will see in 24/1371, this
illustration should move to 10.71.2.5, that describes epochs and their
boundaries.
Do you have a view on this topic?
Thank you!
Jerome
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