Re: [rtcweb] Requiring ICE for RTC calls

Roman Shpount <roman@telurix.com> Wed, 28 September 2011 19:41 UTC

Return-Path: <roman@telurix.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D64C11E811D for <rtcweb@ietfa.amsl.com>; Wed, 28 Sep 2011 12:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.615
X-Spam-Level:
X-Spam-Status: No, score=-2.615 tagged_above=-999 required=5 tests=[AWL=0.361, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mmiyCQojomDH for <rtcweb@ietfa.amsl.com>; Wed, 28 Sep 2011 12:41:29 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 69E6811E80FF for <rtcweb@ietf.org>; Wed, 28 Sep 2011 12:41:29 -0700 (PDT)
Received: by gyd12 with SMTP id 12so8153364gyd.31 for <rtcweb@ietf.org>; Wed, 28 Sep 2011 12:44:18 -0700 (PDT)
Received: by 10.236.132.81 with SMTP id n57mr58153045yhi.47.1317239057922; Wed, 28 Sep 2011 12:44:17 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by mx.google.com with ESMTPS id w50sm23196533yhi.2.2011.09.28.12.44.16 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Sep 2011 12:44:17 -0700 (PDT)
Received: by yxt33 with SMTP id 33so8308417yxt.31 for <rtcweb@ietf.org>; Wed, 28 Sep 2011 12:44:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.33.130 with SMTP id r2mr46289353pbi.71.1317239056342; Wed, 28 Sep 2011 12:44:16 -0700 (PDT)
Received: by 10.68.40.197 with HTTP; Wed, 28 Sep 2011 12:44:16 -0700 (PDT)
In-Reply-To: <E8461E62-15F6-4726-A450-5EF8C3602C5E@cisco.com>
References: <CAD5OKxtNjmWBz92bRuxka7e-BUpTPgVUvr3ahJGpmZ-U5nuPbQ@mail.gmail.com> <CAD6AjGSmz5T_F+SK2EoBQm6T-iRKp7dd4j8ZAF5JKdbbyomZQA@mail.gmail.com> <CALiegfmO54HC+g9L_DYn4jtXAAbLEvS++qxKa6TNrLDREs9SeA@mail.gmail.com> <4E80984A.903@skype.net> <CALiegfmyvTb57WVooKryS-ubfcg+w5gZ+zfO1zzBLn3609AzaA@mail.gmail.com> <4E809EE6.2050702@skype.net> <CAD5OKxvUOadaU0dnB7-Ho9cZ92VY+4Owuhj7oKPCx9Jy1iwT1Q@mail.gmail.com> <C2DF2C51-B3F7-443D-A047-7E6FB03E6D20@phonefromhere.com> <CAOJ7v-3AJJcdrCKcH4AJmv_016sZtcOPOo8yCv3Va65eJogAkQ@mail.gmail.com> <53C72381-DC23-4A6A-944C-B418791876B0@cisco.com> <CAD5OKxuWj5M_tFQ2qrHfz3jbAyZH-cGLNbOT_oyEnhwHzJp04w@mail.gmail.com> <E8461E62-15F6-4726-A450-5EF8C3602C5E@cisco.com>
Date: Wed, 28 Sep 2011 15:44:16 -0400
Message-ID: <CAD5OKxsfv9v5LyCTQZ2M-fTeSD3R7GnNmxmTG31Puj4FiQsHFQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec520f611099e6004ae059e39
Cc: Randell Jesup <randell-ietf@jesup.org>, rtcweb@ietf.org
Subject: Re: [rtcweb] Requiring ICE for RTC calls
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2011 19:41:30 -0000

On Wed, Sep 28, 2011 at 1:04 PM, Cullen Jennings <fluffy@cisco.com> 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