[webrtc-nv-use-cases] Issue with current draft of WebRTC-NV Low Latency Streaming Use Cases (#103)

youennf has just created a new issue for https://github.com/w3c/webrtc-nv-use-cases:

== Issue with current draft of WebRTC-NV Low Latency Streaming Use Cases ==
The various use cases presented in this section are already deployed so I wonder whether they qualify as NV.
My understanding is that use cases should identify shortcomings (via new requirements) to the current WebRTC support.

It is difficult to assess whether these use cases identify shortcomings.
The term “low latency” in particular is vague even in the context of WebRTC.
Are we trying to go to ultra low latency where waiting for an RTP assembled video frame by the proxy is not good enough?

Looking at some of the requirements, I am unclear how we will be able to leverage them:
- N37 is already achieved or seems like an implementation problem that is internal to User Agents.
- N38 is partially achieved via playoutDelay and/or WebRTC encoded transform. The requirement should be precise to identify what is missing after playoutDelay.
- N39 is already achieved via data channel and/or WebRTC encoded transform without any change. The requirement should be precise to identify what is missing.

Please view or discuss this issue at https://github.com/w3c/webrtc-nv-use-cases/issues/103 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 1 February 2023 14:23:32 UTC