[quicwg/base-drafts] The initial table capacity is zero (#2363)

Martin Thomson <notifications@github.com> Wed, 23 January 2019 04:11 UTC

Date: Tue, 22 Jan 2019 20:11:01 -0800
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab68400d52a845066c75864e9620497c24b360501792cf00000001185fab5592a169ce17f6fe9f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2363@github.com>
Subject: [quicwg/base-drafts] The initial table capacity is zero (#2363)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c47e9557d618_71303fe9eced45c0546661"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/REt-x7CHFedNgqZqSWxl_wNGLn0>

Which means that encoders have to send a table capacity change instruction as the first instruction they send on the table update stream.  This is never stated clearly in the draft.

It might be possible to assume - incorrectly - that the table capacity is initially set to the maximum value.  We even contemplated this possibility until the complexities of 0-RTT and stream concurrency squashed those dreams.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2363

[quicwg/base-drafts] The initial table capacity i… Martin Thomson
Re: [quicwg/base-drafts] The initial table capaci… hardie
Re: [quicwg/base-drafts] The initial table capaci… afrind
Re: [quicwg/base-drafts] The initial table capaci… afrind
Re: [quicwg/base-drafts] The initial table capaci… afrind
Re: [quicwg/base-drafts] The initial table capaci… afrind