IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 19 March 2012 16:11 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 CBE3F21F885B for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 09:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.623
X-Spam-Level:
X-Spam-Status: No, score=-2.623 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 JHR9xgqny8lC for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 09:11:09 -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 0262721F8852 for <rtcweb@ietf.org>; Mon, 19 Mar 2012 09:11:08 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so801552vbb.31 for <rtcweb@ietf.org>; Mon, 19 Mar 2012 09:11:08 -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=7VCuQT2lUGqAccSmldn/TTspmWJcgC2S2NNwo7qG5uo=; b=lHvrCADKD+eMfZL8jvjPiOSFViEd+HX1NoVHqv/SL8ASzTZJnsF6SXiEmrGplsMfXa P7RwpE2sxtDDJCJq7r553IIezc8rN907z1bwPOg9uufggRJvy1S2wrfd7vQtjmv54Q3s MIALdd7O38jJMzjt3iSnJGCpXp3gVaiGY4pMQ+2s1ArkAB59eGKC57HHn4LiCSDUwmjF 6C7gJ9iURxXuwuYlbwqF7Wzhr0ZI+194FOo6joCa+Bp87PsDI35TPNdO/ZOFqewj/fMx UMpVz4GobnwzcrL6aE/dLQ4yzW6QDLQOm4orrGf9sEd6lXPK0OL8jdcckmREijm2RkEM dzGg==
Received: by 10.52.65.239 with SMTP id a15mr5938057vdt.51.1332173468384; Mon, 19 Mar 2012 09:11:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.170.165 with HTTP; Mon, 19 Mar 2012 09:10:48 -0700 (PDT)
In-Reply-To: <6F428EFD2B8C2F49A2FB1317291A76C113564482A7@USNAVSXCHMBSA1.ndc.alcatel-lucent.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> <BLU169-W29E5B86F9E2C6F3126961C93420@phx.gbl> <CALiegfk2aT+6Psr4nT-hG1G7eYRBfFCcT+25On2O4HfUXJ6-ng@mail.gmail.com> <CAD6AjGSmi9j+sdGWPts20-iwGvGij05ek0OKYEPULC6B=aFpQg@mail.gmail.com> <6F428EFD2B8C2F49A2FB1317291A76C113564482A7@USNAVSXCHMBSA1.ndc.alcatel-lucent.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 19 Mar 2012 17:10:48 +0100
Message-ID: <CALiegfmBJ99d=9U0zH5Se2LKAG1vmG2VogLCTmTcuADUUpSnKQ@mail.gmail.com>
To: "Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQm4IAqP8YIWmHvjD/bkS5blKS0JMHbd3gyT0aV6DWc05iTD5/xLySkwHVxxlU54UWuTqUxn
Cc: "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: Mon, 19 Mar 2012 16:11:10 -0000

2012/3/19 Ejzak, Richard P (Richard) <richard.ejzak@alcatel-lucent.com>:
> SRTP by itself guarantees nothing.  What is the point of insisting that the
> browser encrypt media if you know nothing about the other endpoint of the
> encrypted media or even whether anyone else has keys?

If I am at the airport using an open WiFi connection, I visit a web
page using HTTPS and my browser validates the server TLS certificate,
neither I can be sure that the server has not been hacked by
attackers. But at least I know that nobody in the airport can monitor
my HTTPS traffic.

Indeed SRTP by itself guarantees nothing, but if the signaling path is
secured (HTTPS or WebSocket over TLS, so SRTP-SDES becomes a secure
solution) nobody in my network can intercept my media communication.
IMHO that's much better than nothing (plain RTP).

Regards.

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

v2.23.0 | Report a Bug | By Email