IETF Logo Mail Archive

Re: [rtcweb] Retransmit: Summary of Alternatives for media keying

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 28 July 2011 22:44 UTC

Return-Path: <HKaplan@acmepacket.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 8B1BB21F8BC6 for <rtcweb@ietfa.amsl.com>; Thu, 28 Jul 2011 15:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level:
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TifTTYSdRfFJ for <rtcweb@ietfa.amsl.com>; Thu, 28 Jul 2011 15:44:44 -0700 (PDT)
Received: from ETMail2.acmepacket.com (etmail2.acmepacket.com [216.41.24.9]) by ietfa.amsl.com (Postfix) with ESMTP id 15A7321F8BAE for <rtcweb@ietf.org>; Thu, 28 Jul 2011 15:44:44 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by ETMail2.acmepacket.com (216.41.24.9) with Microsoft SMTP Server (TLS) id 8.1.240.5; Thu, 28 Jul 2011 18:44:42 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Thu, 28 Jul 2011 18:44:41 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Matthew Kaufman <matthew.kaufman@skype.net>
Date: Thu, 28 Jul 2011 18:44:40 -0400
Thread-Topic: [rtcweb] Retransmit: Summary of Alternatives for media keying
Thread-Index: AcxNd++lpPrqtkVhTlO9eGXXsWSGuQ==
Message-ID: <D3161A15-A686-4908-8A85-AACCE1E4FAB8@acmepacket.com>
References: <12BF9E55-662F-4762-9E47-2BBD3FA5FD93@acmepacket.com> <A444A0F8084434499206E78C106220CA08F1D75CF0@MCHP058A.global-ad.net> <2E6CBDE0-DA10-4792-8059-A01F554DB370@skype.net> <E1963869-9E21-4F1F-AB4A-E5D070CCA581@acmepacket.com> <55C78CA7-292C-4E0E-901B-83B7614C2F32@skype.net>
In-Reply-To: <55C78CA7-292C-4E0E-901B-83B7614C2F32@skype.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAUA=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Retransmit: Summary of Alternatives for media keying
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: Thu, 28 Jul 2011 22:44:45 -0000

On Jul 28, 2011, at 1:18 PM, Matthew Kaufman wrote:

> 
> On Jul 28, 2011, at 11:13 AM, Hadriel Kaplan wrote:
> 
>> I would be perfectly happy with using sdes-based SRTP.  But if the call would otherwise fail altogether, I'd like the option to make the call no matter what (ie, even if it ends up being cleartext).
> 
> Why would the call "otherwise fail altogether"?

Because I'm calling someone who has a legacy VoIP device or is on the PSTN, and they're not going to support DTLS-SRTP.
Of course we could require the RTCWEB service to deploy "gateways" in order to terminate DTLS-SRTP and do SDES-based SRTP or cleartext RTP to non-RTCWEB, but that's expensive and complex.  Not to mention its mis-leading - the media is not secure end-to-end, and again the lock-icon model won't work.


> Have you ever called into a conference call from a public place, with your microphone muted?

Nah, I talk too much.  ;)

-hadriel
p.s. Of course I'm speaking as an individual - my employer would probably be ecstatic with requiring such gateways.

v2.23.0 | Report a Bug | By Email