Skip to content

Key-Value-Pairs Delta encoding editorial tweaks. #1366

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

Merged
merged 1 commit into from
Nov 8, 2025
Merged

Key-Value-Pairs Delta encoding editorial tweaks. #1366

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 11 additions & 10 deletions draft-ietf-moq-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -275,8 +275,14 @@ Location A < Location B if:
Key-Value-Pair is a flexible structure designed to carry key/value
pairs in which the key is a variable length integer and the value
is either a variable length integer or a byte field of arbitrary
length. Key-Value-Pairs encode a Type value as a delta from the
previous Type value, or from 0 if there is no previous Type value.
length.

Key-Value-Pairs encode a Type value as a delta from the previous Type value,
or from 0 if there is no previous Type value. This is efficient on the wire
and makes it easy to ensure there is only one instance of a type when needed.
The previous Type value plus the Delta Type MUST NOT be greater than 2^64 - 1.
If a Delta Type is received that would be too large, the Session MUST be closed
with a `PROTOCOL_VIOLATION`.

Key-Value-Pair is used in both the data plane and control plane, but
is optimized for use in the data plane.
Expand Down Expand Up @@ -1628,12 +1634,7 @@ Receivers ignore unrecognized parameters.
The number of parameters in a message is not specifically limited, but the
total length of a control message is limited to 2^16-1 bytes.

Parameters are serialized as Key-Value-Pairs {{moq-key-value-pair}} in
increasing Parameter ID order with a delta encoding. This is efficient on the
wire and makes it easy to ensure there is only one instance of parameters
that cannot be repeated. The previous Type value plus the Delta Type MUST NOT be
greater than 2^64 - 1. If a Delta Type is received that would be too large, the Session
MUST be closed with a `PROTOCOL_VIOLATION`.
Parameters are serialized as Key-Value-Pairs {{moq-key-value-pair}}.

Setup message parameters use a namespace that is constant across all MOQT
versions. All other messages use a version-specific namespace.
Expand Down Expand Up @@ -3167,8 +3168,8 @@ definition of the extension, Extension Headers MAY be modified, added, removed,
and/or cached by relays.

Object Extension Headers are serialized as Key-Value-Pairs (see
{{moq-key-value-pair}}) in increasing extension type order with a delta encoding,
prefixed by the length of the serialized Key-Value-Pairs, in bytes.
{{moq-key-value-pair}}), prefixed by the length of the serialized
Key-Value-Pairs, in bytes.

~~~
Extensions {
Expand Down