Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Multiplexing Requirements #151
One of the assumptions of WebRTC is that DTLS, STUN/TURN and RTP and/or RTCP can be multiplexed over the same port. The description of how the multiplexing works is contained in draft-petithuguenin-avtcore-rfc5764-mux-fixes yet this document is not referenced in any RTCWEB WG work item.
To make it clear that this draft needs to be implemented, I'd propose to add the following text to Section 2.2:
"In order to enable multiplexing of DTLS and STUN/TURN with RTP and/or RTCP, implementations must support [MUX-FIXES]."
Since [MUX-FIXES] is not yet a WG work item, a normative reference is probably pre-mature, so how about the following revised-text:
"Since the DTLS negotiation occurs between transport endpoints determined via Interactive Connectivity Establishment (ICE), implementations of this specification MUST support multiplexing of STUN, TURN, DTLS and RTP and/or RTCP. This multiplexing, originally described in [RFC5764] Section 5.1.2, is being revised in [MUX-FIXES]."
Also recommend adding the following text to Section 16.1:
Via the use of [BUNDLE] it is possible for WebRTC 1.0 implementations to multiplex audio and video on the same RTP session. Within ORTC API, equialent behavior can be obtained by constructing multiple RTCRtpReceiver and RTCRtpSender objects from the same RTCDtlsTranport object. As noted in [RTP-USAGE] Section 4.4, support for audio/video multiplexing is required, as described in [RTP-MULTI-STREAM].