From 9bc7cc65b763016e2b80e54fb55ea26825ce7c60 Mon Sep 17 00:00:00 2001 From: ianswett Date: Mon, 17 Aug 2020 09:46:17 -0400 Subject: [PATCH] Cite the second reason bytes_in_flight might exceed CWND Fixes #4004 --- draft-ietf-quic-recovery.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md index 0c7dfebd4d..56a53a0fb4 100644 --- a/draft-ietf-quic-recovery.md +++ b/draft-ietf-quic-recovery.md @@ -733,7 +733,8 @@ window in bytes. An endpoint MUST NOT send a packet if it would cause bytes_in_flight (see {{vars-of-interest}}) to be larger than the congestion window, unless the packet -is sent on a PTO timer expiration; see {{pto}}. +is sent on a PTO timer expiration (see {{pto}}) or when entering recovery +(see {{recovery-period}}). ## Explicit Congestion Notification {#congestion-ecn} @@ -782,7 +783,7 @@ acknowledged. When a loss or ECN-CE marking is detected, NewReno halves the congestion window, sets the slow start threshold to the new congestion window, and then enters the recovery period. -## Recovery Period +## Recovery Period {#recovery-period} A recovery period is entered when loss or ECN-CE marking of a packet is detected in congestion avoidance after the congestion window and slow start