W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

RE: HPACK opcode bit patterns

From: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
Date: Fri, 29 Aug 2014 16:19:03 +0000
To: David Krauss <potswa@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <6C71876BDCCD01488E70A2399529D5E53339A9AC@ADELE.crf.canon.fr>
> -----Original Message-----
> From: David Krauss [mailto:potswa@gmail.com]
> Sent: mercredi 6 août 2014 12:58
> To: HTTP Working Group
> Subject: Re: HPACK opcode bit patterns
> 	I don't have a strong opinion to change the masks, but I am curious if
> the bit pattern selection was deliberate.
> Also, an implementation can treat "without indexing" as "never indexed" and
> use a common code path, since the encodings are identical modulo a don't-
> care bit. Wouldn't be surprised if that was deliberate.

Yes it was deliberate: not only for sharing a common code path, but also from a security perspective, so that the two representations are as close as possible.

Received on Friday, 29 August 2014 16:19:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:10 UTC