Re: PRIORITY stream error?

Lucas Pardue <> Wed, 06 March 2019 21:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4CF89128CF3 for <>; Wed, 6 Mar 2019 13:27:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9tG1XfKsvSD0 for <>; Wed, 6 Mar 2019 13:27:02 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::a2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C2C7A126F72 for <>; Wed, 6 Mar 2019 13:27:01 -0800 (PST)
Received: by with SMTP id e131so3195121vkf.10 for <>; Wed, 06 Mar 2019 13:27:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yHJEFW9WSagbdLr9jjSSk4V/dFRvoAvuLyXhcur7pLs=; b=CtTCbzA+smmQfiVhdCEuDvw29NlLV0al1fifNn+IsMsR1vAOOITlT3CnknVSUvTNqc L/FI50qI/W9RN/pKcUKxh9f7AUcVCseNqe6y8HT46PllwL8oly3eAb04oJNRVwYsh2Bq xdoTxdSoeNHGEmgO/3OoHh6bi/o6RR+PHpaTMZ607Kbx9vW03WsxjLUbIjfEwW266Q7n NTEir2LzTePe2PhFoGaIm/o/tpy0WF0ADrvJERWNzml14nay3mnhyQHbGwUKQ1eU9oAx Mye0s1+wyyYzQ8euDevxl5NUg3jT61IgPonoWM+56NmjbfmrF/z0kG9rNJh2cDpguk0b 0fYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yHJEFW9WSagbdLr9jjSSk4V/dFRvoAvuLyXhcur7pLs=; b=cGSbDDASnmbbmTB5TAMH/M0BW+GcgawKh2NNfFG4qz1uL6HERHHCDQW61JHiH/QKwI /A7v9N0ZWLjdjRKygBXnF3hWxGNx89zpNqNh2pdS2yb2FRzlfRCClPY/wjyNYG2sHsvV q3Dev64LWM5gh9iCsaLU4Fa5Xh6dsZjRHflRL3Kdc440lXhBoZvtQSkQWNkadcsmng7x NKNg1EgvS3BRNbqF8w+Av0bUjEGCX4Ytk5AM3nYsvZPWBVv13rYxflTeR2TMrnsZw2GD WzJd/1WbgEmK7qI6VXHY9T7GZoOhnytHdOV3MEVbDxxHGd5sQ591gOW6MHzEOlG/Nmqe fAXw==
X-Gm-Message-State: APjAAAXFHfsoCxCO7qFIjJqK36fAXEbYPCYr9boiRpRQue7JrCPn5HOP 7s6T28F4P4XApGcJaN42SOu1MhnsiUXNJ1LOBRU=
X-Google-Smtp-Source: APXvYqzMni/vdJ1IyfNxGBBJKrtLixCJ5MGFIFgYZhE7i0BPsF/fGmFVm5Cf9++anIawwTEX9zXDd02dmR8xsfamcPc=
X-Received: by 2002:a1f:b9c4:: with SMTP id j187mr4347078vkf.61.1551907620751; Wed, 06 Mar 2019 13:27:00 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Lucas Pardue <>
Date: Wed, 06 Mar 2019 21:26:51 +0000
Message-ID: <>
Subject: Re: PRIORITY stream error?
To: Martin Duke <>
Cc: QUIC WG <>
Content-Type: multipart/alternative; boundary="000000000000758e17058373a646"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 06 Mar 2019 21:27:04 -0000

Hey Martin,

On Wed, 6 Mar 2019, 20:59 Martin Duke, <> wrote:

> 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?
> Should this be a connection error, or am I missing something?

My thinking is that if you send this in a RESET_STREAM  the other endpoint
knows what stream the offending was sent on. Just getting this in
CONNECTION close is quite a broad error.

Also note that endpoints are free to treat stream errors as connection
errors Iif they want, so you can go straight to that route if you want.