SpencerDawkins / sdp-rtp-quic-issues

Issued gathered from a variety of uncoordinated places, for sanity's sake.
Other
0 stars 0 forks source link

RTP over reliable streams or datagrams? #8

Open aboba opened 2 years ago

aboba commented 2 years ago

So far, implementers have largely chosen to utilize QUIC reliable streams for media transport, rather than QUIC datagrams. This appears to be largely due to:

  1. A focus on use cases other than realtime conferencing (e.g. video ingestion or low latency streaming)
  2. A desire for simplicity.

Realtime conferencing requires protocol standardization if it is desired to interoperate between a QUIC client and QUIC SFU from different vendors. SFUs implement RTP today, so using RTP over QUIC makes the most sense for the conferencing scenario.

However, low latency streaming scenarios typically involve a client downloading code from the cloud so interop is based on APIs rather than protocols. So protocol interop isn't as important. Also, in these scenarios, RTP limitations can be problematic (such as inability to transport significant amounts of synchronized data along with the frame (e.g. for AR/VR).

I think this may be an argument for focusing on RTP over QUIC datagrams and not RTP over QUIC reliable streams.

SpencerDawkins commented 2 years ago

This is related to #3, but I'm leaving it open, to keep track of the discussion there.