IETF Logo Mail Archive

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

Eric Rescorla <ekr@rtfm.com> Wed, 11 January 2012 23:25 UTC

Return-Path: <ekr@rtfm.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 3A83A21F854A for <rtcweb@ietfa.amsl.com>; Wed, 11 Jan 2012 15:25:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.752
X-Spam-Level:
X-Spam-Status: No, score=-102.752 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 Byzz23BK0yL5 for <rtcweb@ietfa.amsl.com>; Wed, 11 Jan 2012 15:25:56 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id AB10F21F8543 for <rtcweb@ietf.org>; Wed, 11 Jan 2012 15:25:56 -0800 (PST)
Received: by vbbfo1 with SMTP id fo1so1060267vbb.31 for <rtcweb@ietf.org>; Wed, 11 Jan 2012 15:25:56 -0800 (PST)
Received: by 10.52.29.228 with SMTP id n4mr656586vdh.57.1326324356208; Wed, 11 Jan 2012 15:25:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.185.227 with HTTP; Wed, 11 Jan 2012 15:25:14 -0800 (PST)
X-Originating-IP: [74.95.2.173]
In-Reply-To: <CAD5OKxsFjj0cYHfaefODstoRXme=gSRJArFbMuB_r+q6WyBTiQ@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> <CAD5OKxsFjj0cYHfaefODstoRXme=gSRJArFbMuB_r+q6WyBTiQ@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 11 Jan 2012 15:25:14 -0800
Message-ID: <CABcZeBMU18m9hkw6y6qYeUPeufHWkCLea4V3JbvUUuMgwdXJOQ@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset="ISO-8859-1"
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:25:57 -0000

On Wed, Jan 11, 2012 at 3:22 PM, Roman Shpount <roman@telurix.com> wrote:
>
> 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?

The requirements in RFC 5246 (DTLS inherits these) and 3711 should be
sufficient to ensure interop. If they're not, I don't see a problem with adding
some more.

-Ekr

v2.23.0 | Report a Bug | By Email