Re: [webrtc-pc] Effect of RTCRtpSendParameters on Simulcast

@shampson @alvestrand PR https://github.com/w3c/webrtc-pc/pull/1995 recommends moving priority from encoding to sending parameters.  This would effectively remove priority as a consideration in simulcast congestion control.  I would also agree that neither maxBitrate nor maxFramerate should influence which layers are dropped. 

There has been discussion of potentially using the ordering of the layers to determine which ones are dropped when congestion occurs.   That would make sense if there are common scenarios where the typical approach (dropping higher quality layers first) is inadequate.   Personally, I have never encountered a scenario where it made sense to drop a lower quality layer first automaticallly, although there may be times when an SFU might want to tell the user agent to stop sending a lower quality layer (e.g. if all endpoints were receiving high quality so that the low quality stream wasn't being forwarded). 

-- 
GitHub Notification of comment by aboba
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1964#issuecomment-425271304 using your GitHub account

Received on Thursday, 27 September 2018 23:13:33 UTC