IETF Logo Mail Archive

Re: PRIORITY stream error?

Lucas Pardue <lucaspardue.24.7@gmail.com> Wed, 06 March 2019 21:27 UTC

Return-Path: <lucaspardue.24.7@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 4CF89128CF3 for <quic@ietfa.amsl.com>; Wed, 6 Mar 2019 13:27:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
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: 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 9tG1XfKsvSD0 for <quic@ietfa.amsl.com>; Wed, 6 Mar 2019 13:27:02 -0800 (PST)
Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com [IPv6:2607:f8b0:4864:20::a2a]) (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 C2C7A126F72 for <quic@ietf.org>; Wed, 6 Mar 2019 13:27:01 -0800 (PST)
Received: by mail-vk1-xa2a.google.com with SMTP id e131so3195121vkf.10 for <quic@ietf.org>; Wed, 06 Mar 2019 13:27:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; 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; d=1e100.net; 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: <CAM4esxRy-F5xjdQxc1sNt4atr840DtD9Z=L8nBUE-jvDZ9154w@mail.gmail.com>
In-Reply-To: <CAM4esxRy-F5xjdQxc1sNt4atr840DtD9Z=L8nBUE-jvDZ9154w@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 06 Mar 2019 21:26:51 +0000
Message-ID: <CALGR9oafBn0OEBFOsjzBbBwN8SxxEg8GuoG1kXTNL+yMdyr12w@mail.gmail.com>
Subject: Re: PRIORITY stream error?
To: Martin Duke <martin.h.duke@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000758e17058373a646"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iE9cfGUZBulr3SZaVxmcxyzkCzs>
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 21:27:04 -0000

Hey Martin,

On Wed, 6 Mar 2019, 20:59 Martin Duke, <martin.h.duke@gmail.com> 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.

Cheers
Lucas

>

v2.23.0 | Report a Bug | By Email