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

Second set of editorial nits #3770

Merged
merged 4 commits into from Jun 19, 2020
Merged

Second set of editorial nits #3770

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9719e06
Second set of editorial nits
martinthomson Jun 17, 2020
8f453ff
Capacity
martinthomson Jun 18, 2020
1ec60fa
These need wrapping :|
martinthomson Jun 19, 2020
5270a60
Wrap
martinthomson Jun 19, 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: 3 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -3464,7 +3464,7 @@ the IP header SHOULD be acknowledged immediately, to reduce the peer's response
time to congestion events.

The algorithms in {{QUIC-RECOVERY}} are expected to be resilient to receivers
that do not follow guidance offered above. However, an endpoint should only
that do not follow guidance offered above. However, an implementation should only
deviate from these requirements after careful consideration of the performance
implications of a change, for connections made by the endpoint and for other
users of the network.
Expand Down Expand Up @@ -3551,8 +3551,8 @@ SHOULD stop tracking those acknowledged ACK Ranges.
It is possible that retaining many ACK Ranges could cause an ACK frame to become
too large. A receiver can discard unacknowledged ACK Ranges to limit ACK frame
size, at the cost of increased retransmissions from the sender. This is
necessary if an ACK frame would be too large to fit in a packet, however
receivers MAY also limit ACK frame size further to preserve space for other
necessary if an ACK frame would be too large to fit in a packet.
Receivers MAY also limit ACK frame size further to preserve space for other
frames or to limit the capacity that acknowledgments consume.

A receiver MUST retain an ACK Range unless it can ensure that it will not
Expand Down