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

Restored a few error codes and redefined FRAME_ERROR. #521

Closed
wants to merge 9 commits into from
Closed

Restored a few error codes and redefined FRAME_ERROR. #521

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
1ed2ef5
Add proposed error codes
martinthomson Apr 24, 2017
27d517e
Reference error codes
martinthomson Apr 24, 2017
d3dec57
Simplify CONNECTION_CLOSE error handling
martinthomson May 12, 2017
870b07b
Add proposed error codes
martinthomson Apr 24, 2017
4a51343
Reference error codes
martinthomson Apr 24, 2017
4183871
Restored a few error codes and redefined FRAME_ERROR.
May 12, 2017
9a501be
fix broken things during rebase
May 12, 2017
e407ba7
fix broken things during rebase
May 12, 2017
875675b
fix broken things during rebase
May 12, 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
14 changes: 8 additions & 6 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2319,18 +2319,19 @@ similar to the way ephemeral streams are used in SST
for some applications.


Stream Identifiers {#stream-id}
## Stream Identifiers {#stream-id}

Streams are identified by an unsigned 32-bit integer, referred to as the Stream
ID. To avoid Stream ID collision, clients initiate streams using odd-numbered
ID. To avoid Stream ID collision, clients initiate streams using odd-numbered
Stream IDs; streams initiated by the server use even-numbered Stream IDs.

Stream ID 0 (0x0) is reserved for the cryptographic handshake. Stream 0 MUST NOT
be used for application data, and is the first client-initiated stream.
Stream ID 0 (0x0) is reserved for the cryptographic handshake. Stream 0 MUST
NOT be used for application data, and is the first client-initiated stream.

A QUIC endpoint cannot reuse a Stream ID. Streams MUST be created in sequential
order. Open streams can be used in any order. Streams that are used out of order
result in lower-numbered streams in the same direction being counted as open.
order. Open streams can be used in any order. Streams that are used out of
order result in lower-numbered streams in the same direction being counted as
open.

Stream IDs are usually encoded as a 32-bit integer, though the STREAM frame
({{frame-stream}}) permits a shorter encoding when the leading bits of the
Expand Down Expand Up @@ -2811,6 +2812,7 @@ Public Reset packet.
An endpoint that receives an invalid CONNECTION_CLOSE frame MUST NOT signal the
existence of the error to its peer.


## Stream Errors

If the error affects a single stream, but otherwise leaves the connection in a
Expand Down