W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2019

[webrtc-pc] rtcpTransport should be null when bundling (#2057)

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Tue, 15 Jan 2019 13:53:41 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-399354888-1547560420-sysbot+gh@w3.org>
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc:

== rtcpTransport should be null when bundling ==
There seems to be an inconsistency between the following two statements:

"Otherwise, let transport and rtcpTransport be newly created RTCDtlsTransport objects, each with a new underlying RTCIceTransport. Though if RTCP multiplexing is negotiated according to [RFC5761], or if connection's RTCRtcpMuxPolicy is require, do not create any RTCP-specific transport objects, and instead let rtcpTransport equal transport." (4.4.1.6 Set the RTCSessionDescription, bullet 2.2.7.1.1.5)

"rtcpTransport of type RTCDtlsTransport, readonly, nullable
The rtcpTransport attribute is the transport over which RTCP is sent and received. Prior to construction of the RTCDtlsTransport object, the rtcpTransport attribute will be null. When RTCP mux is used (or bundling, which mandates RTCP mux), rtcpTransport will be null, and both RTP and RTCP traffic will flow over the transport described by transport.

On getting, the attribute MUST return the value of the [[SenderRtcpTransport]] slot." (section 5.2 RTCRtpSender interface, rtcpTransport attribute).

Suggested fix: Modify 4.4.1.6 bullet 2.2.7.1.1.5 to set rtcpTransport to null.


Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2057 using your GitHub account
Received on Tuesday, 15 January 2019 13:53:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 October 2019 15:15:00 UTC