Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRTP is a need

Iñaki Baz Castillo <ibc@aliax.net> Wed, 04 April 2012 17:34 UTC

Return-Path: <ibc@aliax.net>
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 D632C21F8732 for <rtcweb@ietfa.amsl.com>; Wed, 4 Apr 2012 10:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.315
X-Spam-Level:
X-Spam-Status: No, score=-2.315 tagged_above=-999 required=5 tests=[AWL=-0.338, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_BIZOP=0.7]
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 idlE3rREHXAT for <rtcweb@ietfa.amsl.com>; Wed, 4 Apr 2012 10:34:39 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA3621F86DA for <rtcweb@ietf.org>; Wed, 4 Apr 2012 10:34:39 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so437218vbb.31 for <rtcweb@ietf.org>; Wed, 04 Apr 2012 10:34:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=63Z/PKP7mLc7b7xmS7rSVFdw2wCgvsoWF5XhTnVkwEA=; b=XzPUkIiqq+vnDcT1afxc8qbiS/w6mJFY9gd0YpucLCf926dDpml78NvtdhlnKogOGz +bkzhr51+pyZr/MeZ6lO+X7g/rtvIKiDxPPPQTw/wSIgubB6nSFAI0lfq8sd0UAZ49SX BUs0xvVQE55NRBPbqg5MJpEMrdHgmxeYBIakJ2LtNZ3tqOClkS+Ex2vlDazQJi5YjVem CxrhJUArQgCUpa7bU4CZ3d6mbmEQ3oFCwa3EuC9QiiAPIUBez/TzXl3tN3UYqEvO0Pgk 3l4FJ+mgxYEwKiG66ABziJE6z4VqJY7JRDjoO1aP0K+Vub4MdiEFywJyH4nXQ1SJOPAH lETw==
Received: by 10.52.27.1 with SMTP id p1mr7945954vdg.17.1333560878631; Wed, 04 Apr 2012 10:34:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.170.165 with HTTP; Wed, 4 Apr 2012 10:34:18 -0700 (PDT)
In-Reply-To: <CAD5OKxsxrDdsoV18KB1gZSsUBPno-k2zs4E2FTUaoUBdXfh5yA@mail.gmail.com>
References: <CALiegfmz6tgm9WF3KWEK5qwaBGADKFyit=egB36zkjZXNKdeHw@mail.gmail.com> <CALiegfnA8_ntYd5f935P_E6vvMwjrzt+j6UhB9vjmo6h-RzfPA@mail.gmail.com> <CAD5OKxsxrDdsoV18KB1gZSsUBPno-k2zs4E2FTUaoUBdXfh5yA@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Wed, 04 Apr 2012 19:34:18 +0200
Message-ID: <CALiegfkMGQknktTbnCxA-Xb6_x_WFVyG1Atk0uNq8H3bfeScrA@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlVmnivPbzgBj0SrGVdM8cLHBeHUXb9JccNoja36y4/HDC97OeGOAfglZq+SGlGaqB3dTc9
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRTP is a need
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, 04 Apr 2012 17:34:40 -0000

2012/4/4 Roman Shpount <roman@telurix.com>:
> On Wed, Apr 4, 2012 at 12:43 PM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
>>
>> Hi, nobody cares about the implications of option 2 ???
>>
>> Do all the people planning to interop with SIP assume that they'll
>> need the super B2BUA in the second image (without the possibility of
>> using a pure SIP proxy)?:
>>
>>  http://public.aliax.net/WebRTC/WebRTC_SIP_Interop_DTLS-EKT-SRTP.png
>>
>
> <sarcasm>I guess we should look at this as a business opportunity ;) I am
> not sure why you assume that building such gateway would take 10 years. I
> can sell a gateway like this to anybody who needs it right now.</sarcasm>
>
> My assumption is that IP phones will migrate to WebRTC effectively
> eliminating SIP in end user devices. The only place where SIP will remain
> would be federation, which commonly uses some sort of SBC anyway. This SBC
> will need to be extended to support ICE anyway. Might as well through in
> support for DTLS-EKV-SRTP. I doubt it will map DTLS key updates to
> re-invites. Most probably it will simply re-encode.

Roman... I hope you missed the </sarcasm> closing tag just HERE, am I
right? XDDD

-- 
Iñaki Baz Castillo
<ibc@aliax.net>