IETF Logo Mail Archive

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

"Ravindran, Parthasarathi" <pravindran@sonusnet.com> Sat, 17 March 2012 16:33 UTC

Return-Path: <pravindran@sonusnet.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 6534121F8658 for <rtcweb@ietfa.amsl.com>; Sat, 17 Mar 2012 09:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.826
X-Spam-Level:
X-Spam-Status: No, score=-4.826 tagged_above=-999 required=5 tests=[AWL=1.773, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 d0FQbUZvc6S4 for <rtcweb@ietfa.amsl.com>; Sat, 17 Mar 2012 09:33:08 -0700 (PDT)
Received: from na3sys010aog103.obsmtp.com (na3sys010aog103.obsmtp.com [74.125.245.74]) by ietfa.amsl.com (Postfix) with ESMTP id CA20221F863E for <rtcweb@ietf.org>; Sat, 17 Mar 2012 09:33:07 -0700 (PDT)
Received: from usma-ex-hub1.sonusnet.com ([69.147.176.212]) (using TLSv1) by na3sys010aob103.postini.com ([74.125.244.12]) with SMTP ID DSNKT2S8w+HkUozjF1l+QYUcWorOdu3vyBXk@postini.com; Sat, 17 Mar 2012 09:33:07 PDT
Received: from INBA-HUB01.sonusnet.com (10.70.51.86) by usma-ex-hub1.sonusnet.com (66.203.90.16) with Microsoft SMTP Server (TLS) id 14.2.247.3; Sat, 17 Mar 2012 12:33:18 -0400
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0355.002; Sat, 17 Mar 2012 22:03:01 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Tim Panton <tim@phonefromhere.com>
Thread-Topic: [rtcweb] Resolving RTP/SDES question in Paris
Thread-Index: AQHM8te6ZBG/XYsMg0C4SE+GOqsWNpZtZpyg///aqgCAAJauUIAATxWAgACn8QA=
Date: Sat, 17 Mar 2012 16:33:00 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C0E1FECFC@inba-mail01.sonusnet.com>
References: <4F4759DC.7060303@ericsson.com> <387F9047F55E8C42850AD6B3A7A03C6C0E1FEB69@inba-mail01.sonusnet.com> <4F63BA4E.305@jesup.org> <387F9047F55E8C42850AD6B3A7A03C6C0E1FEC15@inba-mail01.sonusnet.com> <9C904CF5-EDD4-4F4C-83C3-97053B947B17@phonefromhere.com>
In-Reply-To: <9C904CF5-EDD4-4F4C-83C3-97053B947B17@phonefromhere.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [121.242.142.186]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Randell Jesup <randell-ietf@jesup.org>, "rtcweb@ietf.org" <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: Sat, 17 Mar 2012 16:33:09 -0000

Tim,

I think that you miss the point of RTP and ICE are (IPSec) encrypted between (RTCWeb client) endpoint and Enterprise during VPN connection. So, RTP & ICE packets from endpoint are routed in WiFi ISP as IP packet with encrypted payload and no security issues.

Thanks
Partha

>-----Original Message-----
>From: Tim Panton [mailto:tim@phonefromhere.com]
>Sent: Saturday, March 17, 2012 5:23 PM
>To: Ravindran, Parthasarathi
>Cc: Randell Jesup; rtcweb@ietf.org
>Subject: Re: [rtcweb] Resolving RTP/SDES question in Paris
>
>
>On 17 Mar 2012, at 04:13, Ravindran, Parthasarathi wrote:
>
>> Randell,
>>
>> In my usecase, the application will not be able to access the website
>without VPN connection . Please explain your bid-down attack in my
>usecase.
>
>I think there probably is an vulnerability if Bob goes on line (to
>upgrade the call to video say) and happens to be on the same wifi ISP as
>Alice. The ICE probes may find a route between them that does not
>involve Alice's corporate VPN, but rather over the non-routable ISP's
>/16 network. This would result in RTP in the clear being visible on both
>parties local wifi.
>
>It's a slightly contrived case, but not impossible.
>
>Tim.

v2.23.0 | Report a Bug | By Email