Re: [quicwg/base-drafts] HTTP SETTINGS: define setting content encoding (#1556)

afrind <> Tue, 31 July 2018 16:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 59DDE130E35 for <>; Tue, 31 Jul 2018 09:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[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, T_DKIMWL_WL_HIGH=-0.01] 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 Ep9NgsffLSPh for <>; Tue, 31 Jul 2018 09:58:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 14C4B130DEB for <>; Tue, 31 Jul 2018 09:58:05 -0700 (PDT)
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=H4TlQWGLuCM2flsghs8cfxSaOC8=; b=X2Z1bTm+HwWiP1Sw oenWQrylwY+o5W6OV/QJsCGtZrhBBKfft9evBZxcw8DqhUaSoLNXGbN66tieTM4P 5AOj1tnZfge3ZMvFI49GWFbxnMfjWuEdW50RP7kH8ad2kKTHMOEQ7EXumrz/WW0r dlb8VkVwUnhWkpgkIFH8rocTIdM=
Received: by with SMTP id filter1566p1mdw1-5518-5B60951C-12 2018-07-31 16:58:04.504148575 +0000 UTC m=+498517.848750962
Received: from (unknown []) by (SG) with ESMTP id 37g2y0zUQtutV06ld8mKtw for <>; Tue, 31 Jul 2018 16:58:04.353 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 4B0444207E1 for <>; Tue, 31 Jul 2018 09:58:04 -0700 (PDT)
Date: Tue, 31 Jul 2018 16:58:04 +0000
From: afrind <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1556/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] HTTP SETTINGS: define setting content encoding (#1556)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b60951c48b2f_737f3fbf916d45bc11055e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: afrind
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1LVQfQ9qbwWtHtDqq4dhIQ9qCV3cjayqPIIR NiRUYpmp8MgEsOqfXjyf4gi0F6ChRKk/yyjq0CHif6QoWMif9NXrtPnfvse3dq92Lno29u5ZMoJ5Za NDtDiXiVSW3g2kpWds0kFRNq5uFaHXEMsfUtOhblk9e9PO4zrR3uF6GMeg==
Archived-At: <>
X-Mailman-Version: 2.1.27
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, 31 Jul 2018 16:58:06 -0000

We could define integer settings values to be 1, 2, 4 or 8 bytes, specified by a length byte, to avoid oddly-sized integers.  I'm not wildly crazy about having multiple ways of specifying integers, but I do think the current var-len-len plus var-len-value is both confusing and redundant.

Regarding booleans: I prefer making things explicit rather than implicit by their absence.  I don't think saving a byte or two in SETTINGS is a huge win.

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