Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---Thanks, Dave.
Makes sense.
Sorry to nit pick procedure with you, but we really can’t reject 1681 for insufficient detail, as it is quite specific/detailed. We can: 1) Reject it because we can’t come to consensus, and craft some discussion about what we considered and the issues that were not settled; or 2) we can get the commenter (Mark Rison) to withdraw the comments. The latter is less work, but is up to Mark.
Mark
From: David Halasz <dave.halasz@xxxxxxxx>
Sent: Wednesday, June 22, 2022 5:17 PM
To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGM] CIDs 1681 - 1683
--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
In reviewing CIDs 1681-1683 the proper resolution would involve fixing up the specification to address the issue that PV1 frames do not work with QMF. I'm willing to continue to work towards a resolution in the next round of comment resolution and suggest we reject the comments for insufficient detail for this round.
Dave H.
CID
Page
Clause
Duplicate of CID
Resn Status
Comment
Proposed Change
1681
3151.00
12.5.3.4.4
"the recipient shall maintain an additional replay counter for each ACI for received individually addressed robust Management frames and robust PV1 Management frames that are received with the To DS subfield equal to 1." -- precedence is not clear as to whether the To DS check only applies to PV1 Management frames (previous sentence suggests only applies to PV0 Management frames), and it is not clear why only PV0s have to be unicast
Change to "the recipient shall maintain an additional replay counter for each ACI for received individually addressed robust Management and PV1 Management frames that are received with the To DS subfield equal to 1."
1682
12.5
There are replay counters for PMF (one for each of individually addressed robust Management and individually addressed robust PV1 Management) and for QMF (one for each ACI of individually addressed robust Management -- it's not clear whether this is also used for individually addressed robust PV1 management or whether there's a separate set of 4)
Explicitly identify the full set of replay counters
1683
12.5
There is one RC for unicast robust Management and there are four RCs for unicast QMF. It is not clear when the former will be used, if QMF is enabled for the link
Explicitly identify the use of the RC for unicast robust Management frames when QMF i
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
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