|
| 1 | +# rvoip Roadmap |
| 2 | + |
| 3 | +**Updated:** 2026-08-11 |
| 4 | +**Purpose:** portfolio-level rollup of active and future work across the rvoip |
| 5 | +workspace. Detailed component plans remain authoritative for acceptance criteria |
| 6 | +and implementation history. |
| 7 | + |
| 8 | +## Status model |
| 9 | + |
| 10 | +- **Active** — accepted work with an existing detailed tracker. |
| 11 | +- **Future** — desired direction; not scheduled and not a support claim. |
| 12 | +- **Research** — requires standards, interoperability, dependency, or product |
| 13 | + validation before implementation is committed. |
| 14 | + |
| 15 | +## Active engineering tracks |
| 16 | + |
| 17 | +| Track | Status | Detailed tracker | |
| 18 | +|---|---|---| |
| 19 | +| Open-internet media hardening | Active | [`docs/PRODUCTION_HARDENING_ROADMAP.md`](docs/PRODUCTION_HARDENING_ROADMAP.md) — DTLS fragmentation, crypto review, CI/hygiene follow-through | |
| 20 | +| Cross-product architecture gaps | Active | [`docs/GAP_PLAN.md`](docs/GAP_PLAN.md) — deferred v1.x/v2 work and protocol adapters | |
| 21 | +| UCTP completion | Active | [`crates/uctp/rvoip-uctp/UCTP_GAP_PLAN.md`](crates/uctp/rvoip-uctp/UCTP_GAP_PLAN.md) — browser bidi-stream interoperability and per-session SIP codec override | |
| 22 | +| SIP standards promotion | Active | [`docs/sip/SIP_RFC_COMPLIANCE.md`](docs/sip/SIP_RFC_COMPLIANCE.md#roadmap-rollup) — partial/type-only behaviors to promote with executable evidence | |
| 23 | +| SIP transport reliability | Active | [`crates/sip/sip-transport/TODO.md`](crates/sip/sip-transport/TODO.md) — failover, recovery, backpressure, load/stress, and interoperability | |
| 24 | + |
| 25 | +## Future protocols and products |
| 26 | + |
| 27 | +| Initiative | Status | Intended integration | |
| 28 | +|---|---|---| |
| 29 | +| SIP-over-QUIC | Future | Add a QUIC transport to `rvoip-sip-transport`; keep the SIP transaction/dialog layers transport-neutral. | |
| 30 | +| RTP-over-QUIC (RoQ) | Future | Add a codec-agnostic `rvoip-roq` adapter for RTP/RTCP over QUIC DATAGRAMs and, where useful, QUIC streams. Preserve UCTP's distinct datagram framing and bridge at the media-adapter boundary. | |
| 31 | +| **Lyra V2 over UCTP, RTP, SIP, and RoQ** | Research | Add an optional Lyra V2 codec backend, an experimental RTP payload mapping, UCTP capability negotiation, SIP SDP integration, and a Lyra-over-RoQ end-to-end proof. See the workstream below. | |
| 32 | +| Media over QUIC (MoQ) | Future | Extend the existing MoQ crates toward broadcast-scale fan-out and UCTP/WebRTC bridging. | |
| 33 | +| Multi-party SFU/MCU products | Future | Build integrated products on the shipped media and subscription-routing primitives. | |
| 34 | +| AAuth production graduation | Future | Graduate the experimental standards work after security and deployment evidence mature. | |
| 35 | +| Deeper AI participants | Future | Add multi-agent orchestration beyond the current pluggable provider harness. | |
| 36 | +| QUIC multipath/NAT traversal | Research | Re-evaluate `noq` or equivalent when direct peer-to-peer and mobile multipath requirements justify a `quinn`-compatible change. | |
| 37 | + |
| 38 | +## Lyra V2 + RTP-over-QUIC workstream |
| 39 | + |
| 40 | +### Goal |
| 41 | + |
| 42 | +Demonstrate a bidirectional voice session that encodes 20 ms PCM frames with |
| 43 | +Lyra V2, packetizes them as RTP, and carries the same RTP stream over either |
| 44 | +ordinary UDP or RoQ. The proof must work through both a UCTP Session and a SIP |
| 45 | +call controlled by `rvoip-sip`. |
| 46 | + |
| 47 | +This is initially an **experimental, controlled-endpoint profile**. Lyra does |
| 48 | +not currently have an IETF-standard RTP payload format or a broadly deployed |
| 49 | +IANA/SDP registration, and RoQ is not yet a broadly deployed production |
| 50 | +transport. The roadmap must not imply third-party interoperability until a |
| 51 | +stable specification and independent test evidence exist. |
| 52 | + |
| 53 | +### Component ownership |
| 54 | + |
| 55 | +1. **`rvoip-codec-core` — Lyra V2 codec backend** |
| 56 | + - Add an opt-in feature and isolate the Google Lyra/TFLite native dependency |
| 57 | + from default builds. |
| 58 | + - Support mono 20 ms frames, 3.2/6/9.2 kbps, and the Lyra V2-supported |
| 59 | + external sample rates. |
| 60 | + - Expose encode/decode, bitrate selection, packet-loss concealment behavior, |
| 61 | + and capability metadata through the existing codec abstractions. |
| 62 | + |
| 63 | +2. **`rvoip-rtp-core` — experimental Lyra RTP profile** |
| 64 | + - Add packetizer/depacketizer support using a dynamic payload type. |
| 65 | + - Define the controlled-profile SDP shape, initially following the proven |
| 66 | + experimental convention `lyra/<clock-rate>/1` with a `bitrate` `fmtp` |
| 67 | + parameter. |
| 68 | + - Specify timestamp increments, frame aggregation rules, marker behavior, |
| 69 | + loss handling, and maximum packet size. Keep the profile explicitly |
| 70 | + namespaced/experimental until standardized. |
| 71 | + |
| 72 | +3. **`rvoip-uctp` — Lyra capability and bridge support** |
| 73 | + - Advertise Lyra V2 clock rates, bitrates, frame duration, and experimental |
| 74 | + RTP profile in `CapabilityDescriptor` negotiation. |
| 75 | + - Carry Lyra RTP packets through the existing UCTP media datagram framing; |
| 76 | + do not create a second codec-specific UCTP wire format. |
| 77 | + - Add codec selection, mismatch refusal, and optional transcoding fallback |
| 78 | + for UCTP-to-SIP bridges. |
| 79 | + |
| 80 | +4. **`rvoip-roq` — RTP/RTCP over QUIC** |
| 81 | + - Implement RoQ flow-ID mapping over QUIC DATAGRAMs first; evaluate stream |
| 82 | + modes separately so reliable delivery cannot accidentally add |
| 83 | + head-of-line latency to conversational audio. |
| 84 | + - Remain codec-agnostic, with Lyra V2 as the first low-bitrate audio proof |
| 85 | + and Opus/G.711 as interoperability controls. |
| 86 | + - Define RTCP/congestion-control ownership and whether QUIC transport |
| 87 | + feedback can safely replace any RTCP feedback in each deployment mode. |
| 88 | + |
| 89 | +5. **`rvoip-sip` — negotiation and end-to-end product integration** |
| 90 | + - Offer/answer the experimental Lyra RTP profile in SDP only when enabled. |
| 91 | + - Complete the existing per-session codec-override gap so re-INVITEs and |
| 92 | + UCTP/SIP bridges can select Lyra without changing global codec policy. |
| 93 | + - Support SIP signaling with a media leg using Lyra RTP over UDP and a |
| 94 | + bridged media leg using the same RTP packets over RoQ. |
| 95 | + - Treat RoQ as a media transport selected by the media adapter, not as a new |
| 96 | + SIP message encoding. SIP-over-QUIC remains a separate roadmap item. |
| 97 | + |
| 98 | +### Proof and qualification gates |
| 99 | + |
| 100 | +- Codec golden vectors and encode/decode round trips for every supported |
| 101 | + bitrate and enabled clock rate. |
| 102 | +- RTP sequence/timestamp, loss, reordering, aggregation, and SDP negotiation |
| 103 | + tests. |
| 104 | +- UCTP Lyra-to-Lyra loopback and UCTP-to-SIP bridge tests. |
| 105 | +- `rvoip-sip` calls using Lyra/RTP over UDP, then the same RTP flow tunneled over |
| 106 | + QUIC DATAGRAMs through `rvoip-roq`. |
| 107 | +- Comparison runs against Opus and G.711 under clean, lossy, reordered, and |
| 108 | + mobile-path-migration conditions. |
| 109 | +- Measure mouth-to-ear latency, CPU, memory, packet-loss behavior, and actual |
| 110 | + wire bitrate at 20, 40, and 100 ms packetization intervals. Report codec, |
| 111 | + RTP/RTCP, QUIC, and IP/UDP overhead separately. |
| 112 | +- Security review of QUIC-only transport encryption versus retaining SRTP for |
| 113 | + end-to-end protection across a terminating RoQ gateway. |
| 114 | +- Independent endpoint interoperability before removing the experimental |
| 115 | + label or making a compatibility claim. |
| 116 | + |
| 117 | +## Maintenance |
| 118 | + |
| 119 | +- Keep this file as the root portfolio rollup; do not copy detailed phase |
| 120 | + histories into it. |
| 121 | +- Add new work here when it crosses crate/product boundaries. Keep crate-local |
| 122 | + TODOs and acceptance details in the linked component tracker. |
| 123 | +- A published crate, feature flag, or experimental demo is not by itself a |
| 124 | + production-readiness or interoperability claim. |
0 commit comments