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

Mike Bishop <> Tue, 07 August 2018 16:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A418A127AC2 for <>; Tue, 7 Aug 2018 09:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, URIBL_BLOCKED=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 Irur1Pihx42O for <>; Tue, 7 Aug 2018 09:29:39 -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 7C3F3130EF0 for <>; Tue, 7 Aug 2018 09:29:39 -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=yB4ssA+wH/Q8zAEQUj2WsrvryDc=; b=epy05U2X3IJStVB4 fjJxuda1taDeR6T3xecahEVofbHpzTM6UpQ1mljNwIl/cSePvb51p4KEoV/b/skz /iTtIsqQLJQNTBB4GXKsmWix0w1hWQMTYTGD7JHUE7T+eT5SWIEh9etEbHLW3A1v I4VD0ctDORH43LVvqXxpn3F4Xsk=
Received: by with SMTP id filter1752p1mdw1-1285-5B69C8F2-9 2018-08-07 16:29:38.369431002 +0000 UTC m=+1101850.727391424
Received: from (unknown []) by (SG) with ESMTP id ZDKI2h5pRiyxv94JbEUX0Q for <>; Tue, 07 Aug 2018 16:29:38.278 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 562DCC0B01 for <>; Tue, 7 Aug 2018 09:29:38 -0700 (PDT)
Date: Tue, 07 Aug 2018 16:29:38 +0000
From: Mike Bishop <>
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_5b69c8f254183_423e3f945e2be6203761a4"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak33RtOSmsPzVsYY+39JNIE+w13t2p7016g+7S 6DhcAY2L0bVvdmmf/bCAcHiOUfU8fJ9r9ywNduvx11TTv1L1cVijH5GYEA4rO1Qx0BtAu9flehwrEW 4ILFs7zBt35rIqGbgWHesWxS3QcJr4Ip0XSrC4ors3qYtVvuEFxXOfut6gkQBFjr+nrPlMA2wQz6wU M=
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, 07 Aug 2018 16:29:42 -0000

That could be specified in four bits, true.  I could be convinced that cutting a byte off the length for every setting value saves more than being able to omit the value for booleans.  The original reason for having an arbitrary-length field was extensions that needed to supply a large set of supported values, such as supported signing algorithms for the CERTIFICATE_PROOF in the originally-adopted version of Secondary Certificates.  So the goal was not only to save bytes from settings that didn't need four bytes, but also to provide extra bytes to settings that needed complex, structured values.

However, the need to negotiate such complicated items has been delegated to TLS in that instance and hasn't shown up elsewhere.  We might simply say that if the need crops up for some future extension, they'll need to define an additional frame type to carry that configuration data.

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