- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Thu, 3 Jul 2014 14:34:51 -0700
- To: Adrian Cole <adrian.f.cole@gmail.com>
- Cc: Mark Nottingham <mnot@mnot.net>, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 3 July 2014 14:24, Adrian Cole <adrian.f.cole@gmail.com> wrote: > Proposal 4 (remove continuation; add setting for total header frame(s) > length limit) works for me. I know details are pending, but I'm > on-board with the idea. To be clear, I believe that proposal 4 is two things: 1. A setting that describes the maximum permissible compressed size of a header block (default 16K) 2. A mandate to fill all frames carrying header block fragments if they are followed by a CONTINUATION In the normal case, this would mean that an implementation could avoid even implementing CONTINUATION. That is, if we get this right and say that padding can be used to fill the frame, otherwise we're back in the poop.
Received on Thursday, 3 July 2014 21:35:18 UTC