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

Martin Thomson <> Mon, 09 December 2019 04:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ABFDC1200CD for <>; Sun, 8 Dec 2019 20:20:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.522
X-Spam-Status: No, score=-6.522 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, RCVD_IN_MSPIKE_H2=-0.14, 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 OYxy7XUMAdxI for <>; Sun, 8 Dec 2019 20:20:06 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C2EEB1200CC for <>; Sun, 8 Dec 2019 20:20:05 -0800 (PST)
Date: Sun, 08 Dec 2019 20:20:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1575865205; bh=2/qugfccoS82dhyeaBrDrwyBSk+2KQG6oPtNL25zD2M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=E6v3/pHkoxQI5H4kLFEhP7qmTuw5vPNPQHFqJP2VUWm2wXKju3ZtwRqgFGmpZYo7L NYIWUXaWRGfzBrs4pSW4PN1Y2+VeyLu+W8T6Z54IhVLHR53xUQzgLiZLKFgub43ZGq V0P1ihKqRW2VOmHRxi2FWv+bgOZ1VjnAbcLV2SuU=
From: Martin Thomson <>
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_5dedcb75877a_75073fefccecd9604236b3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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 04:20:08 -0000

That nuance is already possible: if the application wants to hand the transport this power, it can.  It can provide a default code for the entire connection; or more complex expressions of policy can be made (e.g., even streams get code X, stream Y gets code Z, otherwise don't touch).  That is a negotiation that can be managed at the interface between application and transport code.  Without that information, the transport is always able to access the final solution.

As for the suggestion that an application can ask the transport to use one of its own error codes with CONNECTION_CLOSE (0x1c/transport), that's another negotiation for the API they share.

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