Re: [MMUSIC] Bundling data channel and RTP? - Text proposal

[Roman Shpount <[e-mail]>]

On Fri, May 29, 2015 at 1:24 AM, Christer Holmberg <
[e-mail]> wrote:

>
> >I would suggest "use_srtp" extension must always be enabled for DTLS
> session used in bundle.
>
> Assuming SRTP is supported, I assume. If a node doesn't support SRTP to
> begin with, or if an application is never going to offer (or accept if
> offered) SRTP, I guess there is no reason to mandate "use_srtp".
>
> Now, there are statements in RFC 5764 saying e.g.:
>
>         "This extension MUST only be used when the data being transported
> is RTP or RTCP [RFC3550]."
>
> That of course makes sense for a non-BUNDLE DTLS connection, but I wonder
> whether we somehow explicitly need to say that it doesn't apply for BUNDLE?
>
>
Another big question how would current browser implementations handle a
DTLS connection without "use_srtp" extension. I have a strong suspicion
that DTLS session setup will fail without this extension present. I think,
WebRTC enabled browsers currently export SRTP key material during session
setup even if no SRTP traffic is ever sent or received by this connection
and fail the entire connection if key export fails. This, most likely, can
be modified to only export SRTP key material when SRTP session is actually
created and defining some sort of fall back procedure when a media track is
actually added to a connection without "use_srtp" (either failure or
require renegotiation with new transport).

To conclude, the group can either decide that all DTLS sessions in bundle
should be setup with "use_srtp" extension and keep the current
implementations working as they are currently coded, or allow not to
include this extension and fix the implementations.
_____________
Roman Shpount