IETF Logo Mail Archive

Re: [rtcweb] SDES in browser [was: RTCWeb Forking usecase [was: draft-kaplan-rtcweb-sip-interworking-requirements-00]]

Christer Holmberg <christer.holmberg@ericsson.com> Sun, 30 October 2011 07:33 UTC

Return-Path: <christer.holmberg@ericsson.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 A4B9321F8551 for <rtcweb@ietfa.amsl.com>; Sun, 30 Oct 2011 00:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.069
X-Spam-Level:
X-Spam-Status: No, score=-6.069 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 fYFcYeAwtyLm for <rtcweb@ietfa.amsl.com>; Sun, 30 Oct 2011 00:33:33 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id DBEC521F854F for <rtcweb@ietf.org>; Sun, 30 Oct 2011 00:33:32 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-8d-4eacfdcbcfa6
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 99.E4.13753.BCDFCAE4; Sun, 30 Oct 2011 08:33:31 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.57]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Sun, 30 Oct 2011 08:33:31 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Date: Sun, 30 Oct 2011 08:32:22 +0100
Thread-Topic: [rtcweb] SDES in browser [was: RTCWeb Forking usecase [was: draft-kaplan-rtcweb-sip-interworking-requirements-00]]
Thread-Index: AcyWiueYZCnkLjiyRpigS1M8tkSE+gASyide
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585223571738D@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A05852234CFC9FF@ESESSCMS0356.eemea.ericsson.se>, <CALiegf==dNDhXdcVqFQAJ2WCLAH3poQDW8juw2s3gR1VJfddxg@mail.gmail.com>
In-Reply-To: <CALiegf==dNDhXdcVqFQAJ2WCLAH3poQDW8juw2s3gR1VJfddxg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] SDES in browser [was: RTCWeb Forking usecase [was: draft-kaplan-rtcweb-sip-interworking-requirements-00]]
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: Sun, 30 Oct 2011 07:33:33 -0000

Hi,

>>> If we want to support SDES for interop with SIP, which I think we do, then what we could do is mandate the Browsers support both SDES and DTLS-SRTP,
>>
>> I am not sure the browser itself would need to support SDES. It may be enough if SDES is implemented in the JavaScript App, the API then allows the App 
>>to provide keys to the browser, and the browser would use those keys for media encryption instead of triggering DTLS-SRPT.
>>
>> And, if the JavaScript App does not provide any keys to the browser, DTLS-SRTP could be used as default.
>
> Note that it would require some kind of standarized JavaScript WebRTC API callback.

I thought API requirements are part of what we are trying to specify :)

Regards,

Christer

v2.23.0 | Report a Bug | By Email