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

Mandeep Singh <Mandeep.Singh@mavenir.com> Thu, 25 April 2013 22:19 UTC

Return-Path: <Mandeep.Singh@mavenir.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 0C70D21F96C4 for <rtcweb@ietfa.amsl.com>; Thu, 25 Apr 2013 15:19:13 -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 HeIo0eXRzQgr for <rtcweb@ietfa.amsl.com>; Thu, 25 Apr 2013 15:19:12 -0700 (PDT)
Received: from HUB024-nj-6.exch024.serverdata.net (hub024-nj-6.exch024.serverdata.net [206.225.165.112]) by ietfa.amsl.com (Postfix) with ESMTP id 73A4621F96BC for <rtcweb@ietf.org>; Thu, 25 Apr 2013 15:19:12 -0700 (PDT)
Received: from MBX024-E1-NJ-2.exch024.domain.local ([10.240.10.52]) by HUB024-NJ-6.exch024.domain.local ([10.240.10.45]) with mapi id 14.02.0318.001; Thu, 25 Apr 2013 15:19:11 -0700
From: Mandeep Singh <Mandeep.Singh@mavenir.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb
Thread-Index: AQHOQc2ZUXUTsDVm60WY+suOGgC17pjnmKcAgAAZgwD//83vsA==
Date: Thu, 25 Apr 2013 22:19:11 +0000
Message-ID: <26ADD8827FF29046B2E32AE632033BC41804B1EB@mbx024-e1-nj-2.exch024.domain.local>
References: <3FA2E46D-C98E-4FC0-9F1D-AD595A861CE1@iii.ca> <74300615-2293-4DCE-82A7-475F1A5A8256@gmail.com> <BLU403-EAS26AEAA12D3F5499858D8EA93B60@phx.gbl>
In-Reply-To: <BLU403-EAS26AEAA12D3F5499858D8EA93B60@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [38.122.186.90]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 22:19:13 -0000

I believe SDES (besides DTLS-SRTP) is good idea for backward compatibility and interoperability reason.
However for browser to browser communication, DTLS-SRTP should be preferred.

Mandeep Singh

-----Original Message-----
> 
> On Apr 25, 2013, at 11:57 AM, Cullen Jennings <fluffy@iii.ca> wrote:
> 
>> 
>> 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
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb