Re: [quicwg/base-drafts] Inconsistency in STOP_SENDING requirements relative to resetting streams in general (#2884)

Martin Thomson <> Wed, 10 July 2019 06:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 827B2120105 for <>; Tue, 9 Jul 2019 23:53:18 -0700 (PDT)
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 iIWAdHemKS5a for <>; Tue, 9 Jul 2019 23:53:16 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3039C120103 for <>; Tue, 9 Jul 2019 23:53:16 -0700 (PDT)
Date: Tue, 09 Jul 2019 23:53:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1562741594; bh=9xwoPVpPSDTxjLdr0ncwyuf9M9cSuIBVsD/Vcd6j2To=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rP2jMKd9j0aKBnuXVg389kujNExQIxmNA2onUpeSEB0dly+KAJjg2HDM8hT3etmTT Q4VXb/q1StdKl8kcEfc9jlQsbuY9UPychyPCXc1pBpPz5M477O6SfInBgafizGU5gB VPw7CtXzVSe9u+bKgVPOlX9BEDPtGtDFXRH3sE64=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2884/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Inconsistency in STOP_SENDING requirements relative to resetting streams in general (#2884)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d258b5a7af16_74e43f8767ecd9603114529"; 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: Wed, 10 Jul 2019 06:53:19 -0000

I don't see any inconsistency here.  This is the relevant text:

> RESET_STREAM MUST be instigated by the protocol using QUIC, either directly or through the receipt of a STOP_SENDING frame from a peer.

This says that RESET_STREAM is only sent if the application protocol asks for it.  That means either the local stack or the remote stack.  

As you say, the transport is required to send RESET_STREAM in response to STOP_SENDING.  I can firm that up.

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