1. Mind the missing object.
Consecutive IDs proposed · Sent ≠ received
Caches must distinguish missing, filtered and deliberately absent data. The working group has not adopted a new numbering rule.
Ian Swett proposed consecutive object numbers to simplify cache completeness. Other participants raised subgroup selection, datagram loss and filtering. Publisher numbering and the subset received are different questions; this remains a design discussion.
Source section: https://blog.rvnd.me/moqmusings/2026-10-19-moq-minded-the-gap#object-numbers
Primary sources: https://mailarchive.ietf.org/arch/msg/moq/--sp3nkyar9Iseeh7P8HQ15K4Fw/ https://mailarchive.ietf.org/arch/msg/moq/I0OJKCJU1K1iZV9OO_2G27ydHFs/

2. An early finish flag.
Open issue / 21 OCT · Filter changes mid-stream
An updated filter can exclude the final object. What should closing the stream tell the receiver?
Issue 2032 describes an end-of-group indication in a stream header becoming misleading when a later filter excludes the actual final object. Several alternatives are discussed; no released fix is claimed.
Source section: https://blog.rvnd.me/moqmusings/2026-10-19-moq-minded-the-gap#finish-flag
Primary sources: https://github.com/moq-wg/moq-transport/issues/2032

3. Bring a worked example.
Mandatory Track Properties · Request / 24 OCT
Editors want an example extension before San Francisco. Removal is a conditional proposal, not a decision.
Alan Frindell asked for a documented example of Mandatory Track Properties before the San Francisco meetings. Suhas Nandakumar described the need to know whether a path understands a feature. The request did not remove the mechanism.
Source section: https://blog.rvnd.me/moqmusings/2026-10-19-moq-minded-the-gap#mandatory-properties
Primary sources: https://mailarchive.ietf.org/arch/msg/moq/a1CQcpUcmq1iqIivqQq-dBvWXGs/ https://mailarchive.ietf.org/arch/msg/moq/ioi8OEwaCkU9sqS4FfIZIfD6n1Q/

4. One game. Several drivers.
MoQ Boy / existing demo · moq-lite
Controls and game status travel on JSON tracks. No gameplay benchmark or universal interoperability claim.
MoQ Boy is an existing open-source remote Game Boy emulation demo, documented to carry control and status on custom JSON tracks. It uses moq-lite. The source and documentation were inspected; gameplay and latency were not tested.
Source section: https://blog.rvnd.me/moqmusings/2026-10-19-moq-minded-the-gap#built-with-moq
Primary sources: https://moq.dev/boy/