[quicwg/base-drafts] PRIORITY frames from server should be Connection Error (#2507)

martinduke <notifications@github.com> Fri, 08 March 2019 21:09 UTC

Date: Fri, 08 Mar 2019 13:09:17 -0800
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abaf65370f1e155d1715b40388cbbd6376117ffc6a92cf00000001189a9bfd92a169ce18f8cbfa@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2507@github.com>
Subject: [quicwg/base-drafts] PRIORITY frames from server should be Connection Error (#2507)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c82d9fd84c50_d673faf754d45b8748832"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/E2LDJo4W_bDlyUeLm05eeIEFmo0>

the very end of Section 4.2.3 of quic-http says:

   PRIORITY frames received by a client MUST be treated as a stream
   error of type HTTP_UNEXPECTED_FRAME.

Elsewhere, this kind of thing is a connection error. Making this a  stream error seems problematic; if otherwise valid, if this goes out on the control stream a stream error may bring everything down anyway?

Here is the mailing list thread:
https://mailarchive.ietf.org/arch/msg/quic/ODlqMOxUP9W5RcZ5UIjTp2lKh4U

I believe the consensus is to make it a conn error; PR to follow.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2507

[quicwg/base-drafts] PRIORITY frames from server … martinduke
Re: [quicwg/base-drafts] PRIORITY frames from ser… Mike Bishop