- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Fri, 4 Jul 2014 00:16:43 +0000
- To: "public-ortc@w3.org" <public-ortc@w3.org>
In the situation where RTP and RTCP are not multiplexed, we will have an RTCIceTransport for RTP and another one (created via RTCIceTransport.createAssociatedTransport()) for RTCP.
In turn, we can then construct RTCDtlsTransport objects for RTP and RTCP from the RTP and RTCP RTCIceTransport objects.
Given this, it is possible for the RTCSctpTransport used by the Data Channel to be constructed either from the RTP RTCDtlsTransport or the RTCP RTCDtlsTransport.
Personally, it is not obvious to me why you'd want to multiplex the Data Channel with SRTCP as opposed to SRTP, but it can be done.
Since the API always envisages Data Channel being multiplexed over an ICE transport used by RTP or RTCP, there is no "component" value for DataChannel.
Does this make sense?
On July 2, 2014 at 5:21:49 PM, Iņaki Baz Castillo (ibc@aliax.net) wrote:
enum RTCIceComponent {
"RTP",
"RTCP"
};
What should be the value for a DataChannel?
Received on Friday, 4 July 2014 00:17:13 UTC