Re: [quicwg/base-drafts] HTTP/3 frame encodings are unnecessarily difficult to serialize and parse (#2396)

Lucas Pardue <> Thu, 31 January 2019 00:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D0839130FE5 for <>; Wed, 30 Jan 2019 16:16:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Status: No, score=-12.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 XGbhIZnM-qgl for <>; Wed, 30 Jan 2019 16:16:52 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B3D43131022 for <>; Wed, 30 Jan 2019 16:16:52 -0800 (PST)
Date: Wed, 30 Jan 2019 16:16:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1548893811; bh=YdiRvb3PtfgJILBgPK4hSOgD3FggJNi3DmBrnM3F3NM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MDo4c4gODs9SHotc+8vFL7hk/s/xCsGXO3m+OzL7PIdtQQziV1CKWTj6ddDVIzzoY PmSXaKTb82LwtKCwt9oYmFUrk1m2EtKyquxk69YJVqJnUGc5pc7r7Srvmpk2FWq3O4 y/Qj6tvuyV2uMWB7YD1zn8egEJbePrdrAwE8Ju3w=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2396/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] HTTP/3 frame encodings are unnecessarily difficult to serialize and parse (#2396)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c523e732a61c_608b3fb52d6d45bc566fe"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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: Thu, 31 Jan 2019 00:16:55 -0000

If we want to do this, we should still mandate that all extension frames
have a length, so endpoints can easily skip over them

On Thu, 31 Jan 2019, 08:42 ianswett < wrote:

> Multiple HTTP/3 frames have lengths, but do not require the length to
> deserialize.
> On the serialization side, those require extra work to determine the size
> before serializing them, which may or may not be easy. SETTINGs is fairly
> complex because it's a series of varints, so you either need to do a
> two-pass serialization or write the SETTINGs and then go back and write the
> length(possibly assuming it's a 2 byte length?).
> On the parsing side, extra work is required to verify that the parsed
> length matches the specified length.
> This also wastes a byte or two in a few cases.
> I suggest we use the principle that if it's easier to serialize and
> deserialize without a frame length then the length should be omitted.
> Related to #2395 <>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <>, or mute the thread
> <>
> .

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