Adding Media over QUIC (MoQ) protocol

[InfoLibre]

Hello,

Could you add Media over QUIC protocol?
See https://moq.dev/, https://mediamtx.org/docs/kickoff/introduction and https://docs.antmedia.io/guides/publish-live-stream/moq/.

srs/memory/srs-overview.md

Line 133 in e03c841

- **MoQ** — UDP/QUIC. Media over QUIC. An IETF effort for low-latency media ingest and delivery over QUIC, usually over UDP and optionally through WebTransport.

[winlinvip]

Thanks for the suggestion. We would like to support Media over QUIC (MoQ) in SRS in the future, but we are not planning to add major new protocols to the current C++ server right now.

Our current priority is to finish the next-generation Go proxy server and establish a workflow where AI can reliably maintain the project. The next step will be to let AI migrate or build the next-generation origin server and bring it to feature parity with the current origin server.

After that migration is complete, we can work on the next-generation edge server and new protocols such as MoQ. Therefore, MoQ is part of our future direction, but it is deferred until the AI-maintained server foundation is ready.

[winlinvip]

Truth Record — 2026-07-17

This self-contained record supersedes and incorporates the earlier maintainer direction.

Verified project state

• Branch: develop
• Commit: e03c841dc442c6d5059cddc0e2f2e6cc4a89d087
• Version: SRS 8.0.3
• Verification environment: macOS 26.5.2, arm64; source and documentation review only
• Project changes and tests: none, because this is a deferred feature request rather than a current implementation or bug fix

Current state

SRS does not currently support Media over QUIC. The project overview explicitly lists MoQ and WebTransport as unsupported transports. This issue is a valid feature request, not a bug.

We would like to support MoQ in SRS in the future, but we are not planning to add major new protocols to the current C++ server. The current priority is:

1. Finish the next-generation Go proxy server.
2. Establish a workflow in which AI can reliably maintain SRS.
3. Migrate or build the next-generation Go origin server and bring it to feature parity with the current origin server.
4. Build the next-generation edge server and add new protocols such as MoQ.

Therefore, MoQ is part of SRS's future direction, but implementation is deferred until the AI-maintained server foundation is ready.

MoQ itself is still evolving. As of this verification, the current IETF specification is draft-ietf-moq-transport-19, an Internet-Draft covering MOQT over QUIC and WebTransport. A future implementation will need to select its interoperability target and define supported server roles, media formats, codecs, authentication, and integration with SRS sources.

Conclusion and next action

No project change is required now. Retain this issue as a deferred future feature and revisit it after the next-generation origin and edge foundations are ready.

Remaining unknowns

Implementation schedule, MOQT versus moq-lite compatibility, origin/edge/relay responsibilities, supported media formats and codecs, and browser interoperability.