Re: [quicwg/base-drafts] How should an HQ server respond to RST_STREAM? (#1596)

afrind <> Mon, 23 July 2018 20:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 43C6B130F35 for <>; Mon, 23 Jul 2018 13:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 7xITAhTqi0od for <>; Mon, 23 Jul 2018 13:38:36 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8E605130E25 for <>; Mon, 23 Jul 2018 13:38:36 -0700 (PDT)
Date: Mon, 23 Jul 2018 13:38:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1532378314; bh=V4fJQ3t43gtJI2afP7OLXEGBSQxNmdXpqC1q9WU2SkU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MDbdYMg0oAzwkh+mhY8DmwNTRwDqoGIU+m4GsWtXFyc2jUOf8RdVolo00cqRFGLCu NqCY6qxOSZsyPJXOFYoF7bKyp9wANbSYySfFsiTOxxOnguB88jypGTDl1pDA79MLva 4OWAxom7HW8TSuxNsFtCNTRfvAflhNMUa3CxZv60=
From: afrind <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1596/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] How should an HQ server respond to RST_STREAM? (#1596)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b563ccabc483_76353fb80b0be624907fa"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: afrind
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.27
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, 23 Jul 2018 20:38:38 -0000

I don't want to FIN a stream in response to a RST.  For me, FIN implies successful completion and RST applies some kind of exception.  I read section 3.1 to mean that if I shouldn't abort the response if I receive RST_STREAM/STOPPING (eg, I asked for one via STOP_SENDING).

NO_ERROR could be OK, though perhaps something with more semantic meaning would be better.  "I'm terminating my half because you terminated your half".  STOPPING more closely matches that but is reserved for transport.

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