Re: [rtcweb] Consensus call regarding media security

Eric Rescorla <ekr@rtfm.com> Mon, 16 April 2012 11:58 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 91F5F21F86B7 for <rtcweb@ietfa.amsl.com>; Mon, 16 Apr 2012 04:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[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 OLpxt7F+nARM for <rtcweb@ietfa.amsl.com>; Mon, 16 Apr 2012 04:58:26 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id DB3F021F86A8 for <rtcweb@ietf.org>; Mon, 16 Apr 2012 04:58:25 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so3896503vbb.31 for <rtcweb@ietf.org>; Mon, 16 Apr 2012 04:58:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=SEGaHsjcy0r0LxfeEWoqxq3hs4VID1Cw9unkLwjRC3c=; b=K6lFER/ceE1w4UAk/jaxqN6TqSHlaMneY0PLIRDaJ6TQzF63HhOKBmTt2sblu1UTZx JogZKIH336a25ROhjRUP8Pr5MK9qFWCmnClwPwoBbRn8Bn34al0fG4ZHPKilKE/V0YkD DzLx3xkF+vskfEKs5MmjzdrSrFKrma9vbdJwCuuQjBGQypldEo5u7iuTz6X+sMCJ+FEu jz9sYL3p6qcL9/v8Wzf6MuJ0oLVT67CrWtCkTFSnpNInTOeLeZd0iLH9eZ166No1fHz7 BrDhRFP7AcwEoaitOlYOcD0+2jWxAeNJqFciRPBx7cNU6t2KbIASh9Jzh37CqRmZsnuW 7m1A==
Received: by 10.220.153.8 with SMTP id i8mr5834613vcw.73.1334577505365; Mon, 16 Apr 2012 04:58:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.19.233 with HTTP; Mon, 16 Apr 2012 04:57:44 -0700 (PDT)
X-Originating-IP: [66.104.195.130]
In-Reply-To: <4F8BDA2B.3040204@ericsson.com>
References: <4F732531.2030208@ericsson.com> <4F8BDA2B.3040204@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 16 Apr 2012 07:57:44 -0400
Message-ID: <CABcZeBPyrtyyzi1bRVQ1HOKj9pSys63wUPtn56O5n297WDDQOQ@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlpGsSlDrc0pbX/VLPq9ChAK64+p33w+YSHxcLGHurnWUPfCJ9l/h7wOCfK75g37Jc82ayi
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Consensus call regarding media security
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: Mon, 16 Apr 2012 11:58:26 -0000

On Mon, Apr 16, 2012 at 4:36 AM, Magnus Westerlund
<magnus.westerlund@ericsson.com> wrote:
> WG, EKR
>
> The deadline for this call of consensus has ended. I note that there has
> been discussion of a number of details and additional views on the
> actual consensus statement made. Some supporting the consensus from the
> meeting room and some opposing it. In the end I determine that the two
> consensus statements are confirmed:
>
>  The first was that there was overwhelming consensus that all RTP
>  packets SHALL be protected by SRTP.
>
>  Secondly that no one objected against making DTLS-SRTP a mandatory to
>  implement and the default keying mechanism. Additional mechanisms are
>  not precluded.
>
> From the discussion in the thread I would note the following:
>
> 1) Null cipher for encryption is strongly desired but an actual proposal
> is needed for how to express this.
>
> 2) Details of the SRTP and DTLS-SRTP usage in this WG needs to be
> defined. This is for continued discussion. I hope our editor of the
> security architecture can make a proposal to the WG to consider.

Acknowledged.

I will do so.

-Ekr