- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Wed, 11 May 2016 02:42:12 +0000
- To: "public-webrtc@w3.org" <public-webrtc@w3.org>
- CC: Peter Thatcher <pthatcher@google.com>
Received on Wednesday, 11 May 2016 07:26:43 UTC
Github Issue 622: https://github.com/w3c/webrtc-pc/issues/622 Proposed PR 629: https://github.com/w3c/webrtc-pc/pull/629 It would appear that there is a need for clarification of which RTCRtpEncodingParameters attributes apply to the RtpSender/RtpReceiver and which are read-only versus read-write. In the spirit of the IETF (where the quickest way to get a discussion going is to post a proposed resolution that is horribly wrong), here is a potential table for Section 5.2.4: Usage of the attributes is defined in the table below: Attribute Type Receiver/Sender Read/Write ssrc unsigned long Sender Read-only fec RTCRtpFecParameters<http://internaut.com:8080/~baboba/ortc/github/webrtc-pc-master/webrtc.html#idl-def-RTCRtpFecParameters> Receiver/Sender Read-only rtx RTCRtpRtxParameters<http://internaut.com:8080/~baboba/ortc/github/webrtc-pc-master/webrtc.html#idl-def-RTCRtpRtxParameters> Receiver/Sender Read-only active boolean Sender Read/Write priority RTCPriorityType<http://internaut.com:8080/~baboba/ortc/github/webrtc-pc-master/webrtc.html#idl-def-RTCPriorityType> Sender Read/Write maxBitrate unsigned long Sender Read/Write maxFramerate unsigned long Sender Read/Write scaleResolutionDownBy double Sender Read/Write rid DOMString Sender Read/Write
Received on Wednesday, 11 May 2016 07:26:43 UTC