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

Remove QUIC_FLOW_CONTROL_RECEIVED_TOO_MUCH_DATA #1823

Merged
merged 1 commit into from Oct 2, 2018
Merged

Remove QUIC_FLOW_CONTROL_RECEIVED_TOO_MUCH_DATA #1823

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 @@ -3037,9 +3037,9 @@ Maximum Data:
All data sent in STREAM frames counts toward this limit. The sum of the largest
received offsets on all streams - including streams in terminal states - MUST
NOT exceed the value advertised by a receiver. An endpoint MUST terminate a
connection with a QUIC_FLOW_CONTROL_RECEIVED_TOO_MUCH_DATA error if it receives
more data than the maximum data value that it has sent, unless this is a result
of a change in the initial limits (see {{zerortt-parameters}}).
connection with a FLOW_CONTROL_ERROR error if it receives more data than the
maximum data value that it has sent, unless this is a result of a change in
the initial limits (see {{zerortt-parameters}}).


## MAX_STREAM_DATA Frame {#frame-max-stream-data}
Expand Down