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

Jeremy Lainé <notifications@github.com> Tue, 23 June 2020 07:37 UTC

Date: Tue, 23 Jun 2020 00:37:47 -0700
From: Jeremy Lainé <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK274PWPK2BKCQ7AKMN47WJEXEVBNHHCMXFHNA@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@github.com>
Subject: [quicwg/base-drafts] Clarify RESET_STREAM interaction with flow-control limits (#3782)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ef1b14b3bb7e_15463f9913acd9602771c1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/m0MReK8s0z6Fu84KNGo1tXkdgqU>

When a `RESET_STREAM` is received, it carries a `final size` field. The specs do not describe the behaviour if the final size exceeds per-stream or connection-wide flow-control limits: should a `FLOW_CONTROL_ERROR` be triggered or a `FINAL_SIZE_ERROR`?

My preference would be `FLOW_CONTROL_ERROR` as this means the peer has transmitted too much data (presumably lost in flight prior to the reset).

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

[quicwg/base-drafts] Clarify RESET_STREAM interac… Jeremy Lainé
Re: [quicwg/base-drafts] Clarify RESET_STREAM int… Martin Thomson
Re: [quicwg/base-drafts] Clarify RESET_STREAM int… Lars Eggert
Re: [quicwg/base-drafts] Clarify RESET_STREAM int… Lars Eggert
Re: [quicwg/base-drafts] Clarify RESET_STREAM int… Lars Eggert