IETF Logo Mail Archive

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

Mike Bishop <notifications@github.com> Mon, 11 November 2019 20:54 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 1D0A6120825 for <quic-issues@ietfa.amsl.com>; Mon, 11 Nov 2019 12:54:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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_24=1.618, 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 HJzUTdsmbXtk for <quic-issues@ietfa.amsl.com>; Mon, 11 Nov 2019 12:54:31 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E1F9120169 for <quic-issues@ietf.org>; Mon, 11 Nov 2019 12:54:30 -0800 (PST)
Received: from github-lowworker-3a0df0f.ac4-iad.github.net (github-lowworker-3a0df0f.ac4-iad.github.net [10.52.25.92]) by smtp.github.com (Postfix) with ESMTP id D1F382C0B99 for <quic-issues@ietf.org>; Mon, 11 Nov 2019 12:54:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573505669; bh=41tpPXPnUfWx4I8Pu6g6xFUoqf4UuRMcUwu9QccUMes=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tJkcttqUGAcWym4/3pZIX555eRJ89NBMkT8wj5wnL7SQ6FUstuQbuMxT1Uiz18G1x ZIc7o57Or+g9DhZLjsZHARtYWQ9kj4h2gPmECbuQpGo+jK7rpPKt2zydMQMM6VBx8E F2EODeHntgh2KRDpQ041xPsDKi7yMpQsn8AlpfAw=
Date: Mon, 11 Nov 2019 12:54:29 -0800
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7IWJ4OFJFNWETSF6V3236QLEVBNHHB6EDTZQ@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/c552611318@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_5dc9ca85b26d0_1ce33f8b42ccd960953221"; 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-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/AHuWBBjadhcTPJ404WE7FJeJ0D8>
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: Mon, 11 Nov 2019 20:54:33 -0000

No, it's not.  It's a warning that, *due* to the varint encoding, if you use the full 32-bit value space from HTTP/2, you'll get encoded into 64 bits in HTTP/3.  For example, Secondary Certs sends a four-byte binary value in its setting; keeping the identical definition in HTTP/3 would waste space.

Such extensions should either restrict themselves to 30 bits (to fit in the same size) or make use of the 62-bit space since they'll be encoded into that size anyway.

-- 
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#issuecomment-552611318

v2.23.0 | Report a Bug | By Email