Skip to content

Commit

Permalink
Merge pull request #350 from quicwg/stream-limit
Browse files Browse the repository at this point in the history
Add stream offset limit of 2^64.
  • Loading branch information
martinthomson authored Mar 3, 2017
2 parents 18638d0 + 3d9d177 commit 1047b02
Showing 1 changed file with 6 additions and 4 deletions.
10 changes: 6 additions & 4 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -1182,7 +1182,8 @@ The STREAM frame contains the following fields:

* Offset: A variable-sized unsigned number specifying the byte offset in the
stream for the data in this STREAM frame. The first byte in the stream has an
offset of 0.
offset of 0. The largest offset delivered on a stream - the sum of the
re-constructed offset and data length - MUST be less than 2^64.

* Stream Data: The bytes from the designated stream to be delivered.

Expand Down Expand Up @@ -1962,9 +1963,10 @@ sender or during delivery to the application at the receiver.
When new data is to be sent on a stream, a sender MUST set the encapsulating
STREAM frame's offset field to the stream offset of the first byte of this new
data. The first byte of data that is sent on a stream has the stream offset 0.
A receiver MUST ensure that received stream data is delivered to the application
as an ordered byte-stream. Data received out of order MUST be buffered for
later delivery, as long as it is not in violation of the receiver's flow control
The largest offset delivered on a stream MUST be less than 2^64. A receiver
MUST ensure that received stream data is delivered to the application as an
ordered byte-stream. Data received out of order MUST be buffered for later
delivery, as long as it is not in violation of the receiver's flow control
limits.
The cryptographic handshake stream, Stream 1, MUST NOT be subject to congestion
Expand Down

0 comments on commit 1047b02

Please sign in to comment.