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

Nick Banks <> Sat, 07 December 2019 21:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 902FB12006E for <>; Sat, 7 Dec 2019 13:47:06 -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 Ve0DtK7GGH6I for <>; Sat, 7 Dec 2019 13:47:05 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2FFD912004A for <>; Sat, 7 Dec 2019 13:47:05 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 525678C0099 for <>; Sat, 7 Dec 2019 13:47:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1575755224; bh=rSURS9qdNEYhMhrYrodYfqzaw3TJWoQqldcKzCIXCIQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BAMDidna5Yfw+DS86nwYJt8vg81o+SaPPQ2Db+wfF3dcYjj7VUAlSh9hypd05GM9i 3DuZjcTDJhTJXpHoo7NEMHyIZQJigQlmkn5sqOGfu2msXFMJ64ibu+g85zIFfBFGX2 NZUzIzIxdtal1NTqvBsCcVpO2gom5bnoIUB0qQiQ=
Date: Sat, 07 Dec 2019 13:47:04 -0800
From: Nick Banks <>
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_5dec1dd842e00_6fc23fb363acd96455603f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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 21:47:06 -0000

I don't see how it would add any real extra complexity. HTTP/3 must already have some sort of "Internal Error" at the app layer. You could very easily map a transport failure to precisely that. QUIC has to work standalone. It can't only work well when written along side HTTP, in the same code base; and I'd really prefer the solution not to be "just kill the whole connection" if this ever happens.

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