Re: [quicwg/base-drafts] [HTTP/3] [editorial] Remove mention of redefining setting format. (#3220)

Mike Bishop <> Tue, 12 November 2019 17:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 916EC120992 for <>; Tue, 12 Nov 2019 09:58:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 rHxWm3L7Ghcy for <>; Tue, 12 Nov 2019 09:58:31 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E4718120991 for <>; Tue, 12 Nov 2019 09:58:30 -0800 (PST)
Date: Tue, 12 Nov 2019 09:58:30 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1573581510; bh=NZNoBr9U+7OWyFFQcigPOST8iWkAC7EWgj22z5DZFgg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=m+mDOnMT1/lo8+vN8mXjLVHdsCGY2fmpsXKOlsGTR1qaCvt67BktQHlYkNBA8Mi1B CzMw9z+ZbtEnA4YOk7y4ZrFa1abPvC5By2MPcr7OCbyEqvX4Q/V7Kz3u8lQo5W11wy LwWksDDc5WHesQANt9hJyQVdRA9FCzy1PmniVrk4=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3220/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] [HTTP/3] [editorial] Remove mention of redefining setting format. (#3220)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dcaf2c63fbb6_7bac3fd1804cd95c3207ec"; 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
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, 12 Nov 2019 17:58:32 -0000

MikeBishop approved this pull request.

> @@ -1941,7 +1941,9 @@ In HTTP/3, setting values are variable-length integers (6, 14, 30, or 62 bits
 long) rather than fixed-length 32-bit fields as in HTTP/2.  This will often
 produce a shorter encoding, but can produce a longer encoding for settings which
 use the full 32-bit space.  Settings ported from HTTP/2 might choose to redefine
-the format of their settings to avoid using the 62-bit encoding.
+their value to limit it to 30 bits for more efficient encoding, or to make use
+of the 62-bit space (for example, if encoding the original value often requires
+eight bytes anyway).

This parenthetical feels kind of awkward; maybe just something like "or might choose to make use of the 62-bit space if more than 30 bits are required"?

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