- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 May 2017 22:26:37 +0000
- To: public-webrtc-logs@w3.org
> An attempt to set a read-only parameter in setParameters() results in a rejection of the promise with an InvalidModificationError. Should addTransceiver behave the same way? Good point. Now throwing errors. > When will getParameters() return other attributes of RTCRtpParameters such as rtcp or degradationPreference? Let's see. `degradationPreference` is only valid for a sender, and should return whatever it was last set to. For the `RTCRtcpParameters`, it's a bit different between a sender and receiver. **Sender**: * `cname` should be there from creation time, since there should only be one CNAME per PeerConnection. * `reducedSize` should be `true` if the remote description contains "a=rtcp-rsize" and the implementation supports it, and `false` otherwise. **Receiver**: * `cname` never set, since it's not signaled in SDP? * `reducedSize` set to `true` if the receiver is prepared to received reduced-size RTCP. Which means either it was offered (in a local offer; still waiting for answer), or it's fully negotiated (in both local and remote description, `signalingState` is "stable"). Does that all sound reasonable? -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/1134#issuecomment-298449272 using your GitHub account
Received on Monday, 1 May 2017 22:26:44 UTC