Re: [quicwg/base-drafts] Use the FRAME_ENCODING_ERROR for errors in frame encoding (#3042)

[Kazuho Oku <[e-mail]>]

kazuho commented on this pull request.



> @@ -5060,8 +5059,8 @@ the offset of the next byte that would be sent.
 The first byte in the stream has an offset of 0.  The largest offset delivered
 on a stream - the sum of the offset and data length - cannot exceed 2^62-1, as
 it is not possible to provide flow control credit for that data.  Receipt of a
-frame that exceeds this limit will be treated as a connection error of type
-FLOW_CONTROL_ERROR.
+frame that exceeds this limit MUST be treated as a connection error of type
+FRAME_ENCODING_ERROR or FLOW_CONTROL_ERROR.

Note that there is a similar issue with MAX_STREAMS and STREAMS_BLOCKED. They communicate the cumulative count of streams of particular type using varint. It is possible to express numbers up to 2<sup>62</sup> however it is always an error to indicate a value above 2<sup>60</sup>.

[Section 4.5](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#rfc.section.4.5) currently states that STREAM_LIMIT_ERROR is to be used for communicating such error (for MAX_STREAMS, there is no mention of STREAMS_BLOCKED).

-- 
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/3042#discussion_r325491130