You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Discussion: native MMTP container for Hang on the draft-18 line #5912
MMTP (ISO/IEC 23008-1) is the packet format emitted by ATSC 3.0 broadcast and IP multicast media sources. A MoQ publisher can carry one MMTP packet per object, preserving packet identity and authored timing for FEC repair and multicast/unicast switching. A Hang receiver needs a native container adapter to turn those objects into timed media frames.
This proposal targets the current draft-18 line and tests moqt-18. It does not add MoQ control messages, modify @moq/net, or submit draft-20 code.
Proposed boundary
Hang owns its own native mmtp container and decoder binding.
libmmt owns MMTP parsing and MFU reassembly, including malformed-packet classification and bounded, clock-free behavior.
The implementation is staged in Blockcast/moq#8, merged in the fork at 717b84c40559018e023365d758031fc45711357f, from unmodified upstream moq-dev/moq@290485ed12683b53b6e7b474dc4deca9495eec6c. It uses @blockcast/mmt-base@0.3.0 and @blockcast/mmt-container@0.3.0. The fork checks and draft-18 session test are green, with positive vectors, malformed controls and mutation checks.
The upstream submission will be re-authored by a human for the project's DCO before filing. No draft-20 relay behavior is part of this proposal.
Would maintainers accept this native container shape, and which current upstream base/branch should the human-submitted draft-18 PR target?
Thanks for the detailed proposal. We're declining a native MMTP container in Hang, consistent with #5372, #5373 and #4926.
Hang's core containers stay container-neutral (Legacy, CMAF, LOC), and @moq/hang won't take third-party format dependencies. MMTP can still ride MoQ without upstream changes:
publish the tracks with an unregistered container string, which Hang's catalog preserves verbatim (Container::Unknown in Rust, the same in JS);
Activity
kixelated commentedon Oct 19, 2026
Thanks for the detailed proposal. We're declining a native MMTP container in Hang, consistent with #5372, #5373 and #4926.
Hang's core containers stay container-neutral (Legacy, CMAF, LOC), and
@moq/hangwon't take third-party format dependencies. MMTP can still ride MoQ without upstream changes:Container::Unknownin Rust, the same in JS);One note on the base:
mainis the trunk and negotiates drafts 15 through 22; there is no draft-18 branch to target.Tracked in the import planning PR #5969.
(Written by Claude Opus 5.5)