Hi Yongho,
I have been push this contribution 21-0573r3. Since this contribution also touches the setting of A3 for the individually Addressed Management frame,
the 11be group cannot reach consensus. But now, considering 11be group has already decided to carry the intended link info within the frame body, I will push the other part of this contribution, i.e. use the MLD MAC Address to construct AAD for the individually
addressed Management frame. And I have updated my contribution.
Regards
Guogang Huang
发件人: M Montemurro [mailto:montemurro.michael@xxxxxxxxx]
发送时间: 2022年5月6日
5:24
收件人: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBE] Discussion on CID 5360 (DCN 575r2)
Hi Yongho,
Given that there's no specification text for how this works in the draft, there's no agreement for how this works.
This would also mean that everytime a STA would retry a MMPDU on another link, it would need to re-encrypt the frame. That is terribly inefficient and problematic since MPDUs are processed entirely differently from MMPDUs.
Also, there would need to be adjustments to PN processing.
No, I think that it has been discussed in TGbe a long time ago.
At least, I can provide one related document that was submitted by Guogang. Group didn't accept this document.
I disagree and do not support that. It hasn’t been discussed nor is the text in the specification.
Please see my response below.
|
Yongho/all,
Apologies for dropping into this discussion late/in the middle, and perhaps this has been discussed and/or updated since last I knew. But I thought:
-
Individually addressed Data frames are ‘generated’ by the AP MLD’s upper MAC (also where it came into the AP from the DS), and thus encrypted as described, agreed.
[YH: In the MAC header, A1 and A2 are set to the STA MAC address.
When constructing the AAD, A1 and A2 are changed to the MLD MAC addresses associated with the A1 and A2 of the MAC header.]
-
-
Group addressed Data frames are passed from the AP MLD upper MAC to the affiliated AP’s upper MAC(s) for transmission, and are encrypted using link-specific group keys. I believe we’re still agreed.
-
But, individually addressed Management frames could be generated within the AP MLD’s upper MAC, and directed to a specific non-AP MLD peer. Such MMPDUs (and hence their “MPDU”) would have A1 and A2 set to the MLD addresses of the RXr and
TXr MLDs, respectively.
[YH: In the MAC header, A1 and A2 are set to the STA MAC address. (Always Address fields in the MAC header use the STA MAC address.)
When constructing the AAD, A1 and A2 have no change. The A1 and A2 of the MAC header are used.]
-
So, while I agree with the quote below, the implication is that such Management frames would have A1/A2 set to the MPDU Address 1/2 field, yes, but this would not result in different addresses if/when retransmitted on another link.
Did I “miss a memo”?
Thanks. Mark
Thanks for initiating this discussion. Because I suggested this NOTE, I may provide the background.
Current AAD construction rule is that only individually addressed Data frames use the MLD MAC address instead of the STA MAC address.
If dot11MultiLinkActivated is true, for both the transmitter and intended receiver of the MPDU, either of To DS or From DS subfields in the MAC header of the
MPDU is set to 1, and the MPDU is an individually addressed Data frame, then A1 is set to:
—the MLD MAC address of the intended receiver MLD of the MPDU.
—otherwise, Al is set to MPDU Address 1 field.
So, when another frame like a management frame is retransmitted on a different link, the frame is re-encrypted. The below note clarifies this. If people have
a concern on the below NOTE, they have to comment on the above spec text.
Hi,
Initiating this thread to discuss CID 5360 from DCN 575r2 which I presented today. The discussion on the call was for the following NOTE:
NOTE
– (#5360) For MLO, when an individually addressed management frame is retransmitted on another link, the encrypted data is
modified on retransmission.
(Hewlett Packard Enterprise)
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
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
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
|