W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Re: Maximum Frame Size

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 5 Mar 2013 08:49:47 -0800
Message-ID: <CABkgnnUvM+BrsVsCmLHTDrpporz2LSX1T=4jwmq3DoA1e0CKmg@mail.gmail.com>
To: Patrick McManus <pmcmanus@mozilla.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 4 March 2013 18:05, Patrick McManus <pmcmanus@mozilla.com> wrote:
> Its very tempting to just get rid of the path discovery signaling and
> retry baggage and make the max frame size also the minimum supported
> read frame size. When spdy had the max frame size at 31 bits that
> wasn't doable - but at 16 bits I think it is. If the group thinks 64KB
> is too big but 32KB is not, (for a minimum) then I'd rather reduce the
> max frame size than introduce a whole bunch of mechanisms to deal with
> pmtud-prime.

What of it?

1. Reduce the maximum to be the minimum that must be supported.  This
would allow us to remove error cases and negotiation.  Patrick is
suggesting 32K, and of course we can negotiate something else (later).

2. Add settings to signal the maximum size, minimum remains 8192.
Can't send more than 8192 until settings indicate larger.  Remove the
error message.

3. Leave as is with the error message.

The error message does makes things brittle, so removing it would be
good.  A too-large frame that modifies session state will force the
session to be dropped entirely.
Received on Tuesday, 5 March 2013 16:50:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 5 March 2013 16:50:22 GMT