Re: [rtcweb] SDES in browser [was: RTCWeb Forking usecase [was: draft-kaplan-rtcweb-sip-interworking-requirements-00]]
Iñaki Baz Castillo <ibc@aliax.net> Sat, 29 October 2011 22:34 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 881F521F8593 for <rtcweb@ietfa.amsl.com>; Sat, 29 Oct 2011 15:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.643
X-Spam-Level:
X-Spam-Status: No, score=-2.643 tagged_above=-999 required=5 tests=[AWL=0.034, 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 dEF4VVV9AEuk for <rtcweb@ietfa.amsl.com>; Sat, 29 Oct 2011 15:34:21 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 083E521F8564 for <rtcweb@ietf.org>; Sat, 29 Oct 2011 15:34:20 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so4953382vcb.31 for <rtcweb@ietf.org>; Sat, 29 Oct 2011 15:34:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.7.12 with SMTP id b12mr1428397vcb.23.1319927660540; Sat, 29 Oct 2011 15:34:20 -0700 (PDT)
Received: by 10.220.184.6 with HTTP; Sat, 29 Oct 2011 15:34:20 -0700 (PDT)
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852234CFC9FF@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A05852234CFC9FF@ESESSCMS0356.eemea.ericsson.se>
Date: Sun, 30 Oct 2011 00:34:20 +0200
Message-ID: <CALiegf==dNDhXdcVqFQAJ2WCLAH3poQDW8juw2s3gR1VJfddxg@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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: Sat, 29 Oct 2011 22:34:21 -0000
2011/10/29 Christer Holmberg <christer.holmberg@ericsson.com>: >> 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ñaki Baz Castillo <ibc@aliax.net>
- Re: [rtcweb] SDES in browser [was: RTCWeb Forking… Christer Holmberg
- [rtcweb] SDES in browser [was: RTCWeb Forking use… Christer Holmberg
- Re: [rtcweb] SDES in browser [was: RTCWeb Forking… Iñaki Baz Castillo