Home/Events/MoQ Meetup Japan #1
MeetupOct 2, 2026·docomo R&D OPEN LAB ODAIBA, Tokyo, Japan

MoQ Meetup Japan #1

The first MOQ-dedicated meetup in Japan, organised by Tetta Maeda as a sister community of Tokyo Video Tech. Four talks spanning the protocol, a production migration, research and games — the strongest sign yet that MOQ interest is global.

Official event page →

MOQ sessions & talks

The Art of The Switch: Seamless Rate Adaptation in MOQtail

Ali C. Begen

MoQ in a Real-Event Platform for Virtual Talent: HYPER STUDIO

Ryo Kikuchi (Bootstrap Inc.)

Moved from LiveKit to Cloudflare’s MOQ relay in production

MoQ Optimization in Point-cloud Streaming

Kota Yatagai (Keio University SFC)

QUIC and MoQ Seen from Game Real-Time Communication

Ryo Takehara (SEGA)

Covers QUIC usage in Sonic Rumble

Coverage from the pipeline

newsOct 8, 2026via GitHub

New MOQ repo to watch: moq-llm-wiki

MOQ wiki backed by Claude Code Latest tracked commit 29d13a9: Update wiki for Oct 7-8: afrind+Swett subscription flow-control draft; moq-rs CAT-auth + fetch backfill; moqtail/imquic wake-ups; runner +8 second-recovery n…

newsJul 15, 2026via GitHub

moqtail ships relay@0.14.1

Patch Changes #219 78bfab7 Thanks @zafergurel! - Fixes missing header bug. Thanks to kkroo

newsJul 1, 2026via GitHub

moqtail ships moqtail-rs@0.14.0

Minor Changes 0ca44e5 Thanks @zafergurel! - Add raw QUIC transport support alongside WebTransport. TransportConnection/TransportSendStream/TransportRecvStream in moqtail-rs now wrap both wtransport and raw quinn behind…

newsJul 1, 2026via GitHub

moqtail ships relay@0.14.0

Minor Changes 0ca44e5 Thanks @zafergurel! - Add raw QUIC transport support alongside WebTransport. TransportConnection/TransportSendStream/TransportRecvStream in moqtail-rs now wrap both wtransport and raw quinn behind…

newsJul 1, 2026via GitHub

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…

newsMay 29, 2026via IETF Mailing List

IETF MOQ WG: Consensus Call: DTS and SWITCH

Ali C. Begen posted to the MOQ working group mailing list on May 29, 2026. I could not attend the interim call due to a personal emergency, however, I watched the recording. My vote for both Switch and DTS is as follows:

newsMay 20, 2026via IETF Mailing List

IETF MOQ WG: User case or question to Joining Fetch

Zafer Gurel posted to the MOQ working group mailing list on May 20, 2026. Hi Will, You are right. However, the collision problem I mentioned is more about the cache implementation of MOQtail relay. The cache key

newsMay 15, 2026via IETF Mailing List

IETF MOQ WG: User case or question to Joining Fetch

Mo Zanaty (mzanaty) posted to the MOQ working group mailing list on May 15, 2026. Hi Yu, beware of pitfalls in this anti-pattern. A track is malformed (see 2.4.2) if different objects end a subgroup or group. So you mus…

newsMay 15, 2026via IETF Mailing List

IETF MOQ WG: User case or question to Joining Fetch

Yu You (Nokia) posted to the MOQ working group mailing list on May 15, 2026. Thanks for the helpful suggestions. I will re-implement the chat using a wall-clock-based Group ID together with a unique Object ID to avoid c…

newsMay 13, 2026via IETF Mailing List

IETF MOQ WG: User case or question to Joining Fetch

Law, Will posted to the MOQ working group mailing list on May 13, 2026. @Zafer - "Using milliseconds didn't help, sometimes the group IDs collided (when a join message is received by the participants in the room, they s…

newsMay 13, 2026via IETF Mailing List

IETF MOQ WG: User case or question to Joining Fetch

Mo Zanaty (mzanaty) posted to the MOQ working group mailing list on May 13, 2026. Hi Yu, we built something similar using the anti-pattern Zafer described. It's an anti-pattern because MOQT says such tracks SHOULD NOT u…

newsMay 13, 2026via IETF Mailing List

IETF MOQ WG: User case or question to Joining Fetch

Zafer Gurel posted to the MOQ working group mailing list on May 13, 2026. Hi Yu You, That's an interesting problem which I also encountered while developing the Meet

The next event, in your inbox

One email every Monday: IETF spec changes, event outcomes, and what shipped — each item summarized, with a link.