[quicwg/base-drafts] MAX_STREAM_DATA discrepancy (#1744)

[Vidhi Goel <[e-mail]>]

In the transport draft, under Frames section, max_stream_data refers to.
"A variable-length integer indicating the maximum amount of data that can be sent on the identified stream, in units of octets";

whereas under Flow Control section, it refers to max absolute offset, quoted

"MAX_STREAM_DATA frames send the maximum absolute byte offset of a stream. A receiver MAY advertise a larger offset at any point by sending MAX_DATA or MAX_STREAM_DATA frames. A receiver cannot renege on an advertisement; that is, once a receiver advertises an offset, advertising a smaller offset has no effect. A sender MUST therefore ignore any MAX_DATA or MAX_STREAM_DATA frames that do not increase flow control limits."

This discrepancy can cause the implementations to differ as max. amount of data is treated differently than max absolute offset. Can we clarify this in the draft?

-- 
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/issues/1744