Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb

[Binod <[e-mail]>]

I have been reading the discussion on this topic and I prefer
supporting SDES as a keying method for WebRTC.

Not having SDES will have non trivial impact on interop. With
EKT, there is a signalling complexity of sending re-INVITEs, which
make the gateway complex. Without EKT, you need per-packet
crypto  for media exchange, which is CPU intensive.

The fingerprint verification and all other additional DTLS-SRTP
advantages can still be leveraged when both side support DTLS-SRTP.
And then if a gateway really do not want to use SDES, it can support
DTLS/SDES gateway anyway.

thanks,
Binod.

On Thursday 25 April 2013 09:27 PM, Cullen Jennings wrote:
> The working groups committed some time ago to have a further discussion on whether SDP Security Descriptions (RFC 4568 aka SDES) would be usable as a keying method for WebRTC.  As we prepare for that discussion, we'd like to have expressions of interest or support for that approach which indicate the general outlines of support proposed.  If you wish to make such an expression of support, please send it to the chairs or the list.
>
> Cullen, Magnus, & Ted <The Chairs>
>
>
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb