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

Identify streams unidirectional vs bidirectional based on stream ID #872

Merged
merged 6 commits into from Oct 30, 2017
Merged

Identify streams unidirectional vs bidirectional based on stream ID #872

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
820dd81
Identify unidirectional streams by the 2nd bit in the stream ID
RyanTheOptimist Oct 12, 2017
5061a15
Address nits
RyanTheOptimist Oct 13, 2017
a9b13de
invert
RyanTheOptimist Oct 13, 2017
4137259
clarify
RyanTheOptimist Oct 13, 2017
0740371
more
RyanTheOptimist Oct 13, 2017
afabe8a
Remove unnecessary language
RyanTheOptimist Oct 13, 2017
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
6 changes: 0 additions & 6 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2562,12 +2562,6 @@ coordinate the creation of streams; they are created unilaterally by either
endpoint. Endpoints can use acknowledgments to understand the peer's subjective
view of stream state at any given time.

Only the initiator of a stream may send a STREAM frame without receiving one
unless otherwise specified by the application. All implicitly opened streams
must remain in the IDLE state until a STREAM frame has been received. If a
RST is received on a stream reserved for the peer before any STREAM frame
has been received, it will immediately transition to the closed state.

In the absence of more specific guidance elsewhere in this document,
implementations SHOULD treat the receipt of a frame that is not expressly
permitted in the description of a state as a connection error (see
Expand Down