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 connection-level flow control exclusion #246

Merged
merged 1 commit into from Jan 30, 2017
Merged

Remove connection-level flow control exclusion #246

Show file tree
Hide file tree
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
3 changes: 1 addition & 2 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -198,8 +198,7 @@ This amounts to the second least-significant bit differentiating the two streams
in a request.

The lower-numbered stream is called the message control stream and carries
frames related to the request/response, including HEADERS. All request control
streams are exempt from connection-level flow control. The higher-numbered
frames related to the request/response, including HEADERS. The higher-numbered
stream is the data stream and carries the request/response body with no
additional framing. Note that a request or response without a body will cause
this stream to be half-closed in the corresponding direction without
Expand Down
14 changes: 4 additions & 10 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1621,16 +1621,10 @@ as an ordered byte-stream. Data received out of order MUST be buffered for
later delivery, as long as it is not in violation of the receiver's flow control
limits.

An endpoint MUST NOT send any stream data without consulting the congestion
controller and the flow controller, with the following two exceptions.

* The crypto handshake stream, Stream 1, MUST NOT be subject to congestion
control or connection-level flow control, but MUST be subject to stream-level
flow control.

* An application MAY exclude specific stream IDs from connection-level flow
control. If so, these streams MUST NOT be subject to connection-level flow
control.
The crypto handshake stream, Stream 1, MUST NOT be subject to congestion control
or connection-level flow control, but MUST be subject to stream-level flow
control. An endpoint MUST NOT send data on any other stream without consulting
the congestion controller and the flow controller.

Flow control is described in detail in {{flow-control}}, and congestion control
is described in the companion document {{QUIC-RECOVERY}}.
Expand Down