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

Improve description of max_ack_delay transport parameter #1869

Closed
wants to merge 6 commits into from
Closed

Improve description of max_ack_delay transport parameter #1869

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
d19d65c
Improve description of max_ack_delay transport parameter
Oct 17, 2018
0f5f6f2
Fix max_ack_delay: it's the *sender's* delay value
Oct 17, 2018
ab99715
Revert "Fix max_ack_delay: it's the *sender's* delay value"
Oct 18, 2018
0acc50b
Revert "Improve description of max_ack_delay transport parameter"
Oct 18, 2018
b63e386
Use Martin Thomson's suggestion to improve max_ack_delay description
Oct 18, 2018
f2ba00b
s/sending of acknowledgments/sending acknowledgments/
Oct 18, 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
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1729,8 +1729,8 @@ disable_migration (0x0009):
max_ack_delay (0x000c):

: An 8 bit unsigned integer value indicating the maximum amount of time in
milliseconds by which it will delay sending of acknowledgments. If this
value is absent, a default of 25 milliseconds is assumed.
milliseconds by which the endpoint will delay sending acknowledgments.
If this value is absent, a default of 25 milliseconds is assumed.

Either peer MAY advertise an initial value for the flow control on each type of
stream on which they might receive data. Each of the following transport
Expand Down