IETF Logo Mail Archive

Re: [quicwg/base-drafts] ambiguity on reaction to RST_STREAM (#1671)

MikkelFJ <notifications@github.com> Thu, 16 August 2018 18:30 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4961130F9D for <quic-issues@ietfa.amsl.com>; Thu, 16 Aug 2018 11:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HGUDF32ICM7m for <quic-issues@ietfa.amsl.com>; Thu, 16 Aug 2018 11:30:28 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18292130F43 for <quic-issues@ietf.org>; Thu, 16 Aug 2018 11:30:28 -0700 (PDT)
Date: Thu, 16 Aug 2018 11:30:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1534444227; bh=qgo6suZKPWEb252mV3FJylaQSgDW6lFolomEiVQiOhs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vbejevR1Asr6XdhmXXxxlsOubnozNzehoHWdIaLWyPqDrorGylQj/J5Ey3o699k3/ AnuKjNlSaARaw3SvEMMdMTxf+DSTuB0j99V3uPuA1mtfoFEUNwGoQMibyzu2mJkB87 dYfMNFDyHVUv/CBfRZPSUiesR3t28z6nsE2mXJ9Y=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4546aa537a52cdefbf66965f6d471f186b4ad5d192cf00000001178d84c392a169ce14f025d9@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1671/413641949@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1671@github.com>
References: <quicwg/base-drafts/issues/1671@github.com>
Subject: Re: [quicwg/base-drafts] ambiguity on reaction to RST_STREAM (#1671)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b75c2c3344f9_1a143fa7d6ebe6243147c8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/g2UFq5HPOXl9X-nxlPcID4OU-Ss>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2018 18:30:36 -0000

OK, maybe I'm not up to speed on the spec then.

But as I see it, anything you send on a stream counts as send whether you later decide to RST or FIN. You have used capacity on the wire. The fact that you do not care about the data any more is just a sunk cost, just as if you bought a concert ticket and got sick.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1671#issuecomment-413641949

v2.35.0 | Report a Bug | By Email | System Status