IETF Logo Mail Archive

Re: [quicwg/base-drafts] STOP_SENDING in Ready state (#1797)

MikkelFJ <notifications@github.com> Thu, 15 November 2018 18:43 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 9DA9312F1A6 for <quic-issues@ietfa.amsl.com>; Thu, 15 Nov 2018 10:43:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.471
X-Spam-Level:
X-Spam-Status: No, score=-3.471 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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 vtUlSUv6O5kl for <quic-issues@ietfa.amsl.com>; Thu, 15 Nov 2018 10:43:01 -0800 (PST)
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 0CE04127598 for <quic-issues@ietf.org>; Thu, 15 Nov 2018 10:43:00 -0800 (PST)
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=fug258Va7dIYLJeE+cyPkqSgx48=; b=albFppVgCWC85srX TY1bHF0Z9PKmpW977SG38PirC2/16MSGLBqLfWvx06TQJI3KBOWPmz/ciofo0MmU CTrnTTT7Nx2FKCcRW07EBZlaLoQ/C2s1yA522ExO3PIzzl6p6KBin1s9PkrYLZz5 hBSIY3j+xCZqxhXauOBlT8TK4lA=
Received: by filter1493p1mdw1.sendgrid.net with SMTP id filter1493p1mdw1-19287-5BEDBE34-A 2018-11-15 18:43:00.185714523 +0000 UTC m=+694274.537359551
Received: from github-lowworker-97d0962.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0012p1iad2.sendgrid.net (SG) with ESMTP id 5w8ifkiaS9e-dX7WsmqN6g for <quic-issues@ietf.org>; Thu, 15 Nov 2018 18:43:00.155 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-97d0962.cp1-iad.github.net (Postfix) with ESMTP id 2D74180D37 for <quic-issues@ietf.org>; Thu, 15 Nov 2018 10:43:00 -0800 (PST)
Date: Thu, 15 Nov 2018 18:43:00 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1f659d40cf9be4dc9f06e1a07834dc347a12bbe792cf000000011805803492a169ce15ad130f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1797/439146964@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1797@github.com>
References: <quicwg/base-drafts/issues/1797@github.com>
Subject: Re: [quicwg/base-drafts] STOP_SENDING in Ready state (#1797)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bedbe342b94f_48723fe36c6d45b837529"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3c6mhJ3wHeIKTQKy7ee5lUa9x/Avvri9Zg91 Sda+Ed+ZnZPjTCwDxu452bOde6mwb26cfEwY+O28DgghrCmOgx/jIa/gXxk1jfwRhPSG7XkC+q40c0 YoIKYAfgMskJ/+CYs+SGo/ZiXmv4HHzs7pI8Y8lDv120lCQcHoao0gWKBg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/66mahtsefkzXNguYLm65i63_QrA>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Nov 2018 18:43:03 -0000

I think it should be permissable to receive STOP_SENDING on a Ready stream because a stream is only ready if a higher stream has been created and started sending (I think). When the receiver sees that transmission it would know that earlier streams are potentially able to transmit (and addition to being ready to send). If the initiator does not want to waste state on tracking STOP_SENDING, it should not transmit on a higher ID first.

Alternatively, we should just accept this limitation - that you can't stop a transmission before seeing evidence of it being active. All the implicit open logic is about being able to transmit while STOP_SENDING affects the peers send state - which is unfortunate. It's really bordering cause/effect in particle physics (not entirely coincidental).

-- 
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/1797#issuecomment-439146964

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