Re: [quicwg/base-drafts] Does minimal frame type encoding apply to extensions? (#3402)

Kazuho Oku <> Fri, 31 January 2020 04:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 52058120168 for <>; Thu, 30 Jan 2020 20:58:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iMsdl6UmZbEr for <>; Thu, 30 Jan 2020 20:58:01 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 98BFA120044 for <>; Thu, 30 Jan 2020 20:58:01 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 2BD5D66003A for <>; Thu, 30 Jan 2020 20:58:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580446680; bh=UOWw/t8tcKteUYLK82jKUi/OgD5FCo68hkpQPwkJnb8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SpCXZmLwRd+ZbXkYOe/0pe4q7Yd1OwtfygUodT7tO8p4mteEZtTp739ZD4CHvcO1Q yKOhnv/SWKfqnhqRrlIqen6osjEwAMyJhUIuNlSHDZjsBxMogPWd7g56RsYuHa4m+7 9dTEOXP45DwpD58NgdZw8QpSOXgOpoq+xtpGOU7E=
Date: Thu, 30 Jan 2020 20:58:00 -0800
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3402/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Does minimal frame type encoding apply to extensions? (#3402)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e33b3d81be9a_17f33fb0f8ecd964332d6"; 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: Fri, 31 Jan 2020 04:58:03 -0000

@marten-seemann See #1473.

IIRC the rationale for using *minimal* varint encoding is that stacks that support only the standardized frames can live with a simpler dispatch scheme that takes *one byte* as an input (i.e. the dispatch method being a table or a switch clause).

While I do not have a strong opinion regarding that requirement, I'd prefer not revisiting the discussion.

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