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
7 changes: 4 additions & 3 deletions draft-ietf-quic-recovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -420,9 +420,10 @@ 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 SHOULD use algorithms developed for TCP,
such as TCP-NCR {{?RFC4653}}, to improve QUIC's reordering resilience after
losses are spuriously detected.
detect spurious losses. Implementers SHOULD increase QUIC's reordering
thresholds in packets or time after losses are spuriously detected,
and can build on mechanisms described in {{?RACK}}.


### Time Threshold {#time-threshold}

Expand Down