- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Sat, 14 Jan 2023 01:07:33 +0000
- To: "public-webrtc@w3.org" <public-webrtc@w3.org>
- Message-ID: <BYAPR00MB06132025B6DDFA9F1AAEA50BECC39@BYAPR00MB0613.namprd00.prod.outlook.com>
I support addition of the "Low Latency Streaming" uses cases in Section 3.2. However, I also believe the following GitHub Issues need to be addressed: https://github.com/w3c/webrtc-nv-use-cases/issues/80 Access to raw audio data Games are implementing increasingly more sophisticated audio functionality, including spatial audio and more advanced codecs. In these applications, raw audio is obtained and encoded by custom codecs. Today this is not straightforward. https://github.com/w3c/webrtc-nv-use-cases/issues/86: Is the DRM requirement in the Low latency Broadcast with Fanout use case satisfied by data channels? Containerized media can today be transported over the data channel, so one can argue that DRM is supported. The issue however has been that lack of worker support has been an issue for a data-channel/MSE approach to support of DRM along with low-latency transport. So my take is that requirement N36 should be removed, and a requirement for DataChannel in Workers (something along the lines of N13) should be substituted. https://github.com/w3c/webrtc-nv-use-cases/issues/91 : N15 latency control should be formulated in a technology-agnostic way In cloud gaming, most media tend to flow from the cloud to the browser endpoint, with game console input going from browser to the cloud. However, the use case shouldn't preclude peer-to-peer media so that game participants can interact with each other. So I agree that requirement N15 is formulated too narrowly. On Tue, Jan 3, 2023 at 7:20 PM 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.
Received on Saturday, 14 January 2023 01:07:52 UTC