[rtcweb] SRTP not mandatory-to-use

Xavier Marjou <xavier.marjou@gmail.com> Wed, 14 December 2011 09:48 UTC

Return-Path: <xavier.marjou@gmail.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 C4D2621F8B1F for <rtcweb@ietfa.amsl.com>; Wed, 14 Dec 2011 01:48:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 ooFx7eGsqslp for <rtcweb@ietfa.amsl.com>; Wed, 14 Dec 2011 01:48:15 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4670521F8B00 for <rtcweb@ietf.org>; Wed, 14 Dec 2011 01:48:15 -0800 (PST)
Received: by yhjj72 with SMTP id j72so1322131yhj.31 for <rtcweb@ietf.org>; Wed, 14 Dec 2011 01:48:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=VL31peBGvpeCjQCZjWzYL7pJmExS7TEpdT9aFqKmlKg=; b=JFWXQ0vvgA+hcXI0Cslk36T+3JjKIQpp0u3fALn6e0UNnXvcopLXxWG4n0IzdGPDaS cDlqYVn3tpQpe7u3FenN88m/l7cy5G21IH5NEuolYbCxmSIJRkK3OArWjYeP1LM6/4eT SrYWizXb+0b+hzVXTuTDVu4owEOyPO+kFNuv8=
MIME-Version: 1.0
Received: by 10.236.197.97 with SMTP id s61mr10533751yhn.57.1323856094797; Wed, 14 Dec 2011 01:48:14 -0800 (PST)
Received: by 10.236.180.230 with HTTP; Wed, 14 Dec 2011 01:48:14 -0800 (PST)
Date: Wed, 14 Dec 2011 10:48:14 +0100
Message-ID: <CAErhfrwu322=HTS0JZhum9EGfb73KmYS6CU_KMESyzEWhtvg2w@mail.gmail.com>
From: Xavier Marjou <xavier.marjou@gmail.com>
To: rtcweb@ietf.org
Content-Type: multipart/alternative; boundary="20cf3040ec2c439f8504b40a4428"
Subject: [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, 14 Dec 2011 09:48:15 -0000

Hi,


During the last IETF meeting, there seemed to be many people willing to
have SRTP mandatory-to-use in the browser. However, I would like again to
underline that in some contexts, it is rather desirable to deactivate, via
the WebRTC API, the use of SRTP in order not to encrypt/decrypt at multiple
layers.


This may be the case in the following example: a company wants to use
WebRTC for communications between its co-workers only; the web server and
the script using WebRTC API are located on the VPN. In such a case, there
is no need to use SRTP. The VPN already provides encryption when needed. If
co-workers want to remotely access the VPN, an IPsec tool can already
provide the encryption. Furthermore, if they want to remotely access the
VPN via a 3G network, there will be encryption at layer 2 using AKA, then
IPsec at layer 3, and again at SRTP level if mandatory-to-use.


Cheers,

Xavier