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

nonsensical MUST on frames fitting in packets #2603

Merged
merged 3 commits into from Apr 11, 2019
Merged

nonsensical MUST on frames fitting in packets #2603

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b604fa3
nonsensical MUST on frames fitting in packets
martinthomson Apr 10, 2019
4a2b700
Taking kazuho's suggestion, with tweaks
martinthomson Apr 11, 2019
01a87bc
Tweak
martinthomson Apr 11, 2019
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
15 changes: 6 additions & 9 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2678,12 +2678,9 @@ Packet number encoding at a sender and decoding at a receiver are described in

## Frames and Frame Types {#frames}

The payload of QUIC packets, after removing packet protection, commonly consists
of a sequence of frames, as shown in {{packet-frames}}. Version Negotiation,
Stateless Reset, and Retry packets do not contain frames.

<!-- TODO: Editorial work needed in this section. Not all packets contain
frames. -->
The payload of QUIC packets, after removing packet protection, consists of a
sequence of complete frames, as shown in {{packet-frames}}. Version
Negotiation, Stateless Reset, and Retry packets do not contain frames.

~~~
0 1 2 3
Expand All @@ -2700,9 +2697,9 @@ frames. -->
~~~
{: #packet-frames title="QUIC Payload"}

QUIC payloads MUST contain at least one frame, and MAY contain multiple frames
and multiple frame types. Frames MUST fit within a single QUIC packet and MUST
NOT span a QUIC packet boundary.
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.

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