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.

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

A minimum-length varint encoding is not mandatory #4704

Merged
merged 1 commit into from Jan 11, 2021
Merged
Changes from all commits
Commits
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
4 changes: 3 additions & 1 deletion draft-ietf-quic-transport.md
Expand Up @@ -4418,12 +4418,14 @@ encoding properties.

Examples and a sample decoding algorithm are shown in {{sample-varint}}.

Values do not need to be encoded on the minimum number of bytes necessary, with
the sole exception of the Frame Type field; see {{frames}}.

Versions ({{versions}}), packet numbers sent in the header
({{packet-encoding}}), and the length of connection IDs in long header packets
({{long-header}}) are described using integers, but do not use this encoding.



# Packet Formats {#packet-formats}

All numeric values are encoded in network byte order (that is, big-endian) and
Expand Down