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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -247,7 +247,7 @@ retransmittable packets are not acknowledged during this time, then these
packets MUST be marked as lost.

An endpoint SHOULD set the alarm such that a packet is marked as lost no earlier
than 1.125 * max(SRTT, latest_RTT) since when it was sent.
than 1.25 * max(SRTT, latest_RTT) since when it was sent.

Using max(SRTT, latest_RTT) protects from the two following cases:

Expand All @@ -258,7 +258,7 @@ Using max(SRTT, latest_RTT) protects from the two following cases:
* the latest RTT sample is higher than the SRTT, perhaps due to a sustained
increase in the actual RTT, but the smoothed SRTT has not yet caught up.

The 1.125 multiplier increases reordering resilience. Implementers MAY experiment
The 1.25 multiplier increases reordering resilience. Implementers MAY experiment
with using other multipliers, bearing in mind that a lower multiplier reduces
reordering resilience and increases spurious retransmissions, and a higher
multipler increases loss recovery delay.
Expand Down