search

w3c / webrtc-nv-use-cases

Use cases for WebRTC NV
https://w3c.github.io/webrtc-nv-use-cases/
Other
32 stars 13 forks source link

N42 and N47 partly overlapping #127

Closed stefhak closed 11 months ago

stefhak commented 11 months ago

N42: The WebRTC connection can generate signals indicating the desired bandwidth and any demands for keyframes, and surface those to the application.

N47: The WebRTC connection can generate signals indicating demands for keyframes, and surface those to the application.

Perhaps the "and any demands for keyframes" part of N42 should be scrapped?

alvestrand commented 11 months ago

Keeping them orthogonal seems good to me.

BTW, N47 is probably satisfied by https://github.com/w3c/webrtc-encoded-transform/pull/215

stefhak commented 11 months ago

OK, perhaps we should have a table or something recording what requirements are (becoming) satisfied, and how. There is also the comment "This requirement is addressed by jitterBufferTarget, defined in [WebRTC-Extensions] Section 6." for N38.