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

Packets can't be zero-length #4391

Merged
merged 2 commits into from
Nov 18, 2020
Merged

Packets can't be zero-length #4391

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6e3a65e
Packets can't be zero-length
martinthomson Nov 18, 2020
5ed5d48
OK, forgot the error code
martinthomson Nov 18, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3447,8 +3447,10 @@ Packet Payload {
{: #packet-frames title="QUIC Payload"}

The payload of a packet that contains frames MUST contain at least one frame,
and MAY contain multiple frames and multiple frame types. Frames always fit
within a single QUIC packet and cannot span multiple packets.
and MAY contain multiple frames and multiple frame types. An endpoint MUST
treat receipt of a packet containing no frames as a connection error of type
PROTOCOL_VIOLATION. Frames always fit within a single QUIC packet and cannot
span multiple packets.

Each frame begins with a Frame Type, indicating its type, followed by
additional type-dependent fields:
Expand Down