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

Excess ack_delay could be non-compiance #4218

Merged
merged 5 commits into from Oct 15, 2020
Merged

Excess ack_delay could be non-compiance #4218

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5e3fd9e
Excess ack_delay could be non-compiance
ianswett Oct 15, 2020
8d96439
Update draft-ietf-quic-recovery.md
ianswett Oct 15, 2020
93e1c55
Update draft-ietf-quic-recovery.md
ianswett Oct 15, 2020
e1a08aa
Update draft-ietf-quic-recovery.md
ianswett Oct 15, 2020
e906bb6
Reflow
ianswett Oct 15, 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
2 changes: 1 addition & 1 deletion draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -375,7 +375,7 @@ After the handshake is confirmed, any acknowledgement delays reported by the
peer that are greater than the peer's max_ack_delay are attributed to
unintentional but potentially repeating delays, such as scheduler latency at the
peer or loss of previous acknowledgements. Excess delays could also be due to
a non-compliant implementaton. Therefore, these extra delays are
a non-compliant receiver. Therefore, these extra delays are
considered effectively part of path delay and incorporated into the RTT
estimate.

Expand Down