Back to News
news

moqtail ships moqtail@0.12.0

Minor Changes #206 9c236c9 Thanks @kerembkmz! - Normalize empty subgroup extension headers to null so [] serializes the same as no headers. Patch Changes #208 211ce94 Thanks @zafergurel! - Fix Key-Value-Pair Type fields…

Source: GitHubView source →

Repository Snapshot

  • Repo: moqtail/moqtail
  • Source: GitHub
  • Language: TypeScript
  • Last pushed: 2026-07-01
  • Milestone: Release moqtail@0.12.0
  • Published: 2026-07-01

Summary

Minor Changes #206 9c236c9 Thanks @kerembkmz! - Normalize empty subgroup extension headers to null so [] serializes the same as no headers. Patch Changes #208 211ce94 Thanks @zafergurel! - Fix Key-Value-Pair Type fields…

Why It Matters

moqtail/moqtail is an active MOQ implementation, so a tagged GitHub release is a concrete milestone for implementers tracking protocol and deployment progress.

Source Excerpt

Minor Changes #206 9c236c9 Thanks @kerembkmz! - Normalize empty subgroup extension headers to null so [] serializes the same as no headers. Patch Changes #208 211ce94 Thanks @zafergurel! - Fix Key-Value-Pair Type fields being encoded/decoded as raw absolute values instead of deltas from the previous Type in the same list, per draft-ietf-moq-transport-16 (#1315). This broke interop with spec-compliant v16 peers: parameters such as FORWARD or SUBSCRIPTION_FILTER could be received as the wrong type (e.g. logged as "Unsupported parameter 48/81") by any peer that correctly delta-decodes. Affects Setup/Message Parameters and Object/Track Extension Headers (including the nested ImmutableExtensions list) in both the Rust (moqtail-rs) and TypeScript (moqtail) libraries. Thanks to @lminiero for testing and reporting this bug.

Stay ahead of MOQ

Get the latest IETF MOQ standards updates, protocol analysis, and ecosystem news delivered to your inbox.

Go deeper with MOQ Edge Pro

Weekly deep-dives, IETF standards tracking, and streaming tech trend reports — from $9/mo.

See plans →