Re: HPACK encoder/decoder memory bounding from Fred Akalin on 2013-10-25 (ietf-http-wg@w3.org from October to December 2013)

From: Fred Akalin <akalin@google.com>
Date: Fri, 25 Oct 2013 11:46:50 -0700
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Mike Bishop <Michael.Bishop@microsoft.com>, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>, Hervé Ruellan <ruellan.crf@gmail.com>, Osama Mazahir <OSAMAM@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <CANUYc_SjWyL-O7+c2ATuSOXTuFTqnU4qK8oJJ9pMxuL57u0Big@mail.gmail.com>

I went back and checked the draft and the setting description was clear; I
just glossed over the key phrase '...used to decode header blocks.'

I thought about suggesting that _DECODE_ be put in the settings name, but I
don't know if that would actually be clearer. And the other settings are
"one-way" anyway.

On Fri, Oct 25, 2013 at 11:44 AM, Martin Thomson
<martin.thomson@gmail.com>wrote:

> On 25 October 2013 11:42, Fred Akalin <akalin@google.com> wrote:
> > I think I'm clear on everything now.
>
> Let me know if you think that there is anything unclear in the
> draft(s).  I'm happy to fix anything that is even slightly ambiguous
> or vague.
>

Received on Friday, 25 October 2013 18:47:17 UTC