[quicwg/base-drafts] Allow CRYPTO_BUFFER_EXCEEEDED error when CRYPTO frame goes beyond 2^62 bytes (#3258)

Kazuho Oku <notifications@github.com> Mon, 18 November 2019 07:58 UTC

Date: Sun, 17 Nov 2019 23:58:57 -0800
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZWQ3VL5WED6O35BF5336A4DEVBNHHB6PVAQQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3258@github.com>
Subject: [quicwg/base-drafts] Allow CRYPTO_BUFFER_EXCEEEDED error when CRYPTO frame goes beyond 2^62 bytes (#3258)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dd24f41645b7_6de03fd4410cd9603203d3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/7iQsOtqLFKFW8Pd4rQGXin1oRxM>


When discussing #3027 at Cupertino, we agreed that either of the following two errors can be sent when the payload of the STREAM frame exceeds 2^62 bytes:
* FRAME_ENCODING_ERROR
* FLOW_CONTROL_ERROR

And we've merged PR #3042 that made that change, along with other changes. However, in that PR, we failed to apply the rule that we agreed for SRTEAM frame to CRYPTO frame.

Editors' draft now allows use of FRAME_ENCODING_ERROR for CRYPTO frames, but not CRYPTO_BUFFER_EXCEEDED.

As CRYPTO_BUFFER_EXCEEDED *is* the flow control error for CRYPTO streams, that should be permitted too.

To be fixed by PR #3186.

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

[quicwg/base-drafts] Allow CRYPTO_BUFFER_EXCEEEDE… Kazuho Oku
Re: [quicwg/base-drafts] Allow CRYPTO_BUFFER_EXCE… Martin Thomson
Re: [quicwg/base-drafts] Allow CRYPTO_BUFFER_EXCE… Martin Thomson
Re: [quicwg/base-drafts] Allow CRYPTO_BUFFER_EXCE… Martin Thomson