IETF Logo Mail Archive

Re: [quicwg/base-drafts] Separate HTTP/3 stream errors from connection errors. (#2911)

Daan De Meyer <notifications@github.com> Thu, 26 September 2019 16:34 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D08D6120A7D for <quic-issues@ietfa.amsl.com>; Thu, 26 Sep 2019 09:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.281
X-Spam-Level:
X-Spam-Status: No, score=-6.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 HEbj0xTGNa0h for <quic-issues@ietfa.amsl.com>; Thu, 26 Sep 2019 09:34:38 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38066120809 for <quic-issues@ietf.org>; Thu, 26 Sep 2019 09:34:38 -0700 (PDT)
Received: from github-lowworker-6b40fdd.va3-iad.github.net (github-lowworker-6b40fdd.va3-iad.github.net [10.48.16.64]) by smtp.github.com (Postfix) with ESMTP id 925D9661E70 for <quic-issues@ietf.org>; Thu, 26 Sep 2019 09:34:37 -0700 (PDT)
Date: Thu, 26 Sep 2019 09:34:37 -0700
From: Daan De Meyer <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZEF4WUOER62LKVFTN3TIUS3EVBNHHBYDQKAQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2911/535584983@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2911@github.com>
References: <quicwg/base-drafts/issues/2911@github.com>
Subject: Re: [quicwg/base-drafts] Separate HTTP/3 stream errors from connection errors. (#2911)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d8ce89d835ea_73d43f93f48cd96864839"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DaanDeMeyer
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/F2CqVPttpsxX6L4YAwCg7V4aaN8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 16:34:40 -0000

I took a quick look at the changes and I my main argument that stream level errors do not make sense as connection level errors still applies. Instead of using stream level errors as connection level errors, I would use a general connection level error and use the reason phrase to add more detail on why an endpoint chose to treat a stream level error as a connection level error (I also think that the cases where it makes sense to do this are rather limited).

On the other hand, this is a pretty insignificant issue so I understand if there's no major motivation to change this when we're this late in the standardization process.

-- 
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/2911#issuecomment-535584983

v2.23.0 | Report a Bug | By Email