RE: Issue 151: Multiplexing Requirements

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]."
________________________________________
From: Bernard Aboba [Bernard.Aboba@microsoft.com]
Sent: Sunday, September 21, 2014 9:33 PM
To: public-ortc@w3.org
Subject: Issue 151: Multiplexing Requirements

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]."

[MUX-FIXES]
M. Petit-Huguenin; G. Salgueiro. Multiplexing Scheme Updates for Secure Real-time Transport Protocol (SRTP) Extension for Datagram Transport Layer Security (DTLS). 2 July 2014. Internet Draft (work in progress). URL: http://tools.ietf.org/html/draft-petithuguenin-avtcore-rfc5764-mux-fixes

Received on Monday, 22 September 2014 15:35:47 UTC