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

Move text on infinite ACK loops #4859

Merged
merged 5 commits into from Apr 29, 2021
Merged

Move text on infinite ACK loops #4859

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
46bcb95
Move text on infinite ACK loops
martinthomson Mar 30, 2021
2bee55c
endpoint
martinthomson Mar 30, 2021
8444027
Connective tissue
martinthomson Mar 30, 2021
9c6715f
a good suggestion
martinthomson Apr 1, 2021
c804b89
split those infinitives
martinthomson Apr 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
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -3755,9 +3755,9 @@ non-ack-eliciting packets need to be acknowledged, an endpoint MAY wait until an
ack-eliciting packet has been received to include an ACK frame with outgoing
frames.

A receiver that is only sending non-ack-eliciting packets might choose to
An endpoint that is only sending non-ack-eliciting packets might choose to
occasionally add an ack-eliciting frame to those packets to ensure that it
receives an acknowledgment; see {{ack-tracking}}. A receiver MUST NOT send an
receives an acknowledgment; see {{ack-tracking}}. An endpoint MUST NOT send an
ack-eliciting frame in all packets that would otherwise be non-ack-eliciting, to
avoid an infinite feedback loop of acknowledgments.

Expand Down