IETF Logo Mail Archive

Re: [rtcweb] Question about srtp_mki in DTLS/SRTP

Simon Perreault <sperreault@jive.com> Wed, 14 January 2015 15:08 UTC

Return-Path: <sperreault@jive.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 139711A8859 for <rtcweb@ietfa.amsl.com>; Wed, 14 Jan 2015 07:08:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N8jhGxXPCpna for <rtcweb@ietfa.amsl.com>; Wed, 14 Jan 2015 07:08:12 -0800 (PST)
Received: from mail-la0-f42.google.com (mail-la0-f42.google.com [209.85.215.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F3FC1A6F0A for <rtcweb@ietf.org>; Wed, 14 Jan 2015 07:08:02 -0800 (PST)
Received: by mail-la0-f42.google.com with SMTP id gd6so8631532lab.1 for <rtcweb@ietf.org>; Wed, 14 Jan 2015 07:08:01 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=s30LPFAgdYQEyPppGcTBGOpBBhoqefhrTts4aBZxJJk=; b=OX61XURZfIdrCntx4pBa4SsTavLjm/VJxhgZVTTgMxGjZIuHONsbBXQHMKV3t7mm7Z C6UrlVgRcHR04E7vCXVFEe2xqKfU/hvhtDyvJzYeafnoxgoeDxIRBP1xjeZa8tK0aoqi zGIUcWNYRSX3Snr/ETyzhx0woTyJxp8Awb96QxLgOaJbj5IQFM+jkRXmYBK2NXgrQ/B3 Yco7v6iQ2Py5efqMHrH/hwo25swYt3oUXlVDYW2GQ6xSWKMdlgaQi/Wg5IpYFf4lJnGj wPYIvOjDKX237uuiJoXWBuq9RtbV8WbgBLKPsMu58y627NDD8hiSGzGJ8TMdEj0UwZdY kAig==
X-Gm-Message-State: ALoCoQn232pP2Mvsq/YcQHxevGyZkVEFC/Ippl/zZ1TnLpTqYLEk6MqDUdMH32968oEI5v+61caU
MIME-Version: 1.0
X-Received: by 10.152.8.11 with SMTP id n11mr4401974laa.38.1421248080915; Wed, 14 Jan 2015 07:08:00 -0800 (PST)
Received: by 10.25.84.145 with HTTP; Wed, 14 Jan 2015 07:08:00 -0800 (PST)
In-Reply-To: <CAOW+2dvhEzAfyV51p1YWZoc41vih3TKhoArq3CGXzHvSdHEdcA@mail.gmail.com>
References: <CAOW+2dvhEzAfyV51p1YWZoc41vih3TKhoArq3CGXzHvSdHEdcA@mail.gmail.com>
Date: Wed, 14 Jan 2015 10:08:00 -0500
Message-ID: <CANO7kWBjs4AwyTXXhOBSDqG=y9ThM=XkLyO_S1xPe3naL9za_Q@mail.gmail.com>
From: Simon Perreault <sperreault@jive.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c366e2004561050c9e1b28"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/BeWE5bz4FZqlK_Uf-czndN-eWbA>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Question about srtp_mki in DTLS/SRTP
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 14 Jan 2015 15:08:14 -0000

On Tue, Jan 13, 2015 at 7:48 PM, Bernard Aboba <bernard.aboba@gmail.com>
wrote:

> Do existing WebRTC implementations have the capability to receive or send with the SRTP MKI field (e.g. if the peer implementation requests it?)
>
>
Mine doesn't because OpenSSL doesn't support srtp_mki negotiation.

Do existing WebRTC implementations indicate a desire to use the SRTP MKI field?
>
>
I would much prefer to use MKI because otherwise re-handshake is very
complex and brittle. I did implement re-handshake, which is uncommon.

Simon

v2.23.0 | Report a Bug | By Email