Re: [quicwg/base-drafts] QPACK: Clarify how maximum dynamic table capacity can be set (#2330)

Bence Béky <> Wed, 23 January 2019 01:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D581812F1AC for <>; Tue, 22 Jan 2019 17:37:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.17
X-Spam-Status: No, score=-10.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.979, HTML_IMAGE_ONLY_28=1.404, 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 k7wuZBTfc0SA for <>; Tue, 22 Jan 2019 17:37:20 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6FED612D4E7 for <>; Tue, 22 Jan 2019 17:37:20 -0800 (PST)
Date: Tue, 22 Jan 2019 17:37:19 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1548207439; bh=GS4D7VjcHOTs3c1r4Q860HFQ1gIQoV8/2B1FokiUIas=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xSD2q+YBNhFhM1kREL/A9AEp8cDmiPNlqGlF2etRhcOJrVtGwe7ar6kLeWnNsrsGS 35Z63J7jAB1KL7wfObhBX6qOHwdLQm2tLx4poDARIgT7OzMQveSSr0enept8CiFCsX sUNpXTvZxWbWhAOjHOfHcyUir64Xz0UUyk0LHvpg=
From: Bence Béky <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2330/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] QPACK: Clarify how maximum dynamic table capacity can be set (#2330)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c47c54f28d94_4ccd3fce35ed45c016731"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: bencebeky
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: Wed, 23 Jan 2019 01:37:22 -0000

I support this change, because it avoids the clumsiness around wrapping if changing the value fo SETTINGS_QPACK_MAX_TABLE_CAPACITY was allowed.  I also agree with @afrind that an explicit capacity instruction has to be sent.

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