From 87622a4407dbdb40e3d90c28fadd645d9e932701 Mon Sep 17 00:00:00 2001 From: Jana Iyengar Date: Wed, 11 Dec 2019 18:45:28 -0800 Subject: [PATCH] editorial suggestion --- draft-ietf-quic-transport.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 46176883dc..9cc09d6109 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -2962,10 +2962,14 @@ H: : 1-RTT ({{short-header}}) +*: + +: A CONNECTION_CLOSE frame of type 0x1c can appear in Initial, Handshake, and +1-RTT packets, whereas a CONNECTION_CLOSE of type 0x1d can only appear in a +1-RTT packet. + Section 4 of {{QUIC-TLS}} provides more detail about these restrictions. Note -that all frames can appear in 1-RTT packets. Note that a CONNECTION_CLOSE frame -of type 0x1c can appear in Initial, Handshake, and 1-RTT packets, whereas a -CONNECTION_CLOSE of type 0x1d can only appear in a 1-RTT packet. +that all frames can appear in 1-RTT packets. An endpoint MUST treat the receipt of a frame of unknown type as a connection error of type FRAME_ENCODING_ERROR.