- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Wed, 13 Jul 2016 07:57:44 +0000
- To: Martin Thomson <martin.thomson@gmail.com>
- cc: Julian Reschke <julian.reschke@gmx.de>, Carsten Bormann <cabo@tzi.org>, Willy Tarreau <w@1wt.eu>, Yanick Rochon <yanick.rochon@gmail.com>, Phil Hunt <phil.hunt@oracle.com>, HTTP Working Group <ietf-http-wg@w3.org>
--------
In message <CABkgnnWtXiac_E1X-ztYJMNQVzrVyPZBCvWHtmX=ksYvgU=4ag@mail.gmail.com>
, Martin Thomson writes:
>FWIW, my dislike of CBOR is strong, but I've been warming to this
>notion. But I would suggest that we NOT base{64,85} anything. HTTP/2
>carries octets very nicely, the only catch being 0x00, which we can
>finagle around.
We would use native CBOR in HTTP/2.
base{64|85} is only to shoe-horn CBOR into HTTP/1
--
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, 13 July 2016 07:58:16 UTC