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

MikkelFJ <notifications@github.com> Thu, 15 November 2018 15:07 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 90144130DC5 for <quic-issues@ietfa.amsl.com>; Thu, 15 Nov 2018 07:07:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 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_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 BXT6gCcKTCNT for <quic-issues@ietfa.amsl.com>; Thu, 15 Nov 2018 07:07:03 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45C8212D4EF for <quic-issues@ietf.org>; Thu, 15 Nov 2018 07:07:03 -0800 (PST)
Date: Thu, 15 Nov 2018 07:07:02 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542294422; bh=tBt142X8t5CglJETewBfdWNygsogZsDgC+V/10Uwyno=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kw3PoceL95eVTVv1x1HpT+zgDdlh/98RpY7dZ7UuRJ1oosoPWnoM0buZX4rtgk5Ug FpHSbEzGa7Bh8NPgobFzXfqi5icVoBf9FxtsejhnaHcdWTHMaPCDgkmzmJ2+J5wysz /0U2aCd0HulI4/i2QJc1U1vDfzWHGDZi7BMdloic=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab08872e8209799dcd6236d0d81b8d29e6b86053f592cf0000000118054d9692a169ce15ad130f@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/439071934@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_5bed8b9642ab9_19203fb2d20d45c077782e"; 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/GXOz9moEu3Ecb-XnrtElhnlOLbY>
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 15:07:05 -0000

@RyanAtGoogle that is true, but a lot of people wanted it back, so it reentered. My primary concern was the ability to have inifinite number of streams open - either very old are very future - but there is now a limited set of ID's you need to track. For this to work, it is very important that messages on old or uncreated streams are hard errors. This is the motiviation for the STOP_SENDING in Ready being a hard error. But there are some edge cases as you discovered.

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