Re: [quicwg/base-drafts] Don't use bitmap frames to describe varint structures (#3115)

Kazuho Oku <> Mon, 28 October 2019 00:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B612612008D for <>; Sun, 27 Oct 2019 17:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id R7CjZi7WIML8 for <>; Sun, 27 Oct 2019 17:35:53 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4FE84120046 for <>; Sun, 27 Oct 2019 17:35:53 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 551AA660A70 for <>; Sun, 27 Oct 2019 17:35:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572222952; bh=8E1oYUlDrz5NmttX87U6a2VzvKoff9SnIPWjjMM4BcA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=i2lMcJA67Tf2iMk5kKmEl2T9PjpEUTj44HSAJS4L0o0SSMx4yhZ6JN0S9adxHXcP4 m9wTpPvDngAEx/TXRfvUQF/g/SvvF7MYirdN74zdTqxDpGB3O/fBcoYRk5M/eDctws kMu+aKTwmT+YKUlDZxlUvDAL9Xb3+k7pA6N/XdF8=
Date: Sun, 27 Oct 2019 17:35:52 -0700
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3115/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Don't use bitmap frames to describe varint structures (#3115)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db637e843703_4b7d3f85088cd96828847f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
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, 28 Oct 2019 00:35:55 -0000

I think I agree with @LPardue that for HTTP/3 it is beneficial to use same notation as in HTTP/2. I'd assume that we would be seeing extensions that cover both HTTP/2 and /3. It would be confusing to the readers of those specifications to understand two different notations.

I do not have a strong opinion on the transport draft.

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