PRIORITY stream error?

Martin Duke <martin.h.duke@gmail.com> Wed, 06 March 2019 20:59 UTC

Return-Path: <martin.h.duke@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E23D126F72 for <quic@ietfa.amsl.com>; Wed, 6 Mar 2019 12:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RzoM2HQTd95Z for <quic@ietfa.amsl.com>; Wed, 6 Mar 2019 12:59:17 -0800 (PST)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EEDD126C15 for <quic@ietf.org>; Wed, 6 Mar 2019 12:59:17 -0800 (PST)
Received: by mail-wm1-x32a.google.com with SMTP id g20so7165436wmh.5 for <quic@ietf.org>; Wed, 06 Mar 2019 12:59:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=jDTP1glNR8s4pg54o2Mj3/ZpgVUbyY2r77Zg5/C8mbc=; b=lKj/XSB/hSzbGZeZkc5AopK1b6QVZAwKKQIxslMGs91qKtLJlRQoVKBTKaTuoXnnOP LWAxAFD96yOj1OJnvkLABhKGRKPZc9vA3BS8TcoAvybPAOIwHhzhULwVof/hc0SYItwq GJygc9FlSWQctWK+6Sq+o2W9cR9htBtayqM0sfoLXzCRuLjh3Qy748PpJitsUXIRALvO zyw53hvoopXY9tEAD/0ypIrABB1qG12Q2uGHHVVeZfyv+PRUrcfoINDsCIdlCzViWtFl f7hYieZhEelEY3zPd+RLU9PLMxykxjpiphnYBSx6cOx4SUe2AalcNmjKnfurWCZ2MC0A al1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=jDTP1glNR8s4pg54o2Mj3/ZpgVUbyY2r77Zg5/C8mbc=; b=crPJVtg1raDWJwnFqy0buiBCTUhwy2D1J4i7nUX1zUS+xcGm8ez9XSBjNm5kM9m4a/ NGCxbN4jzYkAKtF0wG1yKeYJmlzdgODaAPKurVEGgwtSXD8HdbSacgse/9MxZOhv1X9Y LHKuFufwH7nDt8kmvuCQRZp6zPMNT44EvhnYtkrdwUD7Rd1eFPQKGNTP2g/0Xx6SDseA hv6CPzGHn2KIzQIS92H0FUnskArWg7BbCVxz9bkNE3PbB1wv4JHqaabxr8RuqYmNzcb2 aj21CCzNHEHsFWt+Sbjz+wiYqS68MhcmgP523J4kDbPx9t8GqXV08Zq00kKjT4ht3vE8 R54g==
X-Gm-Message-State: APjAAAVWwVJRI9px2n+5fV3tsiMYdbd2YOzwKzCnyLTNcdeZF1eePyQ2 IxwZ9flOvj4oLw4O4JkhTtKFyc7hhtAm/m+MAOmB2GM7
X-Google-Smtp-Source: APXvYqxLxRx8gP7e20PB6S4wLuwqxRlXfT2kGLyvQ5FdBpwZYB4D4KeYP4eKfMGIGDEO/l3TRHOMk9LXKgheRmDAdTc=
X-Received: by 2002:a1c:e489:: with SMTP id b131mr3582812wmh.130.1551905955581; Wed, 06 Mar 2019 12:59:15 -0800 (PST)
MIME-Version: 1.0
From: Martin Duke <martin.h.duke@gmail.com>
Date: Wed, 6 Mar 2019 12:59:04 -0800
Message-ID: <CAM4esxRy-F5xjdQxc1sNt4atr840DtD9Z=L8nBUE-jvDZ9154w@mail.gmail.com>
Subject: PRIORITY stream error?
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003512ba0583734381"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ODlqMOxUP9W5RcZ5UIjTp2lKh4U>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2019 20:59:19 -0000

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?