Skip to content

Commit

Permalink
Don't mandate zero server-initiated bidi streams (#2773)
Browse files Browse the repository at this point in the history
  • Loading branch information
MikeBishop committed Jun 12, 2019
1 parent 255e533 commit 3af8d91
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions draft-ietf-quic-http.md
Original file line number Diff line number Diff line change
Expand Up @@ -924,10 +924,10 @@ HTTP/3 server SHOULD send non-zero values for the QUIC transport parameters
RECOMMENDED that `initial_max_bidi_streams` be no smaller than 100, so as to not
unnecessarily limit parallelism.

HTTP/3 does not use server-initiated bidirectional streams; clients MUST omit or
specify a value of zero for the QUIC transport parameter
`initial_max_bidi_streams`.

HTTP/3 does not use server-initiated bidirectional streams, though an extension
could define a use for these streams. Clients MUST treat receipt of a
server-initiated bidirectional stream as a connection error of type
HTTP_GENERAL_PROTOCOL_ERROR unless such an extension has been negotiated.

## Unidirectional Streams

Expand Down

0 comments on commit 3af8d91

Please sign in to comment.