Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb

"Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net> Thu, 25 April 2013 20:28 UTC

Return-Path: <matthew.kaufman@skype.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 4ABD921F93F0 for <rtcweb@ietfa.amsl.com>; Thu, 25 Apr 2013 13:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
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 YOeIFzMeHzPj for <rtcweb@ietfa.amsl.com>; Thu, 25 Apr 2013 13:28:04 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id E03E721F93B9 for <rtcweb@ietf.org>; Thu, 25 Apr 2013 13:28:03 -0700 (PDT)
Received: from BN1BFFO11FD022.protection.gbl (10.58.52.201) by BN1AFFO11HUB032.protection.gbl (10.58.52.142) with Microsoft SMTP Server (TLS) id 15.0.675.0; Thu, 25 Apr 2013 20:28:01 +0000
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD022.mail.protection.outlook.com (10.58.53.82) with Microsoft SMTP Server (TLS) id 15.0.675.0 via Frontend Transport; Thu, 25 Apr 2013 20:28:01 +0000
Received: from TK5EX14MBXC272.redmond.corp.microsoft.com ([169.254.2.242]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.02.0318.003; Thu, 25 Apr 2013 20:27:52 +0000
From: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
To: "Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com>, 'Cullen Jennings' <fluffy@iii.ca>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb
Thread-Index: AQHOQc2XfQPA+8NP/kG64CStJCaibJjnYRuAgAABw+A=
Date: Thu, 25 Apr 2013 20:27:51 +0000
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A48416281FDB@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <3FA2E46D-C98E-4FC0-9F1D-AD595A861CE1@iii.ca> <20130425202238.74EF321F96A5@ietfa.amsl.com>
In-Reply-To: <20130425202238.74EF321F96A5@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(13464002)(51704004)(377454001)(81542001)(74366001)(16406001)(47446002)(77982001)(65816001)(55846006)(46102001)(69226001)(49866001)(31966008)(56816002)(80022001)(6806003)(50466002)(20776003)(63696002)(33656001)(81342001)(74662001)(51856001)(46406003)(54316002)(47776003)(23726002)(4396001)(47976001)(74502001)(54356001)(56776001)(66066001)(76482001)(47736001)(59766001)(79102001)(50986001)(53806001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB032; H:TK5EX14HUBC104.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0827D7ACB9
Subject: Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb
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, 25 Apr 2013 20:28:05 -0000

I agree. The ability to set the cipher suite and keys from JavaScript is critical for certain applications. SDES is the best we'll get with SDP as the API. DTLS-SRTP-only would be unacceptably limiting.

Matthew Kaufman

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Bogineni, Kalyani
> Sent: Thursday, April 25, 2013 1:21 PM
> To: 'Cullen Jennings'; rtcweb@ietf.org
> Subject: Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb
> 
> We would like to support the use of SDES as a keying method for WebRTC.
> 
> Kalyani Bogineni
> Verizon
> 
> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Cullen Jennings
> Sent: Thursday, April 25, 2013 11:57 AM
> To: rtcweb@ietf.org
> Subject: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb
> 
> 
> The working groups committed some time ago to have a further discussion
> on whether SDP Security Descriptions (RFC 4568 aka SDES) would be usable
> as a keying method for WebRTC.  As we prepare for that discussion, we'd like
> to have expressions of interest or support for that approach which indicate
> the general outlines of support proposed.  If you wish to make such an
> expression of support, please send it to the chairs or the list.
> 
> Cullen, Magnus, & Ted <The Chairs>
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb