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

Bence Béky <notifications@github.com> Tue, 12 November 2019 18:44 UTC

Return-Path: <noreply@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 2780E12080F for <quic-issues@ietfa.amsl.com>; Tue, 12 Nov 2019 10:44:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
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: 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 L1SSvmDlrT64 for <quic-issues@ietfa.amsl.com>; Tue, 12 Nov 2019 10:44:22 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A5D01200DE for <quic-issues@ietf.org>; Tue, 12 Nov 2019 10:44:22 -0800 (PST)
Date: Tue, 12 Nov 2019 10:44:21 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573584261; bh=aQ9pd4zVfPK7A92v84NwDMC+8X3kFomcRgGGIYFfAvw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qW1pYFXgmwrZFR6VnGhCYcjhRlJFhAQ5GIXTZJ2wnE4WKu2X+NAbtf3znEb5Gmcm5 sASOuICxH01z6wrLJb8CgNCtivK4JwUMwrY0QwKhb4QHt6xoqqn1rkfTZ9AbN635Hl DqQ2iPdvMBfqUgCj8iQgfAw4+4yfJt3BnEerK4tY=
From: =?UTF-8?B?QmVuY2UgQsOpa3k=?= <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZROSOG5IZPN5CYO6F33AYALEVBNHHB6EDTZQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3220/review/315758358@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3220@github.com>
References: <quicwg/base-drafts/pull/3220@github.com>
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_5dcafd859427d_1ce53fb90e4cd964578161"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: bencebeky
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ZfshRazcbVnVvZ2ubtvq7jn9eek>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Nov 2019 18:44:24 -0000

bencebeky commented on 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).

Thanks for the suggestion.

-- 
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/pull/3220#discussion_r345378768