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

Nick Banks <> Mon, 09 December 2019 15:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 451B4120089 for <>; Mon, 9 Dec 2019 07:05:15 -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 e9P-25Qb8Aye for <>; Mon, 9 Dec 2019 07:05:14 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E5E30120043 for <>; Mon, 9 Dec 2019 07:05:13 -0800 (PST)
Date: Mon, 09 Dec 2019 07:05:13 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1575903913; bh=fniaUeLVd2U+1bK8DrFBTvUOkc2EsJRZP3oPwI7vKhU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Mz3SyCZQ42SL5xWCo4XKnW+e3C1pmzvmBjSq8eIZSshLeGXsM99ruWtJJ7Czq5a1j K+5V22FjKhfi9s06LgdIH1WV+SAxJ6X2PkAfH3Bw1QhJFDJvJPvTiBOf6sRS1U7jDo PnJ6ZWGpcmeiCmK3fMXaBfLXdX7/hJ/NsFgGlTqM=
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_5dee62a925cbe_bc33f9cc18cd96019276e"; 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: Mon, 09 Dec 2019 15:05:15 -0000

So, it seems the WG has no appetite to change the protocol for this scenario. Implementations are stuck with one of the following options then:

1. Close the entire connection with a transport error code.
2. Require app input for the default error code, and close the stream with that error code.

(1) is much simpler, IMO, so that will likely what I'm forced to go ahead with. Thanks for the feedback.

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