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

afrind <> Mon, 16 July 2018 20:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B4612130E2C for <>; Mon, 16 Jul 2018 13:50:42 -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 i3bxjBZY_47F for <>; Mon, 16 Jul 2018 13:50:40 -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 946D4130DD0 for <>; Mon, 16 Jul 2018 13:50:40 -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=seAid4iKPjRFwqmFg+Kqy09TY0w=; b=skWm2dRN8rR3Rwed Cb5KUdeKu0MKTIT13/Fyy3W+gymLrunscT18ZsANCruMuDTjYG+2PIEcZoac9XTc F+9SZ5S64UeZC/vj6o8fm/iCdA/dyofDDBUPkrog33BmcQkle0xTcE/N8ooNnzdp GUgdW47xvKq4cPHUSRNwCAE799E=
Received: by with SMTP id filter0883p1las1-12436-5B4D051F-13 2018-07-16 20:50:39.371142872 +0000 UTC m=+346294.220326675
Received: from (unknown []) by (SG) with ESMTP id iz3FEWi2RfWObXtYhpJIuw for <>; Mon, 16 Jul 2018 20:50:39.242 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 26B33420374 for <>; Mon, 16 Jul 2018 13:50:39 -0700 (PDT)
Date: Mon, 16 Jul 2018 20:50:39 +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_5b4d051f22f3f_7a3e2aacc6be8f503441e6"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0H2I/gdaBE4AufqUdT0H2cnHiFYrL7A7gRd+ FtnAdhYl4ucCxZkR06yvXQbe7TZr3BFjJ2Kcf0z0K42k0B4uT9xAO3v6Qs4Frz2qlCPvmHppTqje67 9l9ttE7j6mEN5p7z911q1ynIr8HrdDe0MMp5XvqSfqgC3LsEGPeg7IHMHA==
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: Mon, 16 Jul 2018 20:50:43 -0000

>  Integer encoding
>   Settings which are integers use the QUIC variable-length integer encoding.

So I don't think there's anything ambiguous in the current draft.  It is strange however that there is both a variable-length integer specifying the length of the integer setting AND the setting itself is a variable-length integer, so its length is self-describing and redundant.  

We could instead define settings that are integers use all of the `Contents` octets to specify the integer and take the length exclusively from the `Length` field of the parameter.  This would save a byte on the wire here and there (eg a parameter with value 100 currently requires 3 bytes to encode), and possibly make things a little less confusing, at the cost of having yet another way to encode integers.

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