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

Ted Hardie <ted.ietf@gmail.com> Wed, 04 January 2012 00:02 UTC

Return-Path: <ted.ietf@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 694AA1F0C70 for <rtcweb@ietfa.amsl.com>; Tue, 3 Jan 2012 16:02:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 45BAkaM1hkVT for <rtcweb@ietfa.amsl.com>; Tue, 3 Jan 2012 16:02:59 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id C96E611E80B3 for <rtcweb@ietf.org>; Tue, 3 Jan 2012 16:02:58 -0800 (PST)
Received: by qadz3 with SMTP id z3so10916519qad.10 for <rtcweb@ietf.org>; Tue, 03 Jan 2012 16:02:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zvRNjy6gfnvue3pBOVmSjktqxAhh6N2Z+Wi2JpKSgQM=; b=o+c73AyIR+hMhxYS/cBWNsSDYQDd/5GuL9vs0CbR/R7Nfe9VXRub1RSb6gVEYA73RL 5xqCS1d2vb4PEor1ftGRu6RxsK+8oiXMSdLUYyB6jcTKGOeXMBsY3hPwSOdjtCNa9/We EeMTws3bimDJvW8d2A/kU6aXbq8v3LEnRfk30=
MIME-Version: 1.0
Received: by 10.224.217.10 with SMTP id hk10mr5280920qab.15.1325635378385; Tue, 03 Jan 2012 16:02:58 -0800 (PST)
Received: by 10.229.88.75 with HTTP; Tue, 3 Jan 2012 16:02:58 -0800 (PST)
In-Reply-To: <BLU152-W469B2EB104C104547FC42393960@phx.gbl>
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>
Date: Tue, 03 Jan 2012 16:02:58 -0800
Message-ID: <CA+9kkMBwyUMAdDyQaYZBx0NYvoe3RV+VVKxzqNCC5Ui6xNdsOA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: randell-ietf@jesup.org, rtcweb@ietf.org
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: Wed, 04 Jan 2012 00:02:59 -0000

On Tue, Jan 3, 2012 at 3:08 PM, Bernard Aboba <bernard_aboba@hotmail.com> wrote:
> Justin Uberti said:
>

> Requiring SRTP in all circumstances (e.g. offering RTP/SAVP(F) and not
> falling back or allowing negotiation of RTP/AVP(F)) would not preclude
> gateways from translating to RTP/AVP(F), without user knowledge.
>
> This would result in an illusion of security, compared with an actual
> negotiation which would apprise the user as to whether security is actually
> in place.
>
I'm a little lost.  In a gateway implemented in a back-to-back user
agent, won't you end up with the same
illusion?

The case I think you're talking about is this:

UA--1<-Connection1->B2BUA/Gateway<-Connection-2->UA-2

Do you expect that the gateway would be refuse to use SRTP on one side
if it intended not to use it on the other?  That seems pretty unlikely
to me personally, especially in cases where the gateway is to the PSTN
or a standard SIP system.  Or do you expect that the negotiation would
be extended so that the gateway somehow indicates that it will not
SRTP on side two to side one?

If the requirement is SRTP always for WEBRTC, then a b2bUA would have
to run SRTP on boths ides if both UA-1 and UA-2 were WEBRTC
applications, but that seems to be what we want.

What am I missing?

Ted


>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>