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

Suggestions from #2197 #2316

Merged
merged 7 commits into from Jan 8, 2019
Merged

Suggestions from #2197 #2316

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
89cb57e
Suggestions from #2197
ianswett Jan 8, 2019
dc395ba
Update draft-ietf-quic-transport.md
martinthomson Jan 8, 2019
20b96fe
Update draft-ietf-quic-transport.md
martinthomson Jan 8, 2019
9781113
Martin's comments
ianswett Jan 8, 2019
9d0d47d
Update draft-ietf-quic-transport.md
ianswett Jan 8, 2019
1450934
Update draft-ietf-quic-transport.md
ianswett Jan 8, 2019
56e891a
Update draft-ietf-quic-transport.md
ianswett Jan 8, 2019
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
3 changes: 2 additions & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2835,7 +2835,8 @@ received packet that contains frames other than ACK and PADDING frames.
An endpoint MUST NOT send a packet containing only an ACK frame in response
to a packet containing only ACK or PADDING frames, even if there are packet
gaps which precede the received packet. This prevents an indefinite feedback
loop of ACKs.
loop of ACKs. The endpoint MUST however acknowledge packets containing only
ACK or PADDING frames when sending ACK frames in response to other packets.

Packets containing PADDING frames are considered to be in flight for congestion
control purposes {{QUIC-RECOVERY}}. Sending only PADDING frames might cause the
Expand Down