Re: [rtcweb] Requiring ICE for RTC calls

[Cullen Jennings <[e-mail]>]

On Sep 28, 2011, at 1:44 PM, Roman Shpount wrote:

> 
> On Wed, Sep 28, 2011 at 1:04 PM, Cullen Jennings <[e-mail]> wrote:
> I agree with you point that the majority of deployed phones don't support ICE. But so what, what do you propose to do. One thing that is not going to happen is browser vendors do something which makes browsers such a security threat that the browsers are banned from every corporate network. Solutions like CORS solve the problem but short of something like that, I don't see browser vendors deciding that remove same origin policy is a good idea.
> 
> 
> As I wrote before, you can use RTC not only in the desktop browser but also in the desktop phone. It is not unreasonable to use the same CPU platform being used in mobile phones and build a desk IP phone which primarily runs the web browser to control its screen and uses RTC to setup voice/video calls. This phone can be a much better and more extendable standard platform for building UC solutions then most of the current SIP phones. The problem is if standard requires ICE/SRTP this phone will not be able to work with most of the current enterprise phones. Once again, since this can be considered a marginal use case, we don't need to cover it in the standard and the phone vendor can just ignore that ICE requirement since it knows that the phone is located in the fully controlled network.
> _____________
> Roman Shpount
> 

Sure, in that sort of case, I'm sure lots of the code being open sourced for RTCweb will will be reused to build phones and modified in ways like you suggest - but as you say, that's outside the scope of what we want to solve here.