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

RE: Why "MUST" encoder emit Context Update

From: <K.Morgan@iaea.org>
Date: Thu, 31 Jul 2014 11:33:31 +0000
To: <OSAMAM@microsoft.com>, <ietf-http-wg@w3.org>
Message-ID: <0356EBBE092D394F9291DA01E8D28EC2011E33C56C@SEM001PD.sg.iaea.org>
On Thursday,31 July 2014 01:42, OSAMAM@microsoft.com wrote:
>    After applying an updated value of the HTTP/2 setting
>    SETTINGS_HEADER_TABLE_SIZE that changes the maximum size of the
>    header table used by the encoder, the encoder MUST signal this change
>    via an encoding context update (see Section 7.3). ...
> Why is it a 'MUST' for the encoder to emit a Context Update opcode?  ...

I agree this is confusing.

For example, suppose the encoder is only using 512 for the table size out of the 4096 default value for SETTINGS_HEADER_TABLE_SIZE.

Now suppose the decoder lowers SETTINGS_HEADER_TABLE_SIZE to 1024, why 'MUST' the encoder emit a Context Update opcode since the new setting doesn't force the encoder to lower the table size and therefore should have no effect?

This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
Received on Thursday, 31 July 2014 11:34:02 UTC

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