Re: [ortc] DTLS/SRTP (non-mux): Are separate DTLS transports required for RTP and RTCP? (#134) from Bernard Aboba on 2014-07-18 (public-ortc@w3.org from July 2014)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Fri, 18 Jul 2014 23:27:19 +0000
To: openpeer/ortc <reply+i-38200667-0cbbe0120fbbdaf884d48762bf72840a31112ea4-808811@reply.github.c>, Peter Thatcher <pthatcher@google.com>
CC: "public-ortc@w3.org" <public-ortc@w3.org>
Message-ID: <BF4E79E7-5AEC-4277-B3EB-8C0510B42A95@microsoft.com>

If RTP and RTCP terminate in different places you MUST have two DTLS connections.

Question: in the non-mux case today does Chrome use separate DTLS sessions for RTP and RTCP?

On Jul 18, 2014, at 1:38 PM, pthatcherg <notifications@github.com<mailto:notifications@github.com>> wrote:


It would be nice if the there were one DtlsTransport with two IceTransports, to avoid needing any layers above that to know about RTP/RTCP non-mux. It's an interesting solution.

However, what if RTP and RTCP end up going to different hosts? Then you must have two different DtlsTransport objects. Would we make that impossible to do?

—
Reply to this email directly or view it on GitHub<https://github.com/openpeer/ortc/issues/134#issuecomment-49477048>.

Received on Friday, 18 July 2014 23:27:52 UTC