- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Sat, 12 Jul 2014 09:07:16 +0000
- To: Mark Nottingham <mnot@mnot.net>
- cc: HTTP Working Group <ietf-http-wg@w3.org>
In message <2A016106-3FC9-48CF-9249-B1E288B03B4C@mnot.net>, Mark Nottingham wri tes: >So: it appears that we have consensus to address issue #553 by: > >* Expanding the frame size field to 24 bits >* Reserving additional bits to align >* Adding a setting advertising the maximum frame size allowed by the >recipient, with a default of 16K octets and a minimum of 256 octets > >This would address (only) ><https://github.com/http2/http2-spec/issues/553>. > >Does anyone have a problem with that, or further comments? +1 I agree on reserving 8 bits, but alignment is not a good argument to use, since frames are not naturally aligned in in the TCP stream. (We could require padding to 4-byte align frames, but I doubt it will buy us anything worth the trouble..) I think the argument for reserving 8 bits should be that we want to make sure we have space for future improvements. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Saturday, 12 July 2014 09:07:41 UTC