From 74dff6511f32ec8a7cde61034cf36abd7846fd64 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Mon, 17 Aug 2020 14:13:57 +1000 Subject: [PATCH] Use FRAME_ENCODING_ERROR for stream limits >2^60 This is an error that can be detected in frame parsing without additional context. Closes #3781. --- draft-ietf-quic-transport.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 2293de62dd..ebe3dce83a 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -970,7 +970,7 @@ If a max_streams transport parameter or MAX_STREAMS frame is received with a value greater than 2^60, this would allow a maximum stream ID that cannot be expressed as a variable-length integer; see {{integer-encoding}}. If either is received, the connection MUST be closed immediately with a -connection error of type STREAM_LIMIT_ERROR; see {{immediate-close}}. +connection error of type FRAME_ENCODING_ERROR; see {{immediate-close}}. Endpoints MUST NOT exceed the limit set by their peer. An endpoint that receives a frame with a stream ID exceeding the limit it has sent MUST treat