Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adaptive thresholds are useful #3572

Merged
merged 9 commits into from
May 13, 2020
Merged
7 changes: 5 additions & 2 deletions draft-ietf-quic-recovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -420,8 +420,11 @@ The RECOMMENDED initial value for the packet reordering threshold
less than 3, to keep in line with TCP {{?RFC5681}}.

Some networks may exhibit higher degrees of reordering, causing a sender to
detect spurious losses. Implementers MAY use algorithms developed for TCP, such
as TCP-NCR {{?RFC4653}}, to improve QUIC's reordering resilience.
detect spurious losses. Algorithms that increase the reordering threshold after
spuriously detecting losses, such as TCP-NCR {{?RFC4653}}, have proven to be
useful in TCP and are expected to at least as useful in QUIC. Re-ordering
could be more common with QUIC than TCP, because network elements cannot observe
and fix the order of out-of-order packets.

### Time Threshold {#time-threshold}

Expand Down