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.

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

Clarify MAX_STREAMS #2012

Merged
merged 4 commits into from Nov 19, 2018
Merged
Changes from 1 commit
Commits
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
12 changes: 7 additions & 5 deletions draft-ietf-quic-transport.md
Expand Up @@ -829,11 +829,13 @@ commitment.

## Controlling Concurrency {#controlling-concurrency}

An endpoint controls concurrency by limiting the total number of incoming
streams. An initial value is set in the transport parameters (see
{{transport-parameter-definitions}}) and subsequently increments are advertised
using MAX_STREAMS frames ({{frame-max-streams}}). Separate limits apply to
unidirectional and bidirectional streams.
An endpoint limits the cumulative number of incoming streams a peer can open.
Only steams with a stream id less than
(max_stream * 4 + initial_stream_id_for_type) can be opened. Initial limits
are set in the transport parameters (see {{transport-parameter-definitions}})
and subsequently limits are advertised using MAX_STREAMS frames
({{frame-max-streams}}). Separate limits apply to unidirectional and
bidirectional streams.

Endpoints MUST NOT exceed the limit set by their peer. An endpoint that
receives a STREAM frame with a stream ID exceeding the limit it has sent MUST
Expand Down