Re: [quicwg/base-drafts] Stream closed state and acknowledgments (#743)

Igor Lubashev <notifications@github.com> Mon, 11 September 2017 19:33 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 7F79E1331A3 for <quic-issues@ietfa.amsl.com>; Mon, 11 Sep 2017 12:33:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 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, 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 iOTdZqLS6_w0 for <quic-issues@ietfa.amsl.com>; Mon, 11 Sep 2017 12:33:52 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 9E98A132F35 for <quic-issues@ietf.org>; Mon, 11 Sep 2017 12:33:52 -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=eD1pgmJgeRZtXcaLL/8O0yjjYNs=; b=WDTzDYGI/XbFh2Bo O71QTpfKRL3rUEZB/JjY5EOvon59IodbIcfw5fkR25n0kXmvip4vzpmMmVFl01Ap mCQSn/k7EAOE4ag603bC5ZbxZzsfold+iQqy+2wgjV2RwRa/4VKRXgk+2t3M6jhd aEiGwoS7TWPsLIpzPneIxKpu+M0=
Received: by filter0840p1mdw1.sendgrid.net with SMTP id filter0840p1mdw1-13150-59B6E51E-38 2017-09-11 19:33:50.489913349 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id KjSpF5gwRIKvvPQIkRnj5g for <quic-issues@ietf.org>; Mon, 11 Sep 2017 19:33:50.339 +0000 (UTC)
Date: Mon, 11 Sep 2017 19:33:50 +0000
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab86665bba5248c3c46d3163ed1467ff43928a147a92cf0000000115cea71e92a169ce0f025d79@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/743/328635021@github.com>
In-Reply-To: <quicwg/base-drafts/issues/743@github.com>
References: <quicwg/base-drafts/issues/743@github.com>
Subject: Re: [quicwg/base-drafts] Stream closed state and acknowledgments (#743)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59b6e51e3030e_44143fe84c213c381040a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2eyWKjADJlAiSiBfwPijgOgxRakZA192UDqR EjFkZcvugbzl7+P4Za0nSvdWeM5XzsIsn1ToaWQKWiCIhAQu1+Y6xcoG5u3aA+7poX74iv9K1ycFIV QKGRFCMa2AYIC7D5KtrGnpZNmkmNmbDKnE2LprIcacb8zpWByRUgtt7nas11BJXSfZSwH6wjtkjYSR M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/00Oy6HwVKYABoPcyYJdrQN6zTx0>
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: Mon, 11 Sep 2017 19:33:54 -0000

> Does a stream become closed when all data is sent the first time, or when that data is acknowledged?

Given that we've moved to max stream id, what difference does the answer to the question make?  Defining "closed" as "when FIN is sent" or "when FIN is requested to be sent" or "when stream.close() API function returns" makes for simpler state diagrams.  Defining "closed" as "when ACKs have been received for all data and the FIN" aligns better with possible implementations.

As far as possible implementations are concerned, "close" can be defined as when the implementation is free to forget all about the stream, except that it is "closed". That happens when "ACKs have been received for all data and the FIN" or when RST is sent.

-- 
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/743#issuecomment-328635021