Re: [rtcweb] Final plea about SRTP
Roman Shpount <roman@telurix.com> Fri, 04 May 2012 16:41 UTC
Return-Path: <roman@telurix.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 4899521F85D5 for <rtcweb@ietfa.amsl.com>; Fri, 4 May 2012 09:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.873
X-Spam-Level:
X-Spam-Status: No, score=-2.873 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 phNIh1GEvSn5 for <rtcweb@ietfa.amsl.com>; Fri, 4 May 2012 09:41:18 -0700 (PDT)
Received: from mail-pz0-f52.google.com (mail-pz0-f52.google.com [209.85.210.52]) by ietfa.amsl.com (Postfix) with ESMTP id BA1C221F85D1 for <rtcweb@ietf.org>; Fri, 4 May 2012 09:41:18 -0700 (PDT)
Received: by dadz9 with SMTP id z9so4847315dad.39 for <rtcweb@ietf.org>; Fri, 04 May 2012 09:41:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=mjVHUYx8oVE+g3jYVfD4yHvSzdS8x9kZCnqiISjLk6o=; b=Kziy5m4VMt1FOq5GXISShPr8iPR7Yh1qu1ZTxyXD7RgBE0ET6pjD5gFEeUdN1t1FF4 NmIM5F1yVIIADbKRlSoYAo5fec/QIqUjiGn4QlfPQGFkH/tjgseNhCHCM5iHOGigqUv6 U778i06BqIx38ckcOxoX6HmRiRCNonNlqcTbpl5D0hKEcwOPvmTajRBZ9bttQ/V+dP39 Tfnxr93LsJBpmV0m8EdUcD6mZIh0sp785yUTZ7lHLuR/8z74ylgkx4fQ9yX/E5FMj3Fp gw1pxuwyJFC0epbK7tEz713HEw6dSfIamrSukTpnAgMV5vBqg29bp6o0sq5iCKINuFPk DKAQ==
Received: by 10.68.130.67 with SMTP id oc3mr20549614pbb.68.1336149674139; Fri, 04 May 2012 09:41:14 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by mx.google.com with ESMTPS id ms7sm1672036pbb.19.2012.05.04.09.41.11 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 May 2012 09:41:12 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so4142977pbc.31 for <rtcweb@ietf.org>; Fri, 04 May 2012 09:41:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.194.1 with SMTP id hs1mr19885690pbc.6.1336149671071; Fri, 04 May 2012 09:41:11 -0700 (PDT)
Received: by 10.68.134.168 with HTTP; Fri, 4 May 2012 09:41:10 -0700 (PDT)
In-Reply-To: <4FA3754D.6020004@ericsson.com>
References: <CAD5OKxtSvdu9gMqfb3ptw5aQJt1NZKLJ1UB_vKRWDXCZurD+1w@mail.gmail.com> <BDA69428-93F2-475B-ABBB-5DE539671DD1@iii.ca> <CAD5OKxs+oZj47DrTSnvaLV7-jNEPOkxjZfJuC5F2fo71kB3-4g@mail.gmail.com> <BLU169-DS251D322307BC173FD221AE932F0@phx.gbl> <CAD5OKxvahkBEs6iVuuyrwuYXzcbKKPvVWL5rx02d6DOhtX_0Cg@mail.gmail.com> <4FA3754D.6020004@ericsson.com>
Date: Fri, 04 May 2012 12:41:10 -0400
Message-ID: <CAD5OKxs3zhxecnXCjsbKzeWNvyJCUy_31pnXKv+orT-T6-FtLg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/alternative; boundary="047d7b15b17182ce3e04bf38966d"
X-Gm-Message-State: ALoCoQmSzoDojO8FTVuTF3HqV7kQSfj7aFXdNBQlaSH+/n8ttOclUJsKa6wA2LXg8OYgmdP+m1Ux
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Final plea about SRTP
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: Fri, 04 May 2012 16:41:19 -0000
On Fri, May 4, 2012 at 2:21 AM, Magnus Westerlund < magnus.westerlund@ericsson.com> wrote: > In my role as a WG chair I have to say that the decision to make SRTP > mandatory to use for WebRTC had a very strong consensus behind it. Yes, > there are some few individuals like yourself that are on the rough side > of this decision. > Let's hope this will work in real life use cases. If it does not (which is what I believe, but I can certainly be wrong), then RTP can be put back at 1.1 version of the standard. I think the bid-down problem is one of the largest for most people. I do not think we need to support auto-negotiation of RTP vs SRTP. Also, RTP should not be allowed from HTTPS sessions, so I do not think bid down is a problem at all. I also see a great benefit with always using SRTP, in that we will get rid > of RTP profile > negotiation. There will be no need to support any other RTP profile than > SAVPF. > I do see a benefit of using one RTP profile only, but this will require WebRTC to use yet another feature that had almost no real life use. This will also ensure that RTCP will need to be re-encoded (as probably RTP) when processing calls to anything outside of WebRTC world. _____________ Roman Shpount
- [rtcweb] Final plea about SRTP Roman Shpount
- Re: [rtcweb] Final plea about SRTP Cullen Jennings
- Re: [rtcweb] Final plea about SRTP Roman Shpount
- Re: [rtcweb] Final plea about SRTP Bernard Aboba
- Re: [rtcweb] Final plea about SRTP Roman Shpount
- Re: [rtcweb] Final plea about SRTP jesse
- Re: [rtcweb] Final plea about SRTP Magnus Westerlund
- Re: [rtcweb] Final plea about SRTP Fabio Pietrosanti (naif)
- Re: [rtcweb] Final plea about SRTP Magnus Westerlund
- Re: [rtcweb] Final plea about SRTP Roman Shpount
- Re: [rtcweb] Final plea about SRTP Randell Jesup
- Re: [rtcweb] Final plea about SRTP Roman Shpount
- [rtcweb] SAVPF history (Re: Final plea about SRTP) Harald Alvestrand
- Re: [rtcweb] SAVPF history (Re: Final plea about … Roman Shpount
- Re: [rtcweb] SAVPF history (Re: Final plea about … Magnus Westerlund
- Re: [rtcweb] SAVPF history (Re: Final plea about … Randell Jesup