IETF Logo Mail Archive

Re: [rtcweb] SRTP not mandatory-to-use

Roman Shpount <roman@telurix.com> Wed, 11 January 2012 23:22 UTC

Return-Path: <roman@telurix.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 93FD021F8532 for <rtcweb@ietfa.amsl.com>; Wed, 11 Jan 2012 15:22:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 6fh+HSzTMvgc for <rtcweb@ietfa.amsl.com>; Wed, 11 Jan 2012 15:22:36 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA2621F8531 for <rtcweb@ietf.org>; Wed, 11 Jan 2012 15:22:36 -0800 (PST)
Received: by iaae16 with SMTP id e16so1599906iaa.31 for <rtcweb@ietf.org>; Wed, 11 Jan 2012 15:22:35 -0800 (PST)
Received: by 10.42.150.6 with SMTP id y6mr1117825icv.14.1326324155450; Wed, 11 Jan 2012 15:22:35 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by mx.google.com with ESMTPS id r5sm5255378igl.3.2012.01.11.15.22.34 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 Jan 2012 15:22:34 -0800 (PST)
Received: by pbdd12 with SMTP id d12so1036341pbd.31 for <rtcweb@ietf.org>; Wed, 11 Jan 2012 15:22:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.192.71 with SMTP id he7mr3391511pbc.17.1326324153637; Wed, 11 Jan 2012 15:22:33 -0800 (PST)
Received: by 10.68.44.197 with HTTP; Wed, 11 Jan 2012 15:22:33 -0800 (PST)
In-Reply-To: <CAOJ7v-2Y3SLYko1r_BTp-8B2ea-L+7y9CRsVAc-RkYU9hWvQ_Q@mail.gmail.com>
References: <CAErhfrwu322=HTS0JZhum9EGfb73KmYS6CU_KMESyzEWhtvg2w@mail.gmail.com> <CAKhHsXHnT2p7yncha5-BQ=-Lzk3-N+tuijM-UqwfP1mPUi173A@mail.gmail.com> <BLU152-W1140980759D89AC3C1D0CA93940@phx.gbl> <CA+9kkMBdX7YT1tPj5M3VrzAPKa6tXNGZVvvhjW9V4oOEC7g_kA@mail.gmail.com> <CAOJ7v-1_qMoHBb3K7rV=hG9EadqL=xn4KEdG0zdWnKZU9_TipQ@mail.gmail.com> <4AEFFC17-EF17-40F2-B83B-0B0CC44AD2C3@cisco.com> <CAKhHsXEes+Lf+uKdTrjXoy+3PMy2uNumNL-W-0s4_xRXW6FiZg@mail.gmail.com> <4F0CAC8C.8010203@wonderhamster.org> <1D062974A4845E4D8A343C6538049202074ABD3A@XMB-BGL-414.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01DCF907@inba-mail02.sonusnet.com> <CALiegfkejnU2rTe-FibUVxTrRS9SivkhGXB5eK+FhD8Vu6iTMA@mail.gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01DCF9FC@inba-mail02.sonusnet.com> <CALiegfn07bS58B+4ZyzRTnO4LCpw1e96dnqpSM+TT1y3QG2Zwg@mail.gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01DCFBC1@inba-mail02.sonusnet.com> <CAOJ7v-20+yL7r+_ODx_czHTiujXZZWESaZRB7MQjhvScg3RFtw@mail.gmail.com> <4F0DFD0B.2000009@jesup.org> <CAD5OKxsOqzXDz3WYhLejDtB-zGUcZYMCApHxPyU3XV++_RZhBg@mail.gmail.com> <CAOJ7v-2Y3SLYko1r_BTp-8B2ea-L+7y9CRsVAc-RkYU9hWvQ_Q@mail.gmail.com>
Date: Wed, 11 Jan 2012 18:22:33 -0500
Message-ID: <CAD5OKxsFjj0cYHfaefODstoRXme=gSRJArFbMuB_r+q6WyBTiQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Justin Uberti <juberti@google.com>
Content-Type: multipart/alternative; boundary="e89a8fb2091208dc0b04b648e898"
Cc: Randell Jesup <randell-ietf@jesup.org>, rtcweb@ietf.org
Subject: Re: [rtcweb] SRTP not mandatory-to-use
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: Wed, 11 Jan 2012 23:22:36 -0000

On Wed, Jan 11, 2012 at 6:17 PM, Justin Uberti <juberti@google.com> wrote:

> When used with JSEP, DTLS should not require any additional roundtrips for
> connection setup, since DTLS can be brought up as part of transport
> establishment. In fact, connection setup should occur faster than when
> using SDES, since the keys can be negotiated before the answer arrives.
> This prevents clipping of the answerer's media from occurring.
>

Should we provide some sort of best practice document on DTLS-SRTP
implementation? Should we mandate a minimal set of DTLS features that
should be supported to enable WebRTC interop?
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email