From f0ba783832156322077043d6a432a394bb722a5b Mon Sep 17 00:00:00 2001 From: mirjak Date: Fri, 1 Mar 2024 12:16:44 +0100 Subject: [PATCH] Update draft-ietf-quic-ack-frequency.md --- draft-ietf-quic-ack-frequency.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-ack-frequency.md b/draft-ietf-quic-ack-frequency.md index 84c660aa..bf365c86 100644 --- a/draft-ietf-quic-ack-frequency.md +++ b/draft-ietf-quic-ack-frequency.md @@ -138,9 +138,9 @@ endpoint performance in the following ways: acknowledgement-only packets that it sends. Experience shows that this reduction can be critical for high bandwidth connections. -- Similarly, receiving UDP datagrams can also be CPU intensive. A data sender - can decrease its CPU usage by reducing the number of acknowledgment-only - packets that it has to receive and process. +- Similarly, receiving UDP datagrams can also be CPU intensive. Reducing the + acknowledgement frequency therefore also reduces the CPU usage at the data + sender as it has to receive and process less acknowledgment-only packets. - For asymmetric link technologies, such as DOCSIS, LTE, and satellite, connection throughput in the forward path can become constrained