Can rtpReceiver.rtcpTransport retrieve null?

[ibc]

var transport = new RTCDtlsTransport(...);
var rtpReceiver = new RTCRtpReceiver(transport);

rtpReceiver.transport;
// => transport

rtpReceiver.rtcpTransport;
// => transport or null or undefined?

[aboba]

I believe that rtcpTransport should be unset in this case since an rtcpTransport was not supplied in the constructor.

[ibc]

Another approach would be for the getter to retrieve the effective RTCDtlsTransport, which at the end is the given transport.

IMHO it should be clarified in the spec.

[aboba]

Just found the corresponding text in WebRTC 1.0.

Section 5.2.1 (RTCRtpSender)

The rtcpTransport attribute is the transport over which RTCP is sent and received. When BUNDLE is used, many RTCRtpSender objects will share one rtcpTransport and will all send and receive RTCP over the same transport. When RTCP mux is used, rtcpTransport will be null, and both RTP and RTCP traffic will flow over the transport described by transport.

Section 5.3.1 (RTCRtpReceiver)

The RTCRtpReceiver.rtcpTransport attribute is the transport over which RTCP is sent and received. When BUNDLE is used, many RTCRtpReceiver objects will share one RTCRtpReceiver.rtcpTransport and will all send and receive RTCP over the same transport. When RTCP mux is used, RTCRtpReceiver.rtcpTransport will be null, and both RTP and RTCP traffic will flow over RTCRtpReceiver.transport.

[ibc]

Clear. Thanks.