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

A few of gorry's nits #4085

Merged
merged 10 commits into from
Sep 10, 2020
2 changes: 1 addition & 1 deletion draft-ietf-quic-recovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down