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

Merge text on what not to send in response to ACKs #4855

Closed
wants to merge 2 commits into from
Closed

Merge text on what not to send in response to ACKs #4855

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
caea0a8
Merge text on what not to send in response to ACKs
ianswett Mar 28, 2021
da100f5
Update draft-ietf-quic-transport.md
ianswett Mar 28, 2021
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-transport.md
View file
Open in desktop
Expand Up @@ -3746,7 +3746,7 @@ received packet. Additionally, a receiver MUST NOT send an ack-eliciting
frame in all packets that would otherwise be non-ack-eliciting. This avoids
an infinite feedback loop of acknowledgments, which could prevent the
connection from ever becoming idle. Non-ack-eliciting packets are eventually
acknowledged when the endpoint sends an ACK frame in response to other events.
acknowledged when the endpoint sends an ACK frame in response to other events.

In order to assist loss detection at the sender, an endpoint SHOULD generate
and send an ACK frame without delay when it receives an ack-eliciting packet
Expand Down