IETF Logo Mail Archive

Re: [rtcweb] Resolving RTP/SDES question in Paris

Bernard Aboba <bernard_aboba@hotmail.com> Mon, 19 March 2012 12:14 UTC

Return-Path: <bernard_aboba@hotmail.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 1A34021F8647 for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 05:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.973
X-Spam-Level:
X-Spam-Status: No, score=-101.973 tagged_above=-999 required=5 tests=[AWL=0.625, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 PTUoPdimoIC9 for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 05:14:13 -0700 (PDT)
Received: from blu0-omc2-s16.blu0.hotmail.com (blu0-omc2-s16.blu0.hotmail.com [65.55.111.91]) by ietfa.amsl.com (Postfix) with ESMTP id 8D43921F84B9 for <rtcweb@ietf.org>; Mon, 19 Mar 2012 05:14:12 -0700 (PDT)
Received: from BLU169-W29 ([65.55.111.73]) by blu0-omc2-s16.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 19 Mar 2012 05:14:11 -0700
Message-ID: <BLU169-W29E5B86F9E2C6F3126961C93420@phx.gbl>
Content-Type: multipart/alternative; boundary="_5be95578-009e-496a-90af-aa19ae6908ef_"
X-Originating-IP: [99.32.177.175]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: ibc@aliax.net
Date: Mon, 19 Mar 2012 05:14:11 -0700
Importance: Normal
In-Reply-To: <CALiegf=jtkDCS_D0ZFe9UpbiadQ0vsJ+4MppQSbLr-wbaXNrfQ@mail.gmail.com>
References: <4F4759DC.7060303@ericsson.com>, <387F9047F55E8C42850AD6B3A7A03C6C0E1FEB69@inba-mail01.sonusnet.com>, <CALiegfnkYVEpmPV-zSL_4wOY-HiFZN-qJCQCiioaS=5NaqhLZw@mail.gmail.com>, <CAD5OKxvtOAxMBx6xDnyfTnEq76oDEm6uj1xL6wGjjrtKUAHy3g@mail.gmail.com>, <CABcZeBNZiotPmCfT53uEo+O0xw4xv6tXW1M_G-3A5BHuncsduA@mail.gmail.com>, <CAD5OKxvYOY5JZ2mYNGiH1poUBQkyOOycePFijH5H+SxtcdqujQ@mail.gmail.com>, <CABkgnnVe-b6Sv=R67bMJk_NQqQwdrRUn6rBm7Gu_CMcfPQwtEg@mail.gmail.com>, <CAD5OKxvZbEJ7sV4WPAYoQapzMR_QwAftj-oKg=ioMKHNT792wQ@mail.gmail.com>, <6F428EFD2B8C2F49A2FB1317291A76C113563C5A92@USNAVSXCHMBSA1.ndc.alcatel-lucent.com>, <CALiegf=jtkDCS_D0ZFe9UpbiadQ0vsJ+4MppQSbLr-wbaXNrfQ@mail.gmail.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 19 Mar 2012 12:14:11.0568 (UTC) FILETIME=[CAFBD700:01CD05C9]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Resolving RTP/SDES question in Paris
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: Mon, 19 Mar 2012 12:14:14 -0000

> Which ones? I just see one: interoperability with legacy SIP devices.

[BA] Agreed.  And as we've already seen, SDES/SRTP support is prevalent enough among legacy devices that the legacy use case does not require RTP. 

> Even if you use an VPN for your enterprise WebRTC application there is NO problem at all in using SRTP
> over the VPN.

[BA] And in fact, this is exactly the NSA "Secure VoIP" architecture (with SDES/SRTP, by the way). 

> I can make business with my legacy and not secure SIP devices,
> those that don't implement SRTP regardless SRTP was designed for SIP".

[BA] At this point, support for SRTP is an expected feature on legacy equipment.  For
example, all the leading PSTN gateway vendors support SRTP already.  By the time
RTCWEB specs are final, SRTP support will be very prevalent.

v2.23.0 | Report a Bug | By Email