From 0cbd1c09aaec823eaa7c4c7d65d2e698e78f54f7 Mon Sep 17 00:00:00 2001 From: ianswett Date: Thu, 10 Sep 2020 12:27:30 -0400 Subject: [PATCH] Update draft-ietf-quic-recovery.md Co-authored-by: Martin Thomson --- draft-ietf-quic-recovery.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md index 9d1fa99efc..fbe2c86cd5 100644 --- a/draft-ietf-quic-recovery.md +++ b/draft-ietf-quic-recovery.md @@ -481,7 +481,7 @@ implementations SHOULD NOT use a packet threshold less than 3; see {{?RFC5681}}. Some networks may exhibit higher degrees of packet reordering, causing a sender to detect spurious losses. Additionally, packet reordering could be more common with QUIC than TCP, because network elements that could observe and reorder -out-of-order TCP packets cannot do that for QUIC, because packet numbers +TCP packets cannot do that for QUIC, because packet numbers are encrypted. Algorithms that increase the reordering threshold after spuriously detecting losses, such as RACK {{?RACK}}, have proven to be useful in TCP and are expected to be at least as useful in QUIC.