From 79217ef30b51c8ff1892dc46de45c22cfc53dd26 Mon Sep 17 00:00:00 2001 From: Jana Iyengar Date: Tue, 9 Apr 2019 16:08:11 -0700 Subject: [PATCH] Frames of unknown type cause connection close --- draft-ietf-quic-transport.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index f8f147e284..59de19365e 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -2701,10 +2701,10 @@ frames. --> {: #packet-frames title="QUIC Payload"} QUIC payloads MUST contain at least one frame, and MAY contain multiple frames -and multiple frame types. +and multiple frame types. Frames MUST fit within a single QUIC packet and MUST +NOT span a QUIC packet boundary. -Frames MUST fit within a single QUIC packet and MUST NOT span a QUIC packet -boundary. Each frame begins with a Frame Type, indicating its type, followed by +Each frame begins with a Frame Type, indicating its type, followed by additional type-dependent fields: ~~~ @@ -2747,6 +2747,9 @@ frames are explained in more detail in {{frame-formats}}. | 0x1c - 0x1d | CONNECTION_CLOSE | {{frame-connection-close}} | {: #frame-types title="Frame Types"} +An endpoint MUST treat the receipt of a frame of unknown type as a connection +error of type FRAME_ENCODING_ERROR. + All QUIC frames are idempotent in this version of QUIC. That is, a valid frame does not cause undesirable side effects or errors when received more than once.