Why ACK/CTS Rates Limit Wi‑Fi Performance Despite Higher Bandwidths

Unlike cellular, Wi-Fi offers the promise of backward compatibility. A Wi-Fi 7 client device can still connect to a Wi-Fi 4 or earlier generation access point (AP) and work in the presence of older Wi-Fi generation devices. To achieve this backward compatibility, several overheads are involved.

All multicast, management, broadcast frames and ACK/CTS response frames in a Wi-Fi network have to be sent only in basic rates. The AP advertises the list of basic rates in Supported Rates Information Element (IE) in beacons which is usually a subset of 11g/11b data rates. Support for basic rates is a requirement for a client to join an AP.

The 802.11 standard requires the data rate for ACK and CTS frames to be assigned depending on the modulation of the received PPDU.

11b → lowest 11b basic rate
OFDM BPSK → 6 Mbps ACK/CTS
OFDM QPSK → 12 Mbps ACK/CTS
OFDM 16QAM or higher → 24 Mbps ACK/CTS

No matter how much Wi-Fi BW increases (40, 80, 160, 320 MHz) or how much Wi-Fi modulation increases (256, 1024, 4096 QAM), the ACK/CTS data rate is still only 6, 12 or 24 Mbps.

Linkedin: :backhand_index_pointing_down:

The PCAP angle worth adding here: in a capture you can actually measure the ACK overhead directly by comparing the inter-frame spacing. A 6 Mbps ACK after a high-MCS data frame creates a visible asymmetry in the frame timeline — the data frame completes in microseconds at MCS 11, but the ACK consumes multiples of that airtime at legacy rate. In dense deployments this shows up as unexplained channel utilisation inflation — the CU counter climbs even when data throughput looks healthy. The fix isn’t the data rate — it’s eliminating the legacy clients forcing the AP to maintain 6 Mbps as a basic rate in the first place.

Hola qué tal esta muy interesante el tema que se está tratando felicidades :smiley: a los creadores grandes éxitos :ok_hand: