Re: Call for Consensus (CfC): WebRTC-NV "One-way media" Use Cases (Section 3.10))

I support the addition of "One-way media" use cases.  Some comments:

In the use case described in Section 3.10.1, I wonder what happens if the traffic cam supports a codec (e.g. HEVC) that is not supported in WebRTC.  Can the application still receive the encoded frames and send out RTP packets?

In the use case described in Section 3.10.2, what if the stored content uses a codec not supported in WebRTC-PC (e.g. HEVC)? Can the application de-containerized the encoded frames and send out RTP packets?

In the use case described in Section 3.10.3, can the application handle de-packetizing and then pass the frames to WebCodecs for decoding?

Is there a requirement for the application to be able to control packetization/de-packetization?

Filed as https://github.com/w3c/webrtc-nv-use-cases/issues/96













============================================

This is a Call for Consensus (CfC) on the WebRTC-NV "One-way media" Use Cases described in Section 3.10:

3.10.1     Live encoded non-WebRTC media
3.10.2     Transmitting stored encoded media
3.10.3      Decoding pre-encoded media

The use cases are available for inspection here:
https://w3c.github.io/webrtc-nv-use-cases/#one-way-media

The GitHub repo 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 "One-way  media" use cases
  *   I object to addition of the "One-way media" use cases, due to issues filed in <link to GitHub issues>

The CfC will last until midnight Pacific Time on February 6, 2023.

Bernard
For the Chairs