| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Mike, As I have explained to you during the call, replay check has to be based on the peer entity of negotiated PTKSA/GTKSA. In baseline the negotiated entity is the same as TA, but in MLD, this is not true anymore.
The right way to clarify this is to write the texts based on the negotiated entity rather than saying TA field value is replaced.
For baseline, you can just use “for non-MLO”, which is already what you have already done for other places in security.
Best, Po-Kai From: M Montemurro <montemurro.michael@xxxxxxxxx> Hello all, During the discussion of https://mentor.ieee.org/802.11/dcn/22/11-22-1178-03-00be-tgbe-lb266-security-comment-resolutions.docx,
we did not reach a conclusion of CID 13599. I'd like to initiate a discussion on the reflector to see if there is consensus on a resolution to this CID. The comment references text in the base standard that describes PN processing based on the PN value and the TA value. However for both GCMP and CCMP in the baseline, the TA is missing from the block diagram as input to the Replay Check
block. I think that the proper way to specify the MLO behavior is to fix the baseline and then add the MLO behavior. However in absence of that, I provided text changes (see document above) that describe the behavior consistent with what's currently
in the baseline. Please provide input. Thanks, Mike 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 |