Re: [quicwg/base-drafts] Allow the Transport to Stop/Reset a Stream? (#3291)

Lucas Pardue <> Sat, 07 December 2019 19:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2A0E4120831 for <>; Sat, 7 Dec 2019 11:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_20=1.546, 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 l_uSD3C6Ffrx for <>; Sat, 7 Dec 2019 11:33:24 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E530E12082E for <>; Sat, 7 Dec 2019 11:33:23 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 7475D26166C for <>; Sat, 7 Dec 2019 11:33:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1575747203; bh=exf77ZOjFxEY5PkwZzX+Zb6RgC2V4v6WksylXdV6dwk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Wp8tLCp44lcpywq0T7dTbXxgFpxYFpjoOwxs2hx+P0woUYmbUHAgbVbejBU7ZccVZ YGs1hViFqaiHxIgJauPIjSpLEbBH5O4fodBz+iGIB+12Ae4cbI/+15g4IEvn53Kqnw KMeU1WO6auyvvopV6W6sCh3U8QSv04iTiK+cQY7I=
Date: Sat, 07 Dec 2019 11:33:23 -0800
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3291/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Allow the Transport to Stop/Reset a Stream? (#3291)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5debfe832ebe4_79763ff6c90cd9605678c5"; 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: Sat, 07 Dec 2019 19:33:25 -0000

Taking the opposite view, adding this capability would add complexity to HTTP/3 because not only do we have to document actual stream errors and their effect on the connection, but with this we'd have to describe what happens when the transport aborts streams. I don't see it adding anything useful for HTTP/3.

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