Re: [rtcweb] Sebastien Cubaud's non-ICE mechanism (Re: Summary of ICE discussion)

Iñaki Baz Castillo <> Tue, 11 October 2011 08:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 260CB21F8CBC for <>; Tue, 11 Oct 2011 01:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.205
X-Spam-Status: No, score=-2.205 tagged_above=-999 required=5 tests=[AWL=-0.128, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7dQcjjbbiopv for <>; Tue, 11 Oct 2011 01:03:18 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A567F21F8C1F for <>; Tue, 11 Oct 2011 01:03:18 -0700 (PDT)
Received: by vcbfo11 with SMTP id fo11so6536173vcb.31 for <>; Tue, 11 Oct 2011 01:03:18 -0700 (PDT)
MIME-Version: 1.0
Received: by with SMTP id e2mr17043971vdj.52.1318320198060; Tue, 11 Oct 2011 01:03:18 -0700 (PDT)
Received: by with HTTP; Tue, 11 Oct 2011 01:03:18 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <> <>
Date: Tue, 11 Oct 2011 10:03:18 +0200
Message-ID: <>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <>
To: Jonathan Rosenberg <>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [rtcweb] Sebastien Cubaud's non-ICE mechanism (Re: Summary of ICE discussion)
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, 11 Oct 2011 08:03:19 -0000

2011/10/11 Jonathan Rosenberg <>et>:
> Security issues aside, the proposed solution does not work with existing
> SIP/RTP implementations. The main drawback of the ICE solution is that it
> won't work with deployed equipment. I see little benefit in specifying
> another solution which does not fix the main limitation we have with ICE.

I agree. IMHO it's time for SIP vendors to implement escurity in SIP
devices (let's say ICE and SRTP, some specifications originally
designed for SIP).

SIP is deployed in different scenarios and each scenario has its own
requirements (some of them require certain codecs, SIP over TLS,
UPDATE/PRACK methods and so on). I consider RTCweb to be another
multimedia communication scenario (but very big!!) so it can impose
its own requirements (for example ICE+SRTP which sounds appropriate
given the open Internet nature).

So if SIP vendors want to interoperate with RTCweb devices, then
implement ICE+SRTP, that's the key.

Iñaki Baz Castillo