On Wed, Mar 25, 2026, at 15:34, Kazuho Oku wrote: > Yes, using short TLS records during startup is important. In fact, h2o > has long been doing that for HTTP/2.
Definitely. Long TLS records leads to more latency, because more bytes share fate. > I would argue, however, that when a QMux sender emits short TLS > records, it should also use correspondingly short framing units. This is where we start to diverge. TLS is the only layer at which framing forces receivers to wait for bytes. At the QMux layer, you can receive 10 bytes of a 1k record. Those 10 bytes are usable. Introducing record framing *encourages* implementers to be lazy and wait for the whole record, but that's going to make their implementation more vulnerable to performance problems.
