IETF Logo Mail Archive

Re: [quicwg/base-drafts] Is it permitted to send both FIN and RST (#779)

MikkelFJ <notifications@github.com> Thu, 21 September 2017 23:34 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 5A4531332D4 for <quic-issues@ietfa.amsl.com>; Thu, 21 Sep 2017 16:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.018
X-Spam-Level:
X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 Oz848CRQyeLD for <quic-issues@ietfa.amsl.com>; Thu, 21 Sep 2017 16:34:48 -0700 (PDT)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A244C132620 for <quic-issues@ietf.org>; Thu, 21 Sep 2017 16:34:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=jWIoswqvsrzXgRMmNO7t/uwWOHE=; b=FLqqryD3aTCy3H1b PW+ALo1MT2BRdBvzaM//GGMl7UD0xdxxIJiDT2p72HVkCGIlveHW9ndQdMc6hhXX y7wLlNf/eZ69ubvysCo8aGEXfi6v8mYxbTRdJm6MLPAkdHjfiiSI80Ltmvjs4nph JHk1vMTLA0llM04EIVHNo6Vp4ZE=
Received: by filter0442p1mdw1.sendgrid.net with SMTP id filter0442p1mdw1-3045-59C44C7D-2C 2017-09-21 23:34:21.891691891 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0001p1iad2.sendgrid.net (SG) with ESMTP id oWSbb87JQye1gvxkUQE0Ow for <quic-issues@ietf.org>; Thu, 21 Sep 2017 23:34:21.900 +0000 (UTC)
Date: Thu, 21 Sep 2017 23:34:22 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abda6c6069fd7909797c137ed0e4445d37a7824fd792cf0000000115dc0e7d92a169ce0f6cdc16@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/779/331309913@github.com>
In-Reply-To: <quicwg/base-drafts/issues/779@github.com>
References: <quicwg/base-drafts/issues/779@github.com>
Subject: Re: [quicwg/base-drafts] Is it permitted to send both FIN and RST (#779)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59c44c7dc37c5_7c863f8e8186cf7860737"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3Ctyb9raiiu4UmWa1RBcWqBupRLN/p0jv4oW 6WIum2sktQByJKH+uS0ahYKkaNHcqLo0PfHnW0jwaXtu/mksohlHly8YF8w9tDCHSuHyWgRF2XUgkl j1pvqIBxq5ffggCi4+T8vQG9/JlE6L4ElIUdV79/HtZv5Ofy1Dlpmj5mxZveOPOjZq/gsXlRUAjmU/ U=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/l26oql0o6dbEKD3pbP6-_xM99sU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 21 Sep 2017 23:34:50 -0000

Receiving RST after FIN complicates transport to application signalling in the receiver because QUIC cannot optimistically signal that at got FIN at a given offset so, e.g. application can go ahead and reserve resources in anticipation of inbound data. It might be simpler for the sender to send all data except for FIN until it is certain that the data is relevant, or send RST instead. This could lead to extra frames, or not, depending on timing, but if could also make sense to send data ahead of time and withhold FIN for quite a while (say waiting for other operations to succeed), and then an extra frame for FIN makes perfect sense - leading to low overhead finalization for the stream.

-- 
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/779#issuecomment-331309913

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