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

Header Length for improving parsing #520

Merged
merged 8 commits into from
Sep 20, 2024
Merged

Header Length for improving parsing #520

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
b5ad15c
add header length for easy parsing
suhasHere Sep 9, 2024
ef1a534
Merge branch 'main' into trail-parsing
ianswett Sep 16, 2024
6616094
Merge branch 'main' into trail-parsing
ianswett Sep 18, 2024
208f2b7
make header length only for control messages
suhasHere Sep 18, 2024
45f558e
Update draft-ietf-moq-transport.md
ianswett Sep 18, 2024
c965aa4
Don't ignore control messages
ianswett Sep 18, 2024
c686c65
Merge branch 'main' into trail-parsing
ianswett Sep 19, 2024
b0c63e3
Add back essential newline
afrind Sep 20, 2024
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
7 changes: 5 additions & 2 deletions draft-ietf-moq-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -830,7 +830,7 @@ formatted as follows:
~~~
MOQT Control Message {
Message Type (i),
Message Payload (..),
Message Payload (b),
}
~~~
{: #moq-transport-message-format title="MOQT Message"}
Expand Down Expand Up @@ -882,6 +882,9 @@ MOQT Control Message {
|-------|-----------------------------------------------------|

An endpoint that receives an unknown message type MUST close the session.
Control messages have a length to make parsing easier, but no control
messages are intended to be ignored. If the length does not match the
length of the message content, the receiver MUST close the session.

## Parameters {#params}

Expand Down Expand Up @@ -1775,7 +1778,7 @@ An `OBJECT_DATAGRAM` message carries a single object in a datagram.

An Object received in an `OBJECT_DATAGRAM` message has an `Object
Forwarding Preference` = `Datagram`. To send an Object with `Object
Forwarding Preference` = `Datagram`, determine the length of the fields and
Forwarding Preference` = `Datagram`, determine the length of the header and
payload and send the Object as datagram. In certain scenarios where the object
size can be larger than maximum datagram size for the session, the Object
will be dropped.
Expand Down
Loading