henbos has just submitted a new pull request for https://github.com/w3c/webrtc-pc: == RTCRtpReceiver.jitterBufferDelayHint attribute added. == Fixes #2139. This is another stab at what #2138 is trying to achieve. This reformulates and clarifies things, but does not necessarily address all concerns of this API. Notably: - The API is not well specified because congestion control is outside the scope of webrtc-pc and I don't think anyone wants to change that. More SHOULD language is added to advice implementations, but there are no hard requirements. As such there is a risk that different implementations behave differently, but note that this statement is already true for any congestion control in place already. - This may be an "NV" feature, not "1.0", but if not here, where does this go? Extension specs is an option, but lack of support becomes a bigger risk. Is this enough to continue the discussion, or do we (Chrome) need to investigate alternatives? @kuddai @alvestrand @jan-ivar @foolip See https://github.com/w3c/webrtc-pc/pull/2149Received on Thursday, 28 March 2019 14:56:18 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:46 UTC