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

Geoff Kizer <> Thu, 12 December 2019 20:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7C14C1200E6 for <>; Thu, 12 Dec 2019 12:57:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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_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
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id X_cKO7pdWosN for <>; Thu, 12 Dec 2019 12:57: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 E9467120024 for <>; Thu, 12 Dec 2019 12:57:23 -0800 (PST)
Date: Thu, 12 Dec 2019 12:57:23 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1576184243; bh=C5oQvOBBisS3MfcdkYAptI9/7sqtyC13NpwmRNFSkCE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xYNx84bYABwLc8YnsTJw8MzMicqYUenOXMj0Qd8qN7Ooco7lqz72LDfIRAPpr8F5a rloZD+Sadhm4+JxP1nh0Sle2oVnMduSkUkJGNC6HfDTPlTYfC21maqxjlBqu94h5qo KDijMDPs5cXR1rFBXc/8u/jA2sy3NENhqQPzJLs8=
From: Geoff Kizer <>
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_5df2a9b3f140_11f63ff58f6cd968397762"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: geoffkizer
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: Thu, 12 Dec 2019 20:57:25 -0000

> Having a stream open and idle is not in any way an "error".

The case I'm describing here is not simply an idle stream. It's a stream that is no longer accessible by the user. Without intervention, it will simply never perform any further action and never terminate. This is user error.

> (Of course if a transport REALLY REALLY wanted to kill streams it could just require the application's "internal error code" to be passed in along with the application's ALPN string.)

Yes, that's a possibility. But it seems rather strange to *require* passing an error code that is only needed when you write incorrect code.

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