Trembit favors WebRTC telehealth consultations over MoQ through 2026

The immediate implication is that telehealth providers must prioritize architectural maturity over emerging protocols to satisfy strict HIPAA and GDPR data-path audits. In the broader streaming ecosystem, this highlights a growing divergence between interactive two-way communication and scalable one-to-many distribution, where MoQ is better suited for grand rounds or surgical broadcasts rather than private consults. The rigid requirements of German KBV certification further illustrate that self-hosted infrastructure remains the only viable path for high-compliance verticals. Watch for the finalization of the MoQ Transport RFC and subsequent browser support updates as the primary signals for when to begin non-critical clinical pilots.

WebRTC's dominance in regulated telehealth is reinforced by its deep integration into major healthcare platforms and its status as the default real-time communication layer across clinical software vendors. In June 2026, Ericsson launched its AI in RAN commercial software subscription, claiming up to 20% higher downlink throughput across more than 15 live deployments, a development that underscores how network-layer improvements continue to benefit WebRTC's UDP-based transport without requiring protocol changes. The IETF's Media over QUIC working group has yet to finalize the MoQ Transport RFC, and no browser vendor has shipped native MoQ support for interactive two-way sessions, leaving WebRTC as the only protocol with guaranteed sub-250ms round-trip performance across Chrome, Firefox, and Safari.

On the business and regulatory side, Nokia's aggressive push into agentic AI for network operations illustrates how infrastructure vendors are betting on automation layers rather than protocol replacements to drive operator differentiation. Nokia announced an agentic AI framework built into its Network Services Platform on June 11, 2026, letting carriers deploy AI agents that make decisions from real-time network data, a move that positions network intelligence above the transport layer rather than displacing it. For telehealth providers, this means the compliance burden remains at the application protocol level, where WebRTC's established DTLS-SRTP encryption and SRTP media paths have already passed HIPAA and GDPR audits at scale. Nokia combined with AWS and Databricks at DTW Ignite to build a unified data and control layer for autonomous networks, demonstrating that even the largest infrastructure players are layering AI orchestration on top of existing transport rather than replacing it.

Technical benchmarks and competitive positioning further favor WebRTC for latency-sensitive clinical use cases. Light Reading reported that Ericsson and Nokia are diverging sharply on AI-RAN architecture, with Nokia running all Layer 1 functions on Nvidia GPUs while Ericsson keeps most L1 software on CPUs, a split that mirrors the broader industry tension between consolidating workloads onto new hardware and maintaining proven software stacks. For telehealth, the analogous decision is whether to migrate to MoQ's QUIC-based transport before browser support and healthcare-specific compliance tooling exist. , suggesting that even in the radio access domain, vendors are choosing incremental evolution over wholesale protocol replacement. Trembit's recommendation aligns with this pattern: WebRTC remains the production-ready choice for two-way clinical video until MoQ achieves equivalent regulatory and browser maturity.