| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| --- This message came from the IEEE 802.11 ARC Reflector ---
Thanks, Harry. One question, what does your “DS” stand for in this usage? As for putting “the line” above the MSDU mux/demux, the problem is that the SFD calls for number of lower features to be “shared”, like Block Ack, which implies encrypt/decrypt, frag/defrag, and duplicate detection. It would be possible to have separate functional blocks for these features in each MAC-L, but only if they are tightly coordinated to maintain the same state in all the multi-link stacks. (At which point, it starts to become hard to tell the difference between one copy or multiple copies that are working off the same state.) But, this is exactly why I think Yongang’s slide #20 is interesting to discuss, and see what everyone thinks. Mark From: Dr. Harry Bims <harrybims@xxxxxx> The components of the MAC-U should be services on the DS that support the Data Handling, Data fwd, Mgmt (inc. SSID), and Beacons/Probes Authen blocks. Thus, the MAC-L-SAP should sit just above the MSDU mux/demux & address matching block. Harry To unsubscribe from the STDS-802-11-ARC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-ARC&A=1 |