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.

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

Second set of editorial nits #3770

Merged
merged 4 commits into from Jun 19, 2020
Merged
Changes from 1 commit
Commits
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
8 changes: 4 additions & 4 deletions draft-ietf-quic-transport.md
Expand Up @@ -3464,10 +3464,10 @@ 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 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.
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.

An endpoint that is only sending ACK frames will not receive acknowledgments
from its peer unless those acknowledgements are included in packets with
Expand Down