Re: [quicwg/base-drafts] Allow extra data after self-terminating h3 frames (#2291)

Lucas Pardue <> Mon, 07 January 2019 20:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4A95112DDA3 for <>; Mon, 7 Jan 2019 12:16:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.936
X-Spam-Level: *
X-Spam-Status: No, score=1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_SUMOF=5, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OMyQmbHQRqsF for <>; Mon, 7 Jan 2019 12:16:12 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 12B1812D7EA for <>; Mon, 7 Jan 2019 12:16:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=+xf3/5C6ereYJcxpG0/Y0EltLKU=; b=LgnJcsceIrrVITAF vb3lLlqWFUq/N+Gb3Tey9Fg0NOQ+QcznpLGjChVZyeU4hEoxVmHF7WSAW4ChbPqs P1EAe1DofCURA0chS8g7ww20yOFgW4LbptYSHuCewg1YM13eBWsDpPZ/qWrF/YtL MkNSONq8Ql2jsoFJ3mN42YTnwHU=
Received: by with SMTP id filter0339p1iad2-17938-5C33B389-14 2019-01-07 20:16:09.462777362 +0000 UTC m=+321840.847074215
Received: from (unknown []) by (SG) with ESMTP id -WEoglYVTQiK8IP0TaVvcw for <>; Mon, 07 Jan 2019 20:16:09.420 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 630BBC18E1 for <>; Mon, 7 Jan 2019 12:16:09 -0800 (PST)
Date: Mon, 07 Jan 2019 20:16:09 +0000
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2291/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Allow extra data after self-terminating h3 frames (#2291)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c33b389613a6_72a43f90c74d45bc79456"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0qxpcXA8Dlejb26cjm0vqRMW/rWL12tSheyB f4shad5uCXE689LwidgVZxvYmODpLwppT2/OVDBeJv9ApIQ8RR8CQR7Cbfso4QWiJhD0kWSAyW3i3X Xqu7pAhev7kf9H/F3NCvXfd26/pdqPIJyXRdT5yefLjlxNjhwVTRzZ+3zwsC/uRSpWMNEOH2uYXeNH 8=
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, 07 Jan 2019 20:16:13 -0000

Ok but that seems tangential to this ticket's request AFAIK (which may be wrong). I thought the ask was to enable arbitrary fields after the core H3 frame fields. Done by using the delta between how large the frame says it is and the sum of all frame fields.

In the case of GOAWAY it's simple. But imagine I start sending extension frames on the control stream. If you know the type is not supported in your receiver, you can just ignore length bytes and carry on. 

I appreciate the want to reduce some complexity but it seems like we'll end up with an inconsistent set of frame types (TLV vs TV) without much spec text /guidance to support it. 

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