IETF Logo Mail Archive

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

"Kevin P. Fleming" <kpfleming@digium.com> Thu, 05 January 2012 17:07 UTC

Return-Path: <kpfleming@digium.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 50DE421F858A for <rtcweb@ietfa.amsl.com>; Thu, 5 Jan 2012 09:07:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 g2QftBKkddK2 for <rtcweb@ietfa.amsl.com>; Thu, 5 Jan 2012 09:07:19 -0800 (PST)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by ietfa.amsl.com (Postfix) with ESMTP id 12A8521F8589 for <rtcweb@ietf.org>; Thu, 5 Jan 2012 09:07:19 -0800 (PST)
Received: from [10.24.55.203] (helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1Riqmc-0005LU-AU for rtcweb@ietf.org; Thu, 05 Jan 2012 11:07:18 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 47F95D8005 for <rtcweb@ietf.org>; Thu, 5 Jan 2012 11:07:18 -0600 (CST)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6eV0ZcacHDUG for <rtcweb@ietf.org>; Thu, 5 Jan 2012 11:07:17 -0600 (CST)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id BC2D7D8002 for <rtcweb@ietf.org>; Thu, 5 Jan 2012 11:07:17 -0600 (CST)
Message-ID: <4F05D8C5.10806@digium.com>
Date: Thu, 05 Jan 2012 11:07:17 -0600
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAErhfrwu322=HTS0JZhum9EGfb73KmYS6CU_KMESyzEWhtvg2w@mail.gmail.com> <CABcZeBOeg-O+6===5tk0haxC8nLxUQyEUFRES2FAoFEf00fKng@mail.gmail.com> <CAErhfrxTKdo7Z+61x5ZcDt5ZM7C7ob5LNxMzwng_kk3Uqrp2_Q@mail.gmail.com> <4F01A790.4060704@alvestrand.no> <4F02A061.60905@jesup.org> <E44893DD4E290745BB608EB23FDDB762141EF8@008-AM1MPN1-042.mgdnok.nokia.com> <4F035DD5.3050305@jesup.org> <CAOJ7v-1dziaA_ePCuMxjn6uhBgOH=ZVybUmLBwQi5qiuyOzDMA@mail.gmail.com> <BLU152-W469B2EB104C104547FC42393960@phx.gbl> <CAD5OKxuE0VhSsjKggj1mLOseLeDXarujvAG44yHkuZttagJggw@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>
In-Reply-To: <4AEFFC17-EF17-40F2-B83B-0B0CC44AD2C3@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Thu, 05 Jan 2012 17:07:20 -0000

On 01/05/2012 10:56 AM, Cullen Jennings wrote:
>
> On Jan 4, 2012, at 8:36 PM, Justin Uberti wrote:
>
>>
>> This argument about debugging keeps coming up, and although I am not persuaded by this argument, it is not a completely unreasonable request. However, I don't think this needs to be controllable from JS. One could easily imagine a plain-RTP option being available from a developer options dialog or console, for use by developers in debugging specific problems with their service.
>> _______________________________________________
>
> I think the best solution for the debugging issue is to allow SRTP to negotiate a NULL cipher in special cases such as Justin described above. This keeps what you are debugging as close as possible to the version when debugging is turned off. I like Justin's idea of having to enable this in the browser and not having it under JS control.

+1, unless I get more votes, in which case +all-of-my-votes

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org

v2.23.0 | Report a Bug | By Email