| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
The proposed solution has the following benefits:
• The unicast Management frame is allowed to be transmitted through any link just like the Data frame, irrespective of the link-level Management frame or the MLD-level Management frame;
• When retransmitted through another link, the AAD will not change and thus no need to re-encrypt it;
However since Link-Level MMPDU are using BSSID and not MLD MAC Address, prevent it from be transmitted on any link without re-calculating AAD again when transmitted over other link.
I would expect that A3 will not be included in AAD for the statement to be true
Could you please advice ?
Regards, Oren
|
MMPDU |
Direction |
AAD Construction |
||
|
A1 |
A2 |
A3 |
||
|
MLD-level MMPDU |
From DS=1 |
AP MLD MAC Address |
||
|
From DS=0 |
AP MLD MAC Address |
Non-AP MLD MAC Address |
AP MLD MAC Address |
|
|
Link-level MMPDU |
To DS=0 From DS=1 |
Non-AP MLD MAC Address |
AP MLD MAC Address |
|
|
To DS=1 From DS=0 |
AP MLD MAC Address |
Non-AP MLD MAC Address |
Affiliated AP BSSID of target link |
|
Hi Alfred and all,
Could you please add the following PDT for individual Management frame and CR for EHT Operation element to the MAC queue? I will upload them later.
l Doc:21/571r0 “PDT MLD security for Individual Management Frame”
l Doc:21/573r0 “CR for CIDs related to EHT Operation element”
Regards
Guogang Huang
To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1