1. The lamp stayed on.
Instagram Live ingest · Meta-reported parity
iOS / Android ingest; delivery all the way to viewers remains future work.
Meta reports MOQ for Instagram Live ingest on iOS and Android: the creator-to-Meta leg. Its rollout measures matched RUSH, the existing transport. Edge translation and RUSH TCP fallback remain; delivery all the way to viewers is future work. The report gives no public traffic count or measured latency improvement.
Source section: https://blog.rvnd.me/moqmusings/2026-10-12-moq-kept-the-lights-on#instagram-ingest
Primary sources: https://engineering.fb.com/2026/10/12/video-engineering/shipping-media-over-quic-at-meta-scale-for-instagram-live-ingest/

2. Check the actual version.
Seattle / 15 OCT · 18 of 76 version reports differed · Client vs test report
The records disagree about the version used. They do not count failed streams.
In Mike English’s October 15 Seattle interop report, clients supplied the MOQ version they used for 76 runs. In 18 of those runs, the test report had assumed a different version. These counts concern the version records, not failed media streams. The report asks for better run details and explicit test versions; successful protocol tests also do not prove correct playback.
Source section: https://blog.rvnd.me/moqmusings/2026-10-12-moq-kept-the-lights-on#seattle-interop
Primary sources: https://datatracker.ietf.org/meeting/interim-2026-moq-29/materials/slides-interim-2026-moq-29-sessa-moq-interop-report-2026-10-15-seattle-00

3. Permission has a clock.
Auth design team · Renew before expiry
Proposed relay-to-client checks: renew permission or stop delivery.
The October 15 auth design-team update proposes continuous authorization, client-managed renewal and stopping delivery when a token no longer authorizes the request. Token formats would define expiry and re-evaluation. Work so far focuses on relay-to-end-client authorization; it is design-team work, not newly adopted core MOQT behavior.
Source section: https://blog.rvnd.me/moqmusings/2026-10-12-moq-kept-the-lights-on#authorization-renewal
Primary sources: https://datatracker.ietf.org/meeting/interim-2026-moq-29/materials/slides-interim-2026-moq-29-sessa-auth-design-team-update-00

4. Put publishers under the lens.
Paul Gregoire’s runner · Publisher · Wire evidence · Report
Existing tool. Drafts 18/21/22; separate moq-lite-06. Trusted-network API; no media checks.
Paul Gregoire’s existing contribution interop runner acts as a receiving relay, requests data from a publisher and checks its protocol messages against draft-specific requirements. It has Linux/CMake and Docker setup instructions and JSON, TAP and HTML reports. Drafts 18, 21 and 22 are separate targets, with moq-lite-06 a separate target. It treats media payloads as opaque and its unauthenticated HTTP API belongs on a trusted network. The tool was inspected, not executed in this editorial run.
Source section: https://blog.rvnd.me/moqmusings/2026-10-12-moq-kept-the-lights-on#built-with-moq
Primary sources: https://github.com/mondain/moq-contribution-interop-runner
