- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Wed, 25 Jun 2014 06:39:00 +0000
- To: Mark Nottingham <mnot@mnot.net>
- cc: Willy Tarreau <w@1wt.eu>, Greg Wilkins <gregw@intalio.com>, HTTP Working Group <ietf-http-wg@w3.org>
In message <B4914129-A5A9-40B5-A4FD-7AAA1A374C81@mnot.net>, Mark Nottingham wri tes: >> Moving objects which are trivially megabytes and gigabytes in size >> using 16kB frames just doesn't make any sense, in particular not >> given that MTUs above 9K are actively being discussed again. > >The simplest way to address this would be to un-reserve the first two >bits of the length <http://http2.github.io/http2-spec/#rfc.section.4.1>; >that would get us back up to 64k, [...] Really ? A 16bit protocol in a 64bit CPU age ? -- 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 Wednesday, 25 June 2014 06:39:26 UTC