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

Fix four typos in recovery draft #2071

Merged
merged 1 commit into from
Nov 29, 2018
Merged

Fix four typos in recovery draft #2071

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -335,16 +335,16 @@ TCP-NCR {{?RFC4653}}, to improve QUIC's reordering resilience.

Time threshold loss detection uses a time threshold to determine how much
reordering to tolerate. In this document, the threshold is expressed as a
fraction of an RTT, but implemenantations MAY experiment with absolute
fraction of an RTT, but implementations MAY experiment with absolute
thresholds. This may be used either as a replacement for a packet reordering
threshold or in addition to it.

When a larger packet is acknowledged, if it was sent more than the threshold
after any in flight packets, those packets are immediately declared lost.
Otherwise, a timer is set for the the reordering threshold minus the time
Otherwise, a timer is set for the reordering threshold minus the time
difference between the earliest in flight packet and the largest newly
acknowledged packet. Note that in some cases the timer could become longer when
packets are acknowleged out of order. The RECOMMENDED time threshold, expressed
packets are acknowledged out of order. The RECOMMENDED time threshold, expressed
as a fraction of the round-trip time (kTimeReorderingFraction), is 1/8.

### Early Retransmit
Expand Down Expand Up @@ -381,7 +381,7 @@ higher multiplier increases loss recovery delay.

This mechanism is based on Early Retransmit for TCP {{?RFC5827}}. However,
{{?RFC5827}} does not include the timer described above. Early Retransmit is
prone to spurious retransmissions due to its reduced reordering resilence
prone to spurious retransmissions due to its reduced reordering resilience
without the timer. This observation led Linux TCP implementers to implement a
timer for TCP as well, and this document incorporates this advancement.

Expand Down