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

MAX_STREAM_DATA is valid in the "idle" state #483

Merged
merged 2 commits into from
May 3, 2017
Merged

MAX_STREAM_DATA is valid in the "idle" state #483

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a023b0f
Allow STREAM_BLOCKED on unopenable streams
martinthomson Apr 20, 2017
b96329d
MAX_STREAM_DATA might arrive on an idle stream
martinthomson Apr 28, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 15 additions & 5 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1795,6 +1795,11 @@ Stream ID:

: A 32-bit unsigned number indicating the stream which is flow control blocked.

An endpoint MAY send a STREAM_BLOCKED frame for a stream that exceeds the
maximum stream ID set by its peer (see {{frame-max-stream-id}}). This does not
open the stream, but informs the peer that a new stream was needed, but the
stream limit prevented the creation of the stream.


## STREAM_ID_NEEDED Frame {#frame-stream-id-needed}

Expand Down Expand Up @@ -2186,9 +2191,10 @@ All streams start in the "idle" state.

The following transitions are valid from this state:

Sending or receiving a STREAM frame causes the stream to become "open". The
stream identifier is selected as described in {{stream-id}}. The same STREAM
frame can also cause a stream to immediately become "half-closed".
Sending or receiving a STREAM frame causes the identified stream to become
"open". The stream identifier for a new stream is selected as described in
{{stream-id}}. The same STREAM frame can also cause a stream to
immediately become "half-closed" if the FIN flag is set.

Receiving a STREAM frame on a peer-initiated stream (that is, a packet sent by a
server on an even-numbered stream or a client packet on an odd-numbered stream)
Expand All @@ -2202,8 +2208,12 @@ A RST_STREAM frame on an "idle" stream causes the stream to become
"half-closed (local)"; receiving RST_STREAM causes the stream to become
"half-closed (remote)".

Receiving any frame other than STREAM or RST_STREAM on a stream in this state
MUST be treated as a connection error ({{error-handling}}) of type YYYY.
An endpoint might receive MAX_STREAM_DATA frames on peer-initiated streams that
are "idle" if there is loss or reordering of packets.

Receiving any frame other than STREAM, MAX_STREAM_DATA, STREAM_BLOCKED, or
RST_STREAM on a stream in this state MUST be treated as a connection error
({{error-handling}}) of type YYYY.

An endpoint MUST NOT send a STREAM of RST_STREAM frame for a stream ID that is
higher than the peers advertised maximum stream ID (see
Expand Down