RE: draft-ietf-httpbis-header-compression-latest, "2.3.2 Dynamic Table"

The decoder sets a maximum size.  The encoder can select the size it wishes to actually use, so long as it’s not greater than the decoder’s limit.  That’s why there’s a limit in both directions – the decoder declares its maximum in HTTP/2 SETTINGS, while the encoder declares the size it’s actually using in an HPACK instruction.

From: []
Sent: Tuesday, June 13, 2017 7:56 PM
Subject: draft-ietf-httpbis-header-compression-latest, "2.3.2 Dynamic Table"



Good day!

I have a question about the section "The encoder decides how to update the dynamic table and as such can control how much memory is used by the dynamic table. To limit the memory requirements of the decoder, the dynamic table size is strictly bounded (see Section 4.2<>).”

the decision about how to update the dynamic table is from “encoder” or “decoder”? I thought it is decoder.

Please correct me if it is not :)

Best Regards,

Okis Chuang


The information contained in this email and any attachments is confidential

and may be subject to copyright or other intellectual property protection.

If you are not the intended recipient, you are not authorized to use or

disclose this information, and we request that you notify us by reply mail or

telephone and delete the original message from your mail system.

Received on Wednesday, 14 June 2017 17:58:39 UTC