IETF Logo Mail Archive

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

afrind <notifications@github.com> Tue, 31 July 2018 16:58 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59DDE130E35 for <quic-issues@ietfa.amsl.com>; Tue, 31 Jul 2018 09:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ep9NgsffLSPh for <quic-issues@ietfa.amsl.com>; Tue, 31 Jul 2018 09:58:05 -0700 (PDT)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14C4B130DEB for <quic-issues@ietf.org>; Tue, 31 Jul 2018 09:58:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; 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 filter1566p1mdw1.sendgrid.net with SMTP id filter1566p1mdw1-5518-5B60951C-12 2018-07-31 16:58:04.504148575 +0000 UTC m=+498517.848750962
Received: from github-lowworker-e8fa9ff.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0006p1iad2.sendgrid.net (SG) with ESMTP id 37g2y0zUQtutV06ld8mKtw for <quic-issues@ietf.org>; Tue, 31 Jul 2018 16:58:04.353 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e8fa9ff.cp1-iad.github.net (Postfix) with ESMTP id 4B0444207E1 for <quic-issues@ietf.org>; Tue, 31 Jul 2018 09:58:04 -0700 (PDT)
Date: Tue, 31 Jul 2018 16:58:04 +0000
From: afrind <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2c72d18b5d5f31e3706ac4d235274cc5bb73e02c92cf000000011778571c92a169ce14546a14@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1556/409293078@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1556@github.com>
References: <quicwg/base-drafts/issues/1556@github.com>
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-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1LVQfQ9qbwWtHtDqq4dhIQ9qCV3cjayqPIIR NiRUYpmp8MgEsOqfXjyf4gi0F6ChRKk/yyjq0CHif6QoWMif9NXrtPnfvse3dq92Lno29u5ZMoJ5Za NDtDiXiVSW3g2kpWds0kFRNq5uFaHXEMsfUtOhblk9e9PO4zrR3uF6GMeg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/G3xqfs2Tr6EkxUg9X53CeRqqYtc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=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:
https://github.com/quicwg/base-drafts/issues/1556#issuecomment-409293078

v2.23.0 | Report a Bug | By Email