Re: [webrtc-pc] "getParameters" and "setParameters" need more thorough specification

Another question that came up for me recently: if the remote description didn't signal SSRCs explicitly, what should `RTCRtpReceiver.getParameters` return in `encodings`? We could have it return a single `RTCRtpEncodingParameters`, with the `ssrc` set if a packet has been received and the SSRC is known, and `undefined` otherwise. Any opinion, @aboba? Maybe it doesn't matter, since WebRTC 1.0 only has `getParameters`, and ORTC only has `receive()`, so there's no situation where the return value of `getParameters` would be passed back into the `RTCRtpReceiver`.

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

Received on Monday, 10 April 2017 03:11:21 UTC