Re: [quicwg/base-drafts] Octets that are sent twice (#1353)

[ianswett <[e-mail]>]

ianswett commented on this pull request.



> @@ -3612,10 +3612,18 @@ 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 octet of data on a stream has an offset of 0.  An endpoint is
 expected to send every stream octet.  The largest offset delivered on a stream
-MUST be less than 2^62. 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.
+MUST be less than 2^62.
+
+QUIC makes no specific allowances for partial reliability or delivery of stream
+data out of order.  Endpoints are expected to deliver stream data to an
+application as an ordered byte-stream.  Delivering an order byte-stream requires

in-order byte stream?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/1353#pullrequestreview-120063548