[quicwg/base-drafts] minimum payload size requirement creates awkward special case (#2049)

[Marten Seemann <[e-mail]>]

In #2030 we set the minimum payload size to `4-packet number length`.
This creates a really awkward special case in my code. When packing STREAM frames, I make sure that the last STREAM frame doesn't have the length flag set, so I can save the bytes for encoding the payload length.

In the corner case where I only have a single stream for new a stream with stream ID < 64 that is closing that stream at offset 0, the length of this STREAM frame is just 2 bytes: 1 (type byte) + 1 (stream ID).
If I now add a PADDING frame in order to fulfill the minimum size requirement, this will be interpreted as part of the payload of the STREAM frame, so I will need special logic to detect the special case described above, and set the length flag on the STREAM frame in that case.

The motivation for #2030 was to avoid a special case that would rarely be executed (and which would lead to an undecryptable packet in the worst case). It seems that we achieved that by introducing an even rarer special case, which leads to incorrect delivery of stream data if not properly taken care of.

-- 
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/2049