IETF Logo Mail Archive

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

Mike Bishop <notifications@github.com> Wed, 26 September 2018 23:48 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 7D5E6130DD2 for <quic-issues@ietfa.amsl.com>; Wed, 26 Sep 2018 16:48:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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] 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 fJSqFKgoHKw0 for <quic-issues@ietfa.amsl.com>; Wed, 26 Sep 2018 16:48:08 -0700 (PDT)
Received: from out-12.smtp.github.com (out-12.smtp.github.com [192.30.254.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EB28130DCF for <quic-issues@ietf.org>; Wed, 26 Sep 2018 16:48:08 -0700 (PDT)
Date: Wed, 26 Sep 2018 16:48:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538005687; bh=SWH3gu/nEJUgIjU8G0q+Cda18Zvq23hsV2FJ0AVl1NE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EPfRVhZt+2F2NqbbjCjGlb6ehxDhNYORrt9utzEg7BXarIUR2mFVXPylxZ3wyrhI9 pBFZz/2kozn6qmPnY41FWHziL02+Z+4qWvCRLBhJMKx0oZD3nVJ4mfgMVuj6PHlm/K HSq9+hc9yYyvbapYwOoaoq++kAa055QxctW6tKMM=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab94c451bca19912b165fc9cbf2a38ac9d7178a50992cf0000000117c3dcb792a169ce15ad130f@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/424906757@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_5bac1ab776bf8_58fa3fcb46cd45b461095a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/bHGs2eyYIEEdm-Pcvn9_onodGi0>
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: Wed, 26 Sep 2018 23:48:11 -0000

This seems like an oversight, so I'm in favor of correcting in.  However, I'm not entirely convinced it's unreasonable to send STOP_SENDING preemptively for unidirectional streams either.

If you had advance knowledge of what was going to be on that stream (think HTTP/2-style PUSH_PROMISE), it might be reasonable to send STOP_SENDING for a stream that hasn't actually had data sent yet.  You can presume the data is in flight based on other application state, for example.

This might also be used to "claw back" unidirectional stream ID space -- you sent MAX_STREAM_ID=4X, then decide to shrink it by sending a STOP_SENDING on X-N streams, though that might not be a pattern we want to encourage.

-- 
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-424906757

v2.23.0 | Report a Bug | By Email