Discovering Maximum Frame Size

[martinthomson]

HTTP/2.0 requires that implementations support a minimum frame size of 8192 bytes. The draft does not specify how an implementation is expected to learn that its peer has limited frame sizes other than by trial and error. Using RST_STREAM causes the error to be discovered after the problem has been encountered.

It's also not possible to use RST_STREAM to reject a too-large frame that is not bound to a specific stream.

This could be indicated in the SETTINGS frame.

[mnot]

Can you bring this up on-list, please?

[jpinner]

Since frame sizes have decreased to 64k maximum down from 16M, is it reasonable to drop this from the spec entirely and require implementations to handle full-sized frames?

[grmocg]

64k is a large amount for an embedded device (but then again it shouldn't be receiving that much data then, probably)?

[mnot]

Discussed at SF Interim; max frame size is fixed.