| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Carol, Thank you for sharing your thought. I think we have two questions now:
This is the original purpose of the SP I would like to run, since I think this is an important point to solve. On one hand, this indicates correlation between links (revealing the MLD structure, but this info is also available in clear in the ML IE in beacons). On the other hand, this avoid correlation between Old and new OTA values across links, and contribute to the mass effect to hide a STA in the crowd.
I think this question is related to the handling of transition period, but of course transition period and Epoch start are linked. I my mind, as written in the D0.3, each Epoch starts with a transition period. Assuming all the non-AP MLD of a given group starts a new Epoch at the same time (TSF counter based), all the non-AP STA, associated to a non-AP
MLD registered to a given EDP Epoch group, starts a new Epoch at the same time. This new Epoch starts with a transition period that allow transmission of buffered frames using Old OTA values (currently only retransmissions in
D0.3, but we can discuss that ), and New OTA values without mixing them in a same TxOP (to avoid correlation). At the end of the transition, a non-AP STA is not allowed to used old OTA values for transmission of any frames, nor decode received frames using
old OTA values. So if the STA still has some retransmission using OLD OTA values waiting for transmission, those frames should be flushed. For transition period I think we can discuss using 11-23/1148r0 (slide 7 and 8) as support. I can (re)present it next session if needed. Stéphane. From: Carol Ansley <carol@xxxxxxxxxx>
Hello Jerome and Stephane and everyone, While I agree that to avoid an observer being able to use the changeover to glean more information about the MLDs, at the same time, we need to consider how to word the text for clarity. For example, If an MLD has a full queue of packets waiting to go out on its 5GHz link as the current epoch ends, do the other links in the MLD wait to start using the new information until the 5GHz link finishes
sending the old information? What about the other MLDs in the Epoch group? To say it another way, do all of the buffers on all of the links need to be purged before the new headers and numbers start being used? What happens on the AP side? Does the AP MLD need to discard any packets that are still in a queue at the end of an epoch or rework them once the new epoch time is reached? Or does it just finish blasting
them all out with the old information until it gets to the next epoch’s packets? Thinking about what can be seen on the air – the SN/PN sequences shared across the link of an MLD unfortunately can be used to connect those links to a single MLD. As long as one of the affiliated STAs is
still using the old parameters, an observer knows that MLD is still there. Is this straw poll intended to ask about what a single MLD does across its affiliated STAs, or what all of the MLDS in that Epoch group will do? Regards, Carol 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 |