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

Martin Thomson <> Sat, 12 January 2019 00:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DF1E7126BED for <>; Fri, 11 Jan 2019 16:08:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.935
X-Spam-Status: No, score=-10.935 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, HTML_IMAGE_ONLY_24=1.618, 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 zk5HdFaJRLqT for <>; Fri, 11 Jan 2019 16:07:59 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 474F2128AFB for <>; Fri, 11 Jan 2019 16:07:59 -0800 (PST)
Date: Fri, 11 Jan 2019 16:07:58 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1547251678; bh=NZ3seqHkJPYF3anNu0AtCq6gVBOs10Al5nKpCk1ZzI8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ojl8DLP/yBAzHqxw1Dc9kucXUW1Fl1jowfjTHfQLbq73af94fNGqZts8GZlkPvcuX DnRawRpUK1c4aXvdmL09360Ofnji3Li/Z3Ss2+oGmSf9wf8A7rtmrCL/dTUo1Bf9po ISjlr4rubkHNY+lSIi/1bB003p98k1l9tISZsyW0=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/commit/98a8932a0b24dbbe725b39ea01f86f1f0f43e947/>
In-Reply-To: <quicwg/base-drafts/commit/>
References: <quicwg/base-drafts/commit/>
Subject: Re: [quicwg/base-drafts] QPACK: Clarify how maximum dynamic table capacity can be set (98a8932)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c392fde982a7_69163ff6d34d45b8408a3"; 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: Sat, 12 Jan 2019 00:08:01 -0000

What is missing here is whether the table capacity instruction needs to be sent when SETTINGS causes the value to increase. 

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