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

Mike Bishop <> Tue, 08 January 2019 19:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 81175130FB7 for <>; Tue, 8 Jan 2019 11:23:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.064
X-Spam-Status: No, score=-8.064 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, HTML_IMAGE_ONLY_32=0.001, 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 L9ohFhQdC6of for <>; Tue, 8 Jan 2019 11:23:51 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AEF23130FB5 for <>; Tue, 8 Jan 2019 11:23:51 -0800 (PST)
Date: Tue, 08 Jan 2019 11:23:50 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1546975430; bh=ngYohHzZgq4WxBcWpDhpS5WSoDnBK9VoeckzFrhEJ5I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GwPL0xizWzMkeGeivv62T4xjLm3zTxMy+8cqtDcGqwRlK36rLOTm9TGSvXttdMa0G 23nfpSSrGgLtS4q4Qebiv2DEgK8xnrpq/fy4vgmp4rP+gjm5YpWG4kCf+9rRsUjTuL YIQKRDjzDyLqy6cLdZJey5/qZynuSUinTPm2KbBg=
From: Mike Bishop <>
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_5c34f8c6c2a4f_69233fafbcad45c02173ae"; 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
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: Tue, 08 Jan 2019 19:23:53 -0000

(Editor hat off.)

If you know that the peer understands the extended fields, then you've created an extension that redefines a frame type by mutual agreement, which is already legal.  Just redefine the frame in your extension, possibly with optional fields.

If you don't negotiate, the risk is that there are conflicting interpretations of this after-the-fields data.  In order to avoid that, you should move your particular interpretation / the extra fields to a new frame type.

I don't see a path in which stuffing excess data into a frame without negotiation is a wise choice.

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