Expand description
MoQT client implementation for draft-09.
Each draft lives in its own top-level module with a complete, independent implementation: connection, endpoint state machine, event types, observer trait, and per-flow state machines (subscribe, fetch, announce, track status). No code is shared across drafts — each draft carries its own copy because wire-level differences would make a shared layer leaky.
Enable via the draft09 feature.
§Differences from draft-08
- Object headers on data streams now carry
extension_headers_length(byte count) instead ofextension_count(item count). Datagram(stream type 0x01) no longer haspayload_lengthorobject_status; payload is the remaining bytes of the datagram.DatagramStatus(stream type 0x02) gainsextension_headers_length.filter_type = 1(NextGroupStart / LatestGroup) is rejected on decode in SUBSCRIBE.
Modules§
- connection
- Outbound MoQT connection with MoQT framing over QUIC.
- endpoint
- Unified endpoint state machine orchestrating all MoQT protocol flows.
- event
- Client event types emitted via the observer. Client event types emitted by a draft-09 MoQT connection.
- fetch
- Fetch lifecycle state machine.
- namespace
- Announce / SubscribeAnnounces state machines.
- observer
- Connection observer trait for receiving client events. Connection observer trait for receiving structured events.
- session
- Session state, setup validation, and subscribe ID allocation. MoQT session lifecycle management (draft-09).
- subscription
- Subscription lifecycle state machine.
- track_
status - Track status lifecycle state machine.