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

Stream 1 counts toward MSPC #282

Merged
merged 1 commit into from Feb 16, 2017
Merged

Stream 1 counts toward MSPC #282

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
9 changes: 9 additions & 0 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1705,6 +1705,15 @@ receives a STREAM frame that causes its advertised concurrent stream limit to be
exceeded MUST treat this as a stream error of type QUIC_TOO_MANY_OPEN_STREAMS
({{error-handling}}).

All streams, including stream 1, count toward this limit. Thus, a concurrent
stream limit of 0 will cause a connection to be unusable. Application protocols
that use QUIC might require a certain minimum number of streams to function
correctly. If a peer advertises an MSPC value that is too small for the
selected application protocol to function, an endpoint MUST terminate the
connection with an error of type QUIC_TOO_MANY_OPEN_STREAMS
({{error-handling}}).


## Sending and Receiving Data

Once a stream is created, endpoints may use the stream to send and receive data.
Expand Down