Hello Henry,
The change is a result of implementing the resolution of CID 8149. Unfortunately, Editor made an error. According the resolution of CID 8149, “CCMP
of GCMP header” should be “CCMP
or GCMP header”.
However, someone may still answer your question: why is
any GCMP text included here?
See table below:
|
8149 |
3037.00 |
12.5.2.4.4 |
V |
"the separate replay counter for individually addressed Protected Fine Timing frames shall be used if the FTM subfield of the CCMP Header" -- what if GCMP is used rather than
CCMP? |
As it says in the comment |
REVISED (SEC: 2024-07-18 18:09:35Z) Change “FTM subfield of the CCMP Header (Figure 12-15 (Expanded CCMP MPDU(#3525)(11az)))” to “FTM subfield of the CCMP
or GCMP header (Figure 12-15 (Expanded CCMP MPDU(#3525)(11az)) or Figure 12-28 (Expanded GCMP MPDU(11az)))”. |
Regards,
Emily
From: Henry Ptasinski <henry@xxxxxxxxxx>
Sent: Thursday, August 01, 2024 3:54 PM
To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGM] Questions on D7.0 changes to clause 12.5.2.4.4
--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Hi,
Could somebody explain these changes to the replay detection text (redline of D7.0 vs D6.0 shown)?
With these changes, it now refers to "the CCMP of GCMP header", which obviously doesn't make any sense. Also, why is
any GCMP text included here? GCMP replay detection is handled in 12.5.4.4.4. (Also note that the equivalent step (i) is completely missing from 12.5.4.4.4.)
Maybe there were some misapplied edits?
Thanks,
--
To unsubscribe from the STDS-802-11-TGM list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1
To unsubscribe from the STDS-802-11-TGM list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1