From fd1261db69b7fcc825da4c0d4cc96be47dba2749 Mon Sep 17 00:00:00 2001 From: ianswett Date: Thu, 24 Sep 2020 18:51:39 -0400 Subject: [PATCH] QUIC transport does not have stream level errors Fixes #4123 --- draft-ietf-quic-transport.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 7983a2ed0c..5416a9eab6 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -3184,8 +3184,7 @@ the connection. Errors that result in the connection being unusable, such as an obvious violation of protocol semantics or corruption of state that affects an entire connection, MUST be signaled using a CONNECTION_CLOSE frame -({{frame-connection-close}}). An endpoint MAY close the connection in this -manner even if the error only affects a single stream. +({{frame-connection-close}}). Application-specific protocol errors are signaled using the CONNECTION_CLOSE frame with a frame type of 0x1d. Errors that are specific to the transport,