- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Sat, 28 Jan 2012 11:54:59 +0000
- To: Julian Reschke <julian.reschke@gmx.de>
- cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
In message <4F23DF7E.1030809@gmx.de>, Julian Reschke writes: >> Those are all things being transported, just like GET, PUT and 200 >> are and they are no different from a transport point of view, should >> not be treated any different from a transport point of view, and >> their interpretation and semantics should be standardized separately >> from the transport, just like GET, PUT and 200. > >Yes. People have known these to be defined by "HTTP" for ~20 years now. >I see no reason to change that. As I said: I'm not keen on calling anything HTTP/2.0 -- 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, 28 January 2012 11:55:32 UTC