Re: [quicwg/base-drafts] Clean up text on Maximum Table Size. (#2115)

Martin Thomson <> Thu, 13 December 2018 00:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AE535131355 for <>; Wed, 12 Dec 2018 16:28:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -9.459
X-Spam-Status: No, score=-9.459 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id n1CScLSisYAP for <>; Wed, 12 Dec 2018 16:28:29 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D4381130F58 for <>; Wed, 12 Dec 2018 16:28:28 -0800 (PST)
Date: Wed, 12 Dec 2018 16:28:27 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1544660907; bh=i8EioADRFq/i1SL4DK0wFciNuc6F+HxxfOP2hebCk60=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jisT45JZfpQ09Mnhwi5DVqgRfN7JWOfhYe1jmBsAir7KTFu36GDByDVFBBf0rDBE7 mQ8fx1IPivDWQ8UDBOofu0SNRafr8RprYktwCN+Z3qAhJtkvWvDJ5YEhUGlh31SiBS 4a2WpffeM3FGK9YXBZT4kLoisXSglBZcus4hkMTY=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2115/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Clean up text on Maximum Table Size. (#2115)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c11a7abbd92a_43c33f9aaeed45bc2889ea"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 13 Dec 2018 00:28:31 -0000

So I don't think that the amount of *used* space (your A) is that important in the text.  What is most relevant is the amount of space the decoder allows (the setting, your C) and the amount of space the encoder is using (your B).

If we can avoid talking too much about the occupied space, then we might be in a better position.  If we have to, we can talk about "used" or "occupied" space.

I'd like to suggest "maximum table capacity" (C), "table capacity" (B), and "table size" (A).  Would that be better?  I think that avoids the problems you are talking about by using the word "capacity".

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: