| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Folks,
I wanted to initiate an offline discussion on this CID to seek your help in determining a path forward. This CID relates to the following text in Clause 11.55.2:
NOTE—Although the octets xx and yy for EBCS DL traffic areexpected to be set to a combination of values that are
unique to the coverage area where the content is being broadcast, the uniqueness of the octets xx and yy is not
guaranteed. The octets xx, yy, and zz for EBCS UL traffic must be set to values that are unique to the UL traffic stream.
EBCS UL and EBCS Data frames can be differentiated because the EBCS UL frame is a management frame while the
EBCS Data frame is a Data frame.
The CID specifically addresses the second sentence, in bold, which says that the combination of xx, yy, and xx must be unique for each UL traffic stream. The concern is that these values are "configured by the EBCS non-AP STA". What is not clear to me is
how independent EBCS non-AP STAs will ensure this uniqueness. Given that UL traffic can be generated by unassociated STAs, I don't see a clear path to coordinating the values. I can imagine ways that an EBCS non-AP STA could attempt to generate a unique
value (e.g., listen for UL traffic before initial transmission, populate based on values extracted from the on-board clock) but these would not guarantee uniqueness.
We don't necessarily need to define a solution in the document, but I think it would help if we gave some indication of the expectation on the EBCA non-AP STA. So I am asking
for your thoughts on how this uniqueness would/could/should be accomplished.
John
To unsubscribe from the STDS-802-11-TGBC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBC&A=1 |