IETF Logo Mail Archive

Re: [rtcweb] Resolving RTP/SDES question in Paris

Cameron Byrne <cb.list6@gmail.com> Mon, 19 March 2012 15:19 UTC

Return-Path: <cb.list6@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 C727F21F87FB for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 08:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.314
X-Spam-Level:
X-Spam-Status: No, score=-3.314 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 Wssz7eIMZ3wT for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 08:19:11 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id E0C1F21F87F7 for <rtcweb@ietf.org>; Mon, 19 Mar 2012 08:19:10 -0700 (PDT)
Received: by yhkk25 with SMTP id k25so3222325yhk.31 for <rtcweb@ietf.org>; Mon, 19 Mar 2012 08:19:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Js9yXiaDbmyalpAH3WmMX425e99ZByJRFK4qF1OG9O8=; b=A/XzMxTwkzvEmMEu3/ojOr9ZQ8sKw/ibIosU9tt6m2M9HBN3PW7KRT3YRau0n1bZCf QtRx8eOvO+kZeD7JeaAN3HzVWvCtoE9vPihOa6ecIeOxtYPf2lMwVMl4rkfKua1kXdbx xz8xd3WK9xwFKZz5O966QlDz0KUfLSIoYEz1CQIKnAAks8RxZPoV2MSKBNG3mNLDipVi OYwAQ91BsAUCjIEm0pvj7ZROROmOzlhT7wVmHvapN4JzvHRvzOO76uTlGrFE1ZNpR7sv X0UkkG2X+g0gpyipnOcf69cEtYnOjsLwZJZtB7eIZ9+EXSixVJkMn8AgkUr/S1sCYlL0 rtFA==
MIME-Version: 1.0
Received: by 10.68.221.227 with SMTP id qh3mr19549527pbc.43.1332170350107; Mon, 19 Mar 2012 08:19:10 -0700 (PDT)
Received: by 10.143.160.13 with HTTP; Mon, 19 Mar 2012 08:19:09 -0700 (PDT)
Received: by 10.143.160.13 with HTTP; Mon, 19 Mar 2012 08:19:09 -0700 (PDT)
In-Reply-To: <CALiegfk2aT+6Psr4nT-hG1G7eYRBfFCcT+25On2O4HfUXJ6-ng@mail.gmail.com>
References: <4F4759DC.7060303@ericsson.com> <387F9047F55E8C42850AD6B3A7A03C6C0E1FEB69@inba-mail01.sonusnet.com> <CALiegfnkYVEpmPV-zSL_4wOY-HiFZN-qJCQCiioaS=5NaqhLZw@mail.gmail.com> <CAD5OKxvtOAxMBx6xDnyfTnEq76oDEm6uj1xL6wGjjrtKUAHy3g@mail.gmail.com> <CABcZeBNZiotPmCfT53uEo+O0xw4xv6tXW1M_G-3A5BHuncsduA@mail.gmail.com> <CAD5OKxvYOY5JZ2mYNGiH1poUBQkyOOycePFijH5H+SxtcdqujQ@mail.gmail.com> <CABkgnnVe-b6Sv=R67bMJk_NQqQwdrRUn6rBm7Gu_CMcfPQwtEg@mail.gmail.com> <CAD5OKxvZbEJ7sV4WPAYoQapzMR_QwAftj-oKg=ioMKHNT792wQ@mail.gmail.com> <6F428EFD2B8C2F49A2FB1317291A76C113563C5A92@USNAVSXCHMBSA1.ndc.alcatel-lucent.com> <CALiegf=jtkDCS_D0ZFe9UpbiadQ0vsJ+4MppQSbLr-wbaXNrfQ@mail.gmail.com> <BLU169-W29E5B86F9E2C6F3126961C93420@phx.gbl> <CALiegfk2aT+6Psr4nT-hG1G7eYRBfFCcT+25On2O4HfUXJ6-ng@mail.gmail.com>
Date: Mon, 19 Mar 2012 08:19:09 -0700
Message-ID: <CAD6AjGSmi9j+sdGWPts20-iwGvGij05ek0OKYEPULC6B=aFpQg@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Content-Type: multipart/alternative; boundary="e89a8ff255ae7f9c7a04bb9a1443"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Resolving RTP/SDES question in Paris
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: Mon, 19 Mar 2012 15:19:12 -0000

On Mar 19, 2012 5:25 AM, "Iñaki Baz Castillo" <ibc@aliax.net> wrote:
>
> 2012/3/19 Bernard Aboba <bernard_aboba@hotmail.com>:
> > At this point, support for SRTP is an expected feature on legacy
equipment.
> > For example, all the leading PSTN gateway vendors support SRTP
already.  By the time RTCWEB specs are final, SRTP support will be very
prevalent.
>
>
> And if they don't support SRTP then bad luck for them. WebRTC cannot
> be less secure and worse just because some SIP legacy equipments don't
> implement a specification from 2004 (RFC 3711 - SRTP) !!
>
> Please, make WebRTC as secure as possible for common usages in the
> open Internet, rather than decreasing the security just to get
> interoperability with telcos non supporting SRTP.
>

+1, srtp is required

And, it blows my mind this discussion is still going on.

If srtp is not mandatory, it creates a great deal more work for me (a telco
who has customers that expect privacy)

Cb
> --
> Iñaki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email