Skip to content

moq-transport draft-07 initial wire format updates #32

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

Merged
merged 3 commits into from
Feb 24, 2025
Merged

Conversation

englishm
Copy link
Owner

@englishm englishm commented Jan 19, 2025

Work in progress.

Draft diffs:

The main change between draft-06 and draft-07 is the addition of Fetch.
Most of the other changes are clarifications or editorial.

@mcintyrehh has already started adding the basic wire format encoding/decoding for Fetch and related messages in #31 which I'll pull in here (so as to land in main together with the version bump)

@englishm englishm changed the title moq-transport draft-06 initial wire format updates moq-transport draft-07 initial wire format updates Jan 20, 2025
@englishm
Copy link
Owner Author

Notes (mostly for myself): Our current Track implementation provides a somewhat leaky abstraction over the various MoQT Subscribe modes that existed prior to SubGroups. We may want to rework this a bit. Also, draft-07 finally drops support for "Track per Stream" so a quick hack might be to repurpose that "mode" as a "Fetch" mode instead since the reader semantics should be about the same.

@englishm
Copy link
Owner Author

After talking with @zafergurel just now at the interop hackathon before the Denver interim, we decided it's probably worth merging the wire format parsing for Fetch here and then we can fill in the implementation I'm still working on later. We'd like to get to wire format compatibility on draft-08 for basic interop with other implementations.

@englishm englishm marked this pull request as ready for review February 24, 2025 22:54
@englishm englishm merged commit 34cd7d9 into main Feb 24, 2025
1 check passed
@github-actions github-actions bot mentioned this pull request Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants