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

[Spencer Dawkins <[e-mail]>]

On 1/5/2012 11:08 AM, Alan Johnston wrote:
> On Thu, Jan 5, 2012 at 10:56 AM, Cullen Jennings<[e-mail]>  wrote:
>>
>> On Jan 4, 2012, at 8:36 PM, Justin Uberti wrote:
>>
>>>
>>> This argument about debugging keeps coming up, and although I am not persuaded by this argument, it is not a completely unreasonable request. However, I don't think this needs to be controllable from JS. One could easily imagine a plain-RTP option being available from a developer options dialog or console, for use by developers in debugging specific problems with their service.
>>> _______________________________________________
>>
>> I think the best solution for the debugging issue is to allow SRTP to negotiate a NULL cipher in special cases such as Justin described above. This keeps what you are debugging as close as possible to the version when debugging is turned off. I like Justin's idea of having to enable this in the browser and not having it under JS control.
>>
>> Cullen (in my individual contributor role)
>
>
> This seems like the right way to do this.
>
> - Alan -

And to me.

So, just to ask the next question ... if we require the use of SRTP and 
allow NULL ciphers (for debugging and whatnot), are there any remaining 
problems with requiring the use of SRTP?

Thanks,

Spencer