Re: [quicwg/base-drafts] all HTTP/3 protocol violations should lead to connection errors (#2510)

Lucas Pardue <> Mon, 11 March 2019 20:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 136B21310BF for <>; Mon, 11 Mar 2019 13:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_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 XHlyanFDihcP for <>; Mon, 11 Mar 2019 13:41:58 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id ACE131293B1 for <>; Mon, 11 Mar 2019 13:41:58 -0700 (PDT)
Date: Mon, 11 Mar 2019 13:41:58 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1552336918; bh=NXsNJLSuKDZdlObRJxt/06CrKMyBnYu/0kcuKocSHLQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=T89oKrJSBTlxU28VwzirfoXHjDbxUzVS6HjMiBjcCxmXBG7OmovYTBUFwf9Fr5IGw PdHws6PvXqm2eqM3cTMk2TZp/Grfib6HNAk9y8r2TZi6wSpX/XIVbOjJcXqHaeTNOr GgV7+F2HOhfvTnWx9Do2aadR8eIUJK9XqbIW2zpc=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2510/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] all HTTP/3 protocol violations should lead to connection errors (#2510)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c86c816394b_19233f8e78ad45bc13351c"; 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: Mon, 11 Mar 2019 20:42:00 -0000

H2 discusses max header list size in the same breath as header block sizes *and* individual header field sizes. The concepts are conflated (perhaps for good reason). 

H3 changes some things. For instance there are no CONTINUATIONS and the header list cannot span more than on HEADERS frame. 

Furthermore, QPACK header blocks dont modify table state, so there are fewer dangers in refusing to process them (or not?)

There is more to this than meets the eye and I dont think we can unpick the problem space as part of this change. Suggest topic is discussed on list or at Prague 104.

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