| 132 | | The failure to receive an ACK for the long MPDU causes both the LRC and and the SLRC to increment. The increment operation on the SLRC causes the CW to increase to its next value. When the ACK is received in the second attempt, the CW is reset to its minimum value according to '''''Excerpt B of Section 9.3.3 of 802.11-2012''''' from [#ExampleS.1 Example S.1]. |
| | 132 | The failure to receive an ACK for the long MPDU causes both the LRC and and the SLRC to increment. The increment operation on the SLRC causes the CW to increase to its next value. When the ACK is received in the second attempt, the CW is reset to its minimum value according to '''''Excerpt B of Section 9.3.3 of 802.11-2012''''' from [#ExampleS.1 Example S.1]. The SLRC is also reset to zero, but the reasons behind this involve going deeper than the 2012 publication of the standard. There is actually an acknowledged error in the 2012 publication. Specifically, |
| | 133 | |
| | 134 | '''''Excerpt E of Section 9.3.3 of 802.11-2012''''' |
| | 135 | |
| | 136 | <strike>The SSRC shall be reset to 0 when a CTS frame is received in response to an RTS frame, when a BlockAck frame is received in response to a BlockAckReq frame, when an ACK frame is received in response to the transmission of a frame of length greater than dot11RTSThreshold containing all or part of an MSDU or MMPDU, or when a frame with a group address in the Address1 field is transmitted. The SLRC shall be reset to 0 when an ACK frame is received in response to transmission of a frame containing all or part of an MSDU or MMPDU of , or when a frame with a group address in the Address1 field is transmitted.</strike> |
