- From: Iñaki Baz Castillo <ibc@aliax.net>
- Date: Tue, 2 Feb 2016 14:00:06 +0100
- To: Peter Thatcher <pthatcher@google.com>
- Cc: Iñaki Baz Castillo via GitHub <sysbot+gh@w3.org>, "public-ortc@w3.org" <public-ortc@w3.org>
2016-02-01 21:48 GMT+01:00 Peter Thatcher <pthatcher@google.com>: > An RtpSender or RtpReceiver is not bound to a particular DtlsTransport > permanently. The RtpSender.transport can be changed on the fly. Otherwise, > you wouldn't be able to implement BUNDLE in PeerConneciton on top of ORTC. > > Further, that would mean that a DTLS thing know about RTP things, which is > kind of weird. A DTLS thing should really only know about DTLS. Yes, I did not properly expose my concerns. They are more about "internal design" when implementing ORTC with all the non rtcp-mux capabilities. Thanks. I'll close the issue. -- Iñaki Baz Castillo <ibc@aliax.net>
Received on Tuesday, 2 February 2016 13:00:55 UTC