Re: [rtcweb] Consensus call regarding media security

"Timothy B. Terriberry" <tterriberry@mozilla.com> Wed, 28 March 2012 18:30 UTC

Return-Path: <tterriberry@mozilla.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 2039221E80F1 for <rtcweb@ietfa.amsl.com>; Wed, 28 Mar 2012 11:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_56=0.6, 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 Zk050a8rZJm6 for <rtcweb@ietfa.amsl.com>; Wed, 28 Mar 2012 11:30:09 -0700 (PDT)
Received: from dm-mail03.mozilla.org (dm-mail03.mozilla.org [63.245.208.213]) by ietfa.amsl.com (Postfix) with ESMTP id 9BD5E21E8040 for <rtcweb@ietf.org>; Wed, 28 Mar 2012 11:30:09 -0700 (PDT)
Received: from [130.129.69.85] (dhcp-4555.meeting.ietf.org [130.129.69.85]) (Authenticated sender: tterriberry@mozilla.com) by dm-mail03.mozilla.org (Postfix) with ESMTP id 271B44AED56 for <rtcweb@ietf.org>; Wed, 28 Mar 2012 11:30:07 -0700 (PDT)
Message-ID: <4F7358AE.4040006@mozilla.com>
Date: Wed, 28 Mar 2012 11:30:06 -0700
From: "Timothy B. Terriberry" <tterriberry@mozilla.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20120113 SeaMonkey/2.4.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <4F732531.2030208@ericsson.com> <CAD5OKxs6NHha2egNSTumEaHYJ0bB6qu_nfshmBM6dntx2n49HQ@mail.gmail.com> <4F733492.9040601@alcatel-lucent.com> <91F0E66E-A75E-4369-A010-9712FF90258D@acmepacket.com>
In-Reply-To: <91F0E66E-A75E-4369-A010-9712FF90258D@acmepacket.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Wed, 28 Mar 2012 18:30:10 -0000

Hadriel Kaplan wrote:
>
> Actually, I was confused about that - it seems to me it's still an open
> item whether to allow null cipher or not.

As a browser vendor, I could see adding an about:config option to enable 
the null cipher for debugging purposes, but would expect that for the 
vast majority of users it will never be allowed.