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

Suggestion for #2499 #2503

Merged
merged 3 commits into from Apr 30, 2019
Merged

Suggestion for #2499 #2503

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
21fa422
Suggestion for #2499
martinthomson Mar 8, 2019
9a9a930
Merge branch 'ianswett-close-max-streams' into invalid-stream-id
martinthomson Apr 30, 2019
18c9450
Reorder sentences
martinthomson Apr 30, 2019
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: 3 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -270,9 +270,9 @@ Bidirectional streams allow for data to be sent in both directions.

Streams are identified within a connection by a numeric value, referred to as
the stream ID. A stream ID is a 62-bit integer (0 to 2^62-1) that is unique for
all streams on a connection. A QUIC endpoint MUST NOT reuse a stream ID within a
connection. Stream IDs are encoded as variable-length integers (see
{{integer-encoding}}).
all streams on a connection. Stream IDs are encoded as variable-length integers
(see {{integer-encoding}}). A QUIC endpoint MUST NOT reuse a stream ID within a
connection.

The least significant bit (0x1) of the stream ID identifies the initiator of the
stream. Client-initiated streams have even-numbered stream IDs (with the bit
Expand Down