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

Bence Béky <> Tue, 18 December 2018 16:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0684B130EFF for <>; Tue, 18 Dec 2018 08:19:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.06
X-Spam-Status: No, score=-6.06 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.105, 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 V3PN7j3qPua9 for <>; Tue, 18 Dec 2018 08:19:49 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 28466130EE3 for <>; Tue, 18 Dec 2018 08:19:49 -0800 (PST)
Date: Tue, 18 Dec 2018 08:19:47 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1545149987; bh=C+IGj9G1vANlpOnNYjPQoGSkaU0ryHTnYEfi1RSZFws=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mREXs4VmdmgVOUCdQApzEjgLyAynFloVMZypVDeuWFvV+zftP4VVaLgr61kbN1BQs qKeTWF6CoHmye+IwwWPMsrFYchBzHe5WyOqLaiHIq9QxRMQjAhVmeR+6KApCwx7dYm 3ZJSgKzBDvERsMqWUwntmiELySFW5y9p0LCwN1pc=
From: Bence Béky <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2115/review/>
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_5c191e23b76cc_2b9b3f8ab8ad45bc261d4"; 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: Tue, 18 Dec 2018 16:19:51 -0000

bencebeky commented on this pull request.

-The initial maximum size is determined by the corresponding setting when HTTP
-requests or responses are first permitted to be sent. For clients using 0-RTT
-data in HTTP/3, the table size is the remembered value of the setting, even if
-the server later specifies a larger maximum in its SETTINGS frame.  For HTTP/3
-servers and HTTP/3 clients when 0-RTT is not attempted or is rejected, the
-initial maximum table size is the value of the setting in the peer's SETTINGS
+The initial dynamic table capacity is the value of the maximum dynamic table
+capacity when HTTP requests or responses are first permitted to be sent.  For
+HTTP/3 servers and HTTP/3 clients when 0-RTT is not attempted or is rejected,
+the initial maximum table capacity is zero.  For clients using 0-RTT data in

I have changed the initial maximum table capacity to zero in the spirit of, because that is what's consistent with the first sentence.  And endpoint is allowed to send HTTP requests and responses before receiving the peer's SETTINGS frame.

Another option is to scratch the first sentence, and describe that an endpoint cannot use the dynamic table until the SETTINGS frame is received, however, at that point the dynamic table capacity is changed to the value of SETTINGS_MAXIMUM_DYNAMIC_TABLE_CAPACITY.

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