Re: [quicwg/base-drafts] Clarify RESET_STREAM interaction with flow-control limits (#3782)

Martin Thomson <notifications@github.com> Fri, 26 June 2020 07:08 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 DA2703A1190 for <quic-issues@ietfa.amsl.com>; Fri, 26 Jun 2020 00:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level:
X-Spam-Status: No, score=-2.008 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 GD5sANed0r-S for <quic-issues@ietfa.amsl.com>; Fri, 26 Jun 2020 00:08:15 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32A013A0A74 for <quic-issues@ietf.org>; Fri, 26 Jun 2020 00:08:15 -0700 (PDT)
Received: from github-lowworker-1b8c660.ash1-iad.github.net (github-lowworker-1b8c660.ash1-iad.github.net [10.56.18.59]) by smtp.github.com (Postfix) with ESMTP id 7631D5208B2 for <quic-issues@ietf.org>; Fri, 26 Jun 2020 00:08:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1593155294; bh=ka92599X0YZQALuyjh6Nm3Fxq+xgk5u/JZwk0cbb2yU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DCuhEHGhKEQBq9KmLoG6QJy/4d7CB1dr9gqUa8zIexJxWeBoVYXMpO/msO1RrBVpF Kok58YIH97YxORZOvrDgny2nc18//iB1GIPYircDgmYtIdcXdAFlYfzCPbTDPuOLpF tIpINS5OdE2jvuQU+0dyZBVdr+jC0PXzHkXRvCzk=
Date: Fri, 26 Jun 2020 00:08:14 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYEVWI7M7GD2XYT6GF5AF755EVBNHHCMXFHNA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3782/650015973@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3782@github.com>
References: <quicwg/base-drafts/issues/3782@github.com>
Subject: Re: [quicwg/base-drafts] Clarify RESET_STREAM interaction with flow-control limits (#3782)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ef59ede66aa2_6abe3fbec64cd9601819ae"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/t3gSw0MXjlgcJQ-d0Jp0Pjk6OcM>
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: Fri, 26 Jun 2020 07:08:17 -0000

I think that the [current text](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#section-4.1-7) is clear enough:

> A receiver MUST close the connection with a FLOW_CONTROL_ERROR error (Section 11) if the sender violates the advertised connection or stream data limits.

-- 
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/3782#issuecomment-650015973