- From: David Krauss <potswa@gmail.com>
- Date: Wed, 25 Jun 2014 18:20:18 +0800
- To: HTTP Working Group <ietf-http-wg@w3.org>
Received on Wednesday, 25 June 2014 10:20:51 UTC
On 2014�06�25, at 5:35 PM, <K.Morgan@iaea.org> <K.Morgan@iaea.org> wrote: > Bad idea IMO. That would really paint HTTP/2 into a corner. With no reserved bits left, there would never be a chance to go above 64K frames. i.e. you could never " back-port bigger frames onto an existing protocol" IPv6 packets only go up to 64K, so no network processor is going to get away with coarser granularity for the foreseeable future. I�ve not been following this (my implementation is on hold as it seems HTTP/2 is going back to the drawing board) but any �jumbo frames� scheme should be amenable to hardware implementation. Needing a branchy CPU program for decoding would be painting into a corner.
Received on Wednesday, 25 June 2014 10:20:51 UTC