Re: [rtcweb] AVPF [was: Encryption mandate (and offer/answer)]

"Timothy B. Terriberry" <tterriberry@mozilla.com> Sun, 11 September 2011 13:37 UTC

Return-Path: <prvs=228ffc744=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 C890B21F85E3 for <rtcweb@ietfa.amsl.com>; Sun, 11 Sep 2011 06:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level:
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 GWymamlITp6j for <rtcweb@ietfa.amsl.com>; Sun, 11 Sep 2011 06:37:07 -0700 (PDT)
Received: from mxip2i.isis.unc.edu (mxip2i.isis.unc.edu [152.2.2.193]) by ietfa.amsl.com (Postfix) with ESMTP id 3C89121F85C4 for <rtcweb@ietf.org>; Sun, 11 Sep 2011 06:37:06 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAGu5bE6sGgRS/2dsb2JhbABBpx2BdIFSAQEFOEABEAshFg8JAwIBAgFFEwEHAr0khm4Eh22QVRCMJw
X-IronPort-AV: E=Sophos;i="4.67,504,1309752000"; d="scan'208";a="183571524"
Received: from mr1a.isis.unc.edu (HELO smtp.unc.edu) ([172.26.4.82]) by mxip2o.isis.unc.edu with ESMTP; 11 Sep 2011 09:39:06 -0400
X-UNC-Auth-As: tterribe
X-UNC-Auth-IP: 24.103.99.21
Received: from [172.26.0.112] (rrcs-24-103-99-21.nyc.biz.rr.com [24.103.99.21]) (authenticated bits=0) by smtp.unc.edu (8.14.4/8.14.3) with ESMTP id p8BDd3Uk017451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rtcweb@ietf.org>; Sun, 11 Sep 2011 09:39:06 -0400 (EDT)
Message-ID: <4E6CB9F7.2060208@mozilla.com>
Date: Sun, 11 Sep 2011 06:39:03 -0700
From: "Timothy B. Terriberry" <tterriberry@mozilla.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101120 Gentoo/2.0.10 SeaMonkey/2.0.10
MIME-Version: 1.0
CC: "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <A444A0F8084434499206E78C106220CA0B00FDB08B@MCHP058A.global-ad.net> <033458F56EC2A64E8D2D7B759FA3E7E7020E64DC@sonusmail04.sonusnet.com> <E4EC1B17-0CC4-4F79-96DD-84E589FCC4F0@edvina.net> <4E67C3F7.7020304@jesup.org> <BE60FA11-8FFF-48E5-9F83-4D84A7FBE2BE@vidyo.com> <4E67F003.6000108@jesup.org> <7F2072F1E0DE894DA4B517B93C6A05852233E8554C@ESESSCMS0356.eemea.ericsson.se> <C3759687E4991243A1A0BD44EAC8230339CA68F054@BE235.mail.lan> <CAOJ7v-2u0UuNXh7bzmZFwiSucbsh=Ps=C3ZM5M3cJrXRmZgODA@mail.gmail.com> <CAKhHsXHXCkNdjtpxCSCk+ABbtxY15GEgouE6X6-sn-LqhnidQw@mail.gmail.com> <4E6A56D4.2030602@skype.net> <CABcZeBOdP6cAqBoiSV-Vdv1_EK3DfgnMamT3t3ccjDOMfELfBw@mail.gmail.com> <CAKhHsXFdU1ZaKQF8hbsOxwTS-_RfmFqQhgzGe=K4mRp+wz+_nQ@mail.gmail.com> <4E6A81EC.3080002@jesup.org>, <4E6AE22A.2070106@alum.mit.edu> <7F2072F1E0DE894DA4B517B93C6A05852233C3B7C5@ESESSCMS0356.eemea.ericsson.se>, <4E6C16FF.1000706@jesup.org> <BBF498F2D030E84AB1179E24D1AC41D61C1BCA829D@ESESSCMS0362.eemea.ericsson.se>
In-Reply-To: <BBF498F2D030E84AB1179E24D1AC41D61C1BCA829D@ESESSCMS0362.eemea.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] AVPF [was: Encryption mandate (and offer/answer)]
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: Sun, 11 Sep 2011 13:37:07 -0000

> * The level of media protection to use (NONE, SDES-SRTP or DTLS-SRTP) should be set by the web app

Why wouldn't this devolve to, "Don't communicate anything. Instead, try 
to create a PeerConnection with DTLS-SRTP, and when that fails, try to 
create a second one with NONE," in the actual webapp.

Or, more likely, since NONE will have a better chance of working with 
legacy devices, "Try to create a PeerConnection with NONE, and when that 
fails, try to create a second one with DTLS-SRTP." Assuming anyone 
bothers with the second step. Having the choice of SDES-SRTP or 
DTLS-SRTP will also make it more likely people won't bother with either, 
as they won't know which one to use. We can try to create incentives 
with browser chrome, but there's only so much that can do.