Re: [quicwg/base-drafts] http3: Are reserved and non-core frames allowed before SETTINGS? (#2693)

Lucas Pardue <> Sun, 12 May 2019 19:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B3DB112004A for <>; Sun, 12 May 2019 12:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.464
X-Spam-Status: No, score=-6.464 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 HTfKjGNoIDXB for <>; Sun, 12 May 2019 12:35:51 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 303C0120041 for <>; Sun, 12 May 2019 12:35:50 -0700 (PDT)
Date: Sun, 12 May 2019 12:35:49 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1557689749; bh=Ezrx9iGsEdfmw9x4jn++1upE+JgQmfjAIRW5ZyUNNqQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CMnY2HFP/L9hl7jHKT1UKM4MrER87c5NPbMu238YgJkpEkkL+/hNy8OUbtAuOwsl/ 0Pd4Zss1yHMJb8NDUSHm6DK7Mh4lbzIGMbTXNz584IboyvMD2e6cL0MHFfICL6AWLB iJ2R+d1/o6nbj/YO+nX+dPWI9hJ6JYtL3sTcKsCs=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2693/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] http3: Are reserved and non-core frames allowed before SETTINGS? (#2693)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd875958e4e4_47f93ffcbb4cd964561638"; 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: Sun, 12 May 2019 19:35:53 -0000

Thanks @lnicco you made me realise I asked the question wrong. 

This is about reserved *and* non-core frames. Section 7 says:

> Implementations MUST ignore unknown or unsupported values in all
   extensible protocol elements. Implementations MUST discard frames ...

I have no strong use case for delivering frames before SETTINGS. But I worry it falls into a slight grey area that might affect interop. I think the correct answer is that the control stream is special case and we should clarify that in Section 7.

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