Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

editorial suggestion #3299

Merged
merged 1 commit into from Dec 12, 2019
Merged

editorial suggestion #3299

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 7 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -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.
Expand Down