Re: [quicwg/base-drafts] Use "Insert Count" rather than "Largest Reference" (#2111)

Mike Bishop <> Tue, 18 December 2018 23:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 882BE1311EA for <>; Tue, 18 Dec 2018 15:08:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.065
X-Spam-Status: No, score=-3.065 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 uWkBuoY3Z2r2 for <>; Tue, 18 Dec 2018 15:08:13 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 04BB91200D7 for <>; Tue, 18 Dec 2018 15:08:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=egsCLn9YWtxa1u2BYiSqNnHPSzk=; b=LMGb1nP3Awi7vqEi tkWccpd6uSuBIDBQ1k7y2IcP7YqL0aEHnfN8UhExLT+KcUEhVg8R8umAKmOrFd1i GueG5LdvfufzvY9cXlC22BDKXZaiKn2KkMGKx7NMjk6zGUirYBfa1Jx2yycppA81 fH6hGrJWAugjLPvqN83B3SmVVPY=
Received: by with SMTP id filter0479p1iad2-20093-5C197DDB-55 2018-12-18 23:08:11.844227231 +0000 UTC m=+103623.306655603
Received: from (unknown []) by (SG) with ESMTP id 4BQxTKwwQ0yvTzH1RSdiYQ for <>; Tue, 18 Dec 2018 23:08:11.844 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id BD0E380628 for <>; Tue, 18 Dec 2018 15:08:11 -0800 (PST)
Date: Tue, 18 Dec 2018 23:08:11 +0000
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2111/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Use "Insert Count" rather than "Largest Reference" (#2111)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c197ddbbbb1e_397d3f8a692d45b4485b6"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1QlowWIxJCGKyb9ShFNOV4YkfoNI9ml2Li8k nhMTYoML79QG1aBqTgbs7+COaRLd9dtV6uDPh6pp4gAo1jk5TXyREmtT1gEM6BHGLrdXJmIx/ZA9MA PACoq2pK+koDz71CLNk0xrCkwjcxmuWCEjWjteRX9MpDcUb1BbUOraWaVNQKZnz8aRkgRWKPSE1HjQ 8=
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 23:08:16 -0000

MikeBishop commented on this pull request.

I'm with Alan that this seems unnecessary.  Also, the largest reference and the number of entries inserted at the end of the encoding are often the same, but need not be.

 n = count of entries inserted
 d = count of entries dropped
 {: title="Example Dynamic Table Indexing - Control Stream"}
 Because frames from request streams can be delivered out of order with
-instructions on the encoder stream, relative indices are relative to the Base
-Index at the beginning of the header block (see {{header-prefix}}). The Base
-Index is an absolute index. When interpreting the rest of the frame, the entry
-identified by Base Index has a relative index of zero.  The relative indices of
-entries do not change while interpreting headers on a request or push stream.
+instructions on the encoder stream, relative indices are relative to the Base at
+the beginning of the header block (see {{header-prefix}}). The Base is encoded
+as a value relative to the Insert Count, so it can be expressed as the number of
+entries inserted. The dynamic table entries up to the Base can be referenced.
+The most recently inserted entry within the limit set by the Base has a relative
+index of 0.
+Though new entries could be added while processing a header block, the relative
+indices of entries do not change.

In theory, you could process instructions on the encoder stream in parallel with interpreting a header block.  However, more likely this refers to entries getting inserted during encoding, and this is the wrong terminology.

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