Re: Issue 114: Identity Assertions and RTCDtlsTransport objects

Since it is now possible to have distinct RTCDtlsTransport objects for RTP and RTCP, this raises some questions. For example:

a. Are the certificates used for RTP and RTCP DTLS Transports necessarily the same on both the local and remote side? If they are supposed to be the same, what happens if they aren't?

b. Can different identities be asserted for the RTP and RTCP DTLS Transports? Does this make sense in some circumstances? If so, when?

[BA]  Within a browser, it would appear to me that the certificates used for RTP and RTCP DTLS Transports should be the same (assuming that RTP and RTCP aren't multiplexed). 

However, I am wondering whether a SFU could potentially terminate RTCP but not RTP, in which case the certificates and asserted identities might be different between RTP and RTCP.  

A question is whether a browser should care about what the asserted identity is for RTCP, or whether it should just focus on RTP.  So while a browser would always use the same certificate and identity for both RTP and RTCP, the question is whether it should be "strict in what it sends, liberal in what it is willing to receive".

Received on Tuesday, 8 July 2014 17:40:40 UTC