[rtcweb] SDES in browser [was: RTCWeb Forking usecase [was: draft-kaplan-rtcweb-sip-interworking-requirements-00]]
Christer Holmberg <christer.holmberg@ericsson.com> Sat, 29 October 2011 21:43 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 B304021F86A6 for <rtcweb@ietfa.amsl.com>; Sat, 29 Oct 2011 14:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.205
X-Spam-Level:
X-Spam-Status: No, score=-6.205 tagged_above=-999 required=5 tests=[AWL=0.394, 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 trOZ1Lw3IRwt for <rtcweb@ietfa.amsl.com>; Sat, 29 Oct 2011 14:43:30 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 0847921F8610 for <rtcweb@ietf.org>; Sat, 29 Oct 2011 14:43:29 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-1f-4eac73809da3
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id AA.87.20773.1837CAE4; Sat, 29 Oct 2011 23:43:29 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.2.197]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Sat, 29 Oct 2011 23:43:28 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, Harald Alvestrand <harald@alvestrand.no>
Date: Sat, 29 Oct 2011 23:43:28 +0200
Thread-Topic: SDES in browser [was: RTCWeb Forking usecase [was: draft-kaplan-rtcweb-sip-interworking-requirements-00]]
Thread-Index: AQHMloPLAoM+L3n8+0Cq94atygftSg==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852234CFC9FF@ESESSCMS0356.eemea.ericsson.se>
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: AAAAAA==
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: [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 21:43:30 -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. Regards, Christer
- 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