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

RACK specifies a slightly larger time threshold #4114

Merged
merged 3 commits into from Sep 22, 2020
Merged

RACK specifies a slightly larger time threshold #4114

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3ca70f9
RACK specifies a slightly larger time threshold
ianswett Sep 22, 2020
c89bdb9
Update draft-ietf-quic-recovery.md
ianswett Sep 22, 2020
78d4adb
Update draft-ietf-quic-recovery.md
ianswett Sep 22, 2020
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
6 changes: 6 additions & 0 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -514,6 +514,12 @@ The RECOMMENDED time threshold (kTimeThreshold), expressed as a round-trip time
multiplier, is 9/8. The RECOMMENDED value of the timer granularity
(kGranularity) is 1ms.

Note:

: TCP's RACK ({{?RACK=I-D.ietf-tcpm-rack}}) specifies a slightly larger
threshold, equivalent to 5/4, for a similar purpose. Experience with QUIC shows
that 9/8 works well.

Implementations MAY experiment with absolute thresholds, thresholds from
previous connections, adaptive thresholds, or including RTT variation. Smaller
thresholds reduce reordering resilience and increase spurious retransmissions,
Expand Down