Re: [quicwg/base-drafts] Inconsistency in STOP_SENDING requirements relative to resetting streams in general (#2884)

MikkelFJ <> Wed, 10 July 2019 17:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EA4D71203D7 for <>; Wed, 10 Jul 2019 10:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GQkQc2vxWlZN for <>; Wed, 10 Jul 2019 10:28:59 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 47C9D1202EE for <>; Wed, 10 Jul 2019 10:28:32 -0700 (PDT)
Date: Wed, 10 Jul 2019 10:28:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1562779711; bh=FsGpY64ZjFlNtL3LOUEb7lNjH/+Szg756Uoq61fmHHc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lrL21aUKyKX5XUReZyn/kc7YwqnifuYr2r5lAMH0KA2kZ8wKNa6KGcp56YTPF5/4d NuOKR4CXFujWqJHg1NKWqmFiVTT0LT4MX8HVRYI+IigSE+w4INA1zDXuQm+ZI+GVHY Z/A9lra9uOtrqdGyDwga+wuCqtMKz9wjqUDX+PBA=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2884/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Inconsistency in STOP_SENDING requirements relative to resetting streams in general (#2884)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d26203f387cb_36743f9143ccd96839329e"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 10 Jul 2019 17:29:01 -0000

> I don't see how this is a concern. For such cases either the application can still issue a reset for the stream, or the transport implementation can optionally take control of it and issue the reset itself.

It may not be in the application protocols best interest to have a forced reset in this case.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: