Re: [quicwg/base-drafts] Clarify the definition of things that make messages malformed (#3345)

Mike Bishop <> Wed, 15 January 2020 00:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 71AF2120058 for <>; Tue, 14 Jan 2020 16:18:44 -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 w22AvaxA4xHV for <>; Tue, 14 Jan 2020 16:18:43 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2119C120046 for <>; Tue, 14 Jan 2020 16:18:43 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 795D4660041 for <>; Tue, 14 Jan 2020 16:18:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1579047522; bh=ArEE+d2XHwTrl28lotale+1jSbdGo78pNt4dJUhQX44=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ck2v0n5P4YPAkw6lfsFkJ+7CCw9m6RvL3rxH+L8nkNlIm/pnBdaqLKxsZg7xegWRm YWmXwSUfuXPMMKDdK8Q9JT6rvrGSMhCOh/wFrwpaxdjNYuaTn/ovLyeZgRar30JmnP AYbAItFN82kWI8CoQFT9CnX5ABUnHnXMiX+nAYKA=
Date: Tue, 14 Jan 2020 16:18:42 -0800
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3345/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Clarify the definition of things that make messages malformed (#3345)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e1e5a626912a_52303ff33b6cd964811b1"; 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: Wed, 15 Jan 2020 00:18:45 -0000

Fair enough.  I think I'd like to generalize this issue:
- Invalid sequences of frames should be connection errors (DATA before HEADERS, multiple non-final HEADERS, possibly multiple trailers modulo #3265)
- Which header fields are prohibited and mandatory needs to be clearly stated; violations of this remain stream errors
- Upper-case field names remain stream errors

Let's make "malformed" more precise, and that should resolve most of our differences on #3300.

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