IETF Logo Mail Archive

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

"Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com> Mon, 19 March 2012 16:03 UTC

Return-Path: <richard.ejzak@alcatel-lucent.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 274BC21F8890 for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 09:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.686
X-Spam-Level:
X-Spam-Status: No, score=-8.686 tagged_above=-999 required=5 tests=[AWL=1.612, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
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 CQnaVRcalf2l for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 09:03:13 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id EDF9E21F8887 for <rtcweb@ietf.org>; Mon, 19 Mar 2012 09:03:12 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q2JG3AJ2024059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 19 Mar 2012 11:03:10 -0500 (CDT)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q2JG3AuI025040 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 19 Mar 2012 11:03:10 -0500
Received: from USNAVSXCHMBSA1.ndc.alcatel-lucent.com ([135.3.39.127]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Mon, 19 Mar 2012 11:03:10 -0500
From: "Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com>
To: Cameron Byrne <cb.list6@gmail.com>, Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 19 Mar 2012 11:03:09 -0500
Thread-Topic: [rtcweb] Resolving RTP/SDES question in Paris
Thread-Index: Ac0F46Wj7l5CR0OSSV6mC0hpo4H6fQABeNoA
Message-ID: <6F428EFD2B8C2F49A2FB1317291A76C113564482A7@USNAVSXCHMBSA1.ndc.alcatel-lucent.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> <CAD6AjGSmi9j+sdGWPts20-iwGvGij05ek0OKYEPULC6B=aFpQg@mail.gmail.com>
In-Reply-To: <CAD6AjGSmi9j+sdGWPts20-iwGvGij05ek0OKYEPULC6B=aFpQg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_6F428EFD2B8C2F49A2FB1317291A76C113564482A7USNAVSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: "rtcweb@ietf.org" <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 16:03:14 -0000

SRTP by itself guarantees nothing.  What is the point of insisting that the browser encrypt media if you know nothing about the other endpoint of the encrypted media or even whether anyone else has keys?

Richard

________________________________
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Cameron Byrne
Sent: Monday, March 19, 2012 10:19 AM
To: Iñaki Baz Castillo
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Resolving RTP/SDES question in Paris


On Mar 19, 2012 5:25 AM, "Iñaki Baz Castillo" <ibc@aliax.net<mailto:ibc@aliax.net>> wrote:
>
> 2012/3/19 Bernard Aboba <bernard_aboba@hotmail.com<mailto: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<mailto:ibc@aliax.net>>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org<mailto:rtcweb@ietf.org>
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email