Re: Call for Consensus (CfC): WebRTC-NV "Low Latency Streaming Use Cases (Section 3.2)

Both use cases are already deployed so I wonder whether they qualify as NV.
They probably qualify as NV if some of their corresponding requirements are not already met with existing web technologies.
When reading the requirements, it seems some/most of them are already met.

The term “low latency” in particular is vague even in the context of WebRTC.
Low latency broadcast with fanout is already achieved by some web sites but it is not clear where we are trying to improve upon existing deployed services.
For instance, 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 the requirements:
- 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. I am not clear whether this use case is asking for more than what is already provided.
- N39 is already achieved via data channel and/or WebRTC encoded transform without any change. I am guessing more is required. If so, can we be more specific?

Thanks,
 Y

> On 4 Jan 2023, at 01:19, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote:
> 
> This is a Call for Consensus (Cfc) relating to the "Low Latency Streaming" use cases within the WebRTC-NV Use Cases document, Section 3.2. 
> 
> The "Game Streaming" use case is described in Section 3.2.1:  
> WebRTC Next Version Use Cases (w3c.github.io) <https://w3c.github.io/webrtc-nv-use-cases/#game-streaming>
> 
> The "Low Latency Broadcast with Fanout" use case is described in Section 3.2.2: 
> WebRTC Next Version Use Cases (w3c.github.io) <https://w3c.github.io/webrtc-nv-use-cases/#auction>
> 
> The GitHub Issues list is here: 
> Issues · w3c/webrtc-nv-use-cases (github.com) <https://github.com/w3c/webrtc-nv-use-cases/issues>
> 
> In response, please state one of the following: 
> I support addition of the "Low Latency Streaming" uses cases in Section 3.2. 
> I object to addition of the "Low Latency Streaming" use cases, due to Issues filed in open bug <# number> 
> The CfC will last until midnight Pacific Time on January 16, 2023.