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

Lucas Pardue <> Sun, 21 July 2019 14:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EF03912012A for <>; Sun, 21 Jul 2019 07:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, 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
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GYtpsr9kYwLE for <>; Sun, 21 Jul 2019 07:38:56 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4013A120136 for <>; Sun, 21 Jul 2019 07:38:56 -0700 (PDT)
Date: Sun, 21 Jul 2019 07:38:55 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1563719935; bh=AYakbBUAvMABjNSZ8UuvdfP7Ev+WVbkK+eT+p3wwnnc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1Bkk1GfSJhaiqQqQgpZHZk54X1Yu52Rap/ZTCru6utWRX+TsslgiwyEHsbV0IZkfW ENp4gFJu1iTkyAlQ+3x5kKQlGjydq1xDRYsrB+iY2zwXFd2QpN/bGVqwUOFBgFR9YU Gv+DA99GAn+wuTtmB5CDk3tiOphc48PnrqiSDk/c=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2911/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Separate HTTP/3 stream errors from connection errors. (#2911)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d3478ff5fe64_a003ff392acd96851562"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 21 Jul 2019 14:39:05 -0000

One of the thorny points to this discussion is that promotion of stream errors to connection errors is a feature of RFC 7540 Section 5.4.1

> An endpoint can end a connection at any time.  In particular, an
   endpoint MAY choose to treat a stream error as a connection error.

So deviating away from this behaviour means that the feature set diverges, which may add complexity to implmentations that attempt to support both (or propogate between H2 and H3

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: