From 606b7d2100bc88e5c2544caa3791ce3d4df2e7a1 Mon Sep 17 00:00:00 2001 From: ianswett Date: Mon, 12 Oct 2020 10:53:51 -0400 Subject: [PATCH] Remove paragraph per mirja's suggestion --- draft-ietf-quic-recovery.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md index 270138e663..4eba728c6d 100644 --- a/draft-ietf-quic-recovery.md +++ b/draft-ietf-quic-recovery.md @@ -1086,10 +1086,6 @@ the congestion window SHOULD NOT be increased in either slow start or congestion avoidance. This can happen due to insufficient application data or flow control limits. -A sender can use a variety of mechanisms to determine if the congestion window -is sufficiently utilized. For example, the pipeACK method described in -Section 4.3 of {{?RFC7661}}. - A sender that paces packets (see {{pacing}}) might delay sending packets and not fully utilize the congestion window due to this delay. A sender SHOULD NOT consider itself application limited if it would have fully