IETF Logo Mail Archive

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

<Markus.Isomaki@nokia.com> Sun, 28 April 2013 19:39 UTC

Return-Path: <Markus.Isomaki@nokia.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 BA41D21F97C5 for <rtcweb@ietfa.amsl.com>; Sun, 28 Apr 2013 12:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 Vg50ewcivymC for <rtcweb@ietfa.amsl.com>; Sun, 28 Apr 2013 12:39:07 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id E8DC021F9763 for <rtcweb@ietf.org>; Sun, 28 Apr 2013 12:39:06 -0700 (PDT)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r3SJd1Hf029027; Sun, 28 Apr 2013 22:39:02 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.61]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Sun, 28 Apr 2013 22:39:01 +0300
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([169.254.2.144]) by 008-AM1MMR1-006.mgdnok.nokia.com ([65.54.30.61]) with mapi id 14.02.0328.011; Sun, 28 Apr 2013 19:39:01 +0000
From: Markus.Isomaki@nokia.com
To: fluffy@iii.ca, rtcweb@ietf.org
Thread-Topic: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb
Thread-Index: AQHOQc2aZhag0IkaJUuPrNdkYnKmoJjsC0EQ
Date: Sun, 28 Apr 2013 19:39:00 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB76209FCF238@008-AM1MPN1-042.mgdnok.nokia.com>
References: <3FA2E46D-C98E-4FC0-9F1D-AD595A861CE1@iii.ca>
In-Reply-To: <3FA2E46D-C98E-4FC0-9F1D-AD595A861CE1@iii.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Nokia Internal Use Only; Project=None;
x-titus-version: 3.5.9.3
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7Ik3QeNEccZVB3Vc5WJiRQg5/fip2jlWgACI+jRRjlOwkIu/5buv39veohDwU6hwGZw9EBm4YHEofpTn7XF45mSMfkOeYrxBwvTl+gSohzIRKIZD0NNsKGoEaB/e09ZsMFB/jxGH0e+k4nqZ8ekJ+OAShcpPjImUB2UzpKLUeKFecgIEVUew0+eeJhTamkthp50N9QIoW/1N940fyU+c5wzIHPhWO8s8uieP0+1vjT24p/FblDSYtIA2GugMLd6ZfJg==
x-originating-ip: [10.163.26.232]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 28 Apr 2013 19:39:01.0892 (UTC) FILETIME=[08F4D440:01CE4448]
X-Nokia-AV: Clean
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: Sun, 28 Apr 2013 19:39:07 -0000

Hi,

I prefer having SDES as a possible keying method for WebRTC, mainly for easier interop with non-WebRTC systems. I see a lot of people working on that type of use cases, i.e. a "browser client access" to an existing communication service. 

Markus 

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of ext Cullen Jennings
Sent: 25 April, 2013 18:57
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

v2.23.0 | Report a Bug | By Email