Re: [rtcweb] Requiring ICE for RTC calls

"Ravindran Parthasarathi" <> Tue, 27 September 2011 18:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4AAAB21F8EC4 for <>; Tue, 27 Sep 2011 11:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.497
X-Spam-Status: No, score=-2.497 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Hb8nF4MaWpYz for <>; Tue, 27 Sep 2011 11:52:31 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5D46021F8EBC for <>; Tue, 27 Sep 2011 11:52:31 -0700 (PDT)
Received: from ( []) by (8.14.3/8.14.3) with ESMTP id p8RItmc8016562; Tue, 27 Sep 2011 14:55:48 -0400
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.4675); Tue, 27 Sep 2011 14:55:16 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC7D46.FD3E5C79"
Date: Wed, 28 Sep 2011 00:25:11 +0530
Message-ID: <>
In-Reply-To: <>
Thread-Topic: [rtcweb] Requiring ICE for RTC calls
Thread-Index: Acx9RKxdtWZqVlkhRSumcfL0ddw6VwAAQNxw
References: <><><><><><><><BLU152-W62B7F2AC3F0D5B6E277CB993F00@phx.gbl><><><><><><> <>
From: Ravindran Parthasarathi <>
To: Roman Shpount <>, Matthew Kaufman <>
X-OriginalArrivalTime: 27 Sep 2011 18:55:16.0549 (UTC) FILETIME=[FEF40750:01CC7D46]
Subject: Re: [rtcweb] Requiring ICE for RTC calls
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 27 Sep 2011 18:52:32 -0000

Hi Roman,


RTCWeb application within Enterprise looks the reasonable argument for
not mandating ICE & SRTP in RTCWeb browser  because Enterprise shall be
visualized as single reachable private network with no NAT & SRTP
requirement. ICE & SRTP are overhead within Enterprise.


In case I understand you correctly, RTCWeb API should provide the
mechanism to include ICE & SRTP on the need basis.







From: [] On Behalf
Of Roman Shpount
Sent: Wednesday, September 28, 2011 12:08 AM
To: Matthew Kaufman
Subject: Re: [rtcweb] Requiring ICE for RTC calls


What about intranet applications that would want to locally call
existing IP phones within the same enterprise? Should we force them to
go through a media gateway as well or should we allow to overwrite this
using a policy?

As far as SRTP is concerned, once again we should at least provide a
local policy. Otherwise it would be a real problem to test and debug
Roman Shpount

On Tue, Sep 27, 2011 at 1:30 PM, Matthew Kaufman
<> wrote:

On 9/27/11 10:01 AM, Justin Uberti wrote:

Neither Google Voice nor Skype (both fairly popular services) send raw
RTP directly from the client to a PSTN terminator. 




	I can't speak for Skype, but Google Voice uses a media gateway
for the quality-related reasons I mentioned earlier.


I can't speak for Skype either, but this is a good guess.


	Since these large-scale services can deploy media gateways, it's
clear that this is not a significant impediment.


Agree. I'm not at all sure what the argument is that we need
existing-PSTN-gateway-compatible RTP (without SRTP or ICE). If there is
demand, these gateways will be upgraded to support RTCWeb. If there is
not, service providers can run intermediate gateways.

Matthew Kaufman