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.

Sign up for GitHub

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

Jump to bottom

Editorial recovery fixes #1551

Merged
merged 8 commits into from Jul 15, 2018
Merged

Editorial recovery fixes #1551

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
4e6aec4
Editorial fixes
ianswett Jul 12, 2018
eec0d2f
Fixes
ianswett Jul 12, 2018
d3aa88a
1.125
ianswett Jul 14, 2018
ccbbde3
Update draft-ietf-quic-recovery.md
ianswett Jul 14, 2018
6418fb7
Update draft-ietf-quic-recovery.md
ianswett Jul 14, 2018
8fade2b
Update draft-ietf-quic-recovery.md
ianswett Jul 14, 2018
dcba32d
Update draft-ietf-quic-recovery.md
ianswett Jul 14, 2018
5432507
Update draft-ietf-quic-recovery.md
ianswett Jul 15, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -228,10 +228,10 @@ degraded performance due to the actions of the congestion controller upon
detecting loss. Implementers MAY use algorithms developed for TCP, such as
TCP-NCR {{?RFC4653}}, to improve QUIC's reordering resilience.

QUIC implementations may use time-based loss detection to deal with reordering.
time-based loss detection allows a certain amount of reordering above
max(SRTT, latest_rtt). The RECOMMENDED reordering tolerance is
1/8 max(SRTT, latest_rtt).
QUIC implementations can use time-based loss detection to handle reordering
based on time elapsed since the packet was sent, instead of a packet reordering
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

slight rewording suggestion: "QUIC implementations can use time-based loss detection instead of a packet reordering threshold to handle reordering based on time elapsed since the packet was sent."

threshold. The RECOMMENDED time threshold, expressed as a fraction of the
round-trip time (kTimeReorderingFraction), is 1/8.

### Early Retransmit

Expand Down