Re: [rtcweb] SRTP not mandatory-to-use

[Roman Shpount <[e-mail]>]

On Wed, Jan 11, 2012 at 4:20 PM, Randell Jesup <[e-mail]>wrote:

>
> I'd like to explore the possibility of making sure there's a workable
> DTLS-SRTP implementation openly available, and locking WebRTC down to that
> only.
>
> I should note that while libsrtp 1.4.2 (last official release) doesn't
> have DTLS-SRTP support, there are DTLS-SRTP support functions and test code
> in the project's CVS since ~2006, and resiprocate/recon supports DTLS-SRTP
> via a modified OpenSSL.  So, I'm not sure the barrier is huge given DTLS
> support already.
>
>
Can you name a single soft-phone, hard-phone, SBC, or gateway that
currently supports DTLS-SRTP?

The reason I am asking is libsrtp, despite being widely used, is extremely
buggy (last official release for instance crashes with GPF), and does not
even provide full DES-SRTP implementation (no F8_128_HMAC_SHA1_8 support).

As far as DTLS (non-SRTP) implementations are concerned, can anybody
provide an indication on how widely they are used? I know that OpenSSL
supported DTLS for a while, but what commonly used software is using this?

Also, what would be the impact of adding DTLS to SBC? It would be
interesting to hear from SBC implementers before decision is made.

How many additional round trips does DTLS require for connection setup? Are
we planning to support certificate validation?
_____________
Roman Shpount