Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRTP is a need
Iñaki Baz Castillo <ibc@aliax.net> Thu, 05 April 2012 18:21 UTC
Return-Path: <ibc@aliax.net>
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 A0FA021F84B5 for <rtcweb@ietfa.amsl.com>; Thu, 5 Apr 2012 11:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Level:
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 2-ibNYxyDU8V for <rtcweb@ietfa.amsl.com>; Thu, 5 Apr 2012 11:21:25 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8EFC821F863B for <rtcweb@ietf.org>; Thu, 5 Apr 2012 11:21:25 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so1012040ghb.31 for <rtcweb@ietf.org>; Thu, 05 Apr 2012 11:21:25 -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:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=NPm6Dip+c+hZEiSCuSygI0xqMHm0IO569G16PURg62o=; b=RPYwySsAPRPc1gPpPHV29GmWd5JXlcorXYkrIivVVl12x2Mz5p8jYT/BjbhcCYSj4a gaCSq6GDIleuupDmkZd+AJdMEWywnGooIZIPST9oxp7KgRa8O5sUpH9BurbOUW3O78OR PmrO6RH/hhqhe0pxaDZtVGvcZUa/WSXG791cV3UGopEXt27kdG3BKqTopKqIaqlpsmEJ +Yb8F8djFKYOrtXNQvNDQloS8KqLVQLk9YsSRvAguQztG17LOkEjjGkzlK7yLP6gsmSh eTc9UtYrJDe66DfzjeavDXm3XumPakVGn76uF2TT2Br8HI/YwSvv7ADx2MGpwmm2twe2 rNgw==
Received: by 10.236.156.230 with SMTP id m66mr3402751yhk.52.1333650085151; Thu, 05 Apr 2012 11:21:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.170.165 with HTTP; Thu, 5 Apr 2012 11:21:04 -0700 (PDT)
In-Reply-To: <CAD5OKxvieFaapmjrxNs2WtcHbOVO1zKir5WC29UMtfs=dOBBMg@mail.gmail.com>
References: <CALiegfmz6tgm9WF3KWEK5qwaBGADKFyit=egB36zkjZXNKdeHw@mail.gmail.com> <CALiegfnA8_ntYd5f935P_E6vvMwjrzt+j6UhB9vjmo6h-RzfPA@mail.gmail.com> <CAD5OKxsxrDdsoV18KB1gZSsUBPno-k2zs4E2FTUaoUBdXfh5yA@mail.gmail.com> <CAE6kErhTOFP1qna-OKRmJzM=Rssc0UEXTyDgSyKmh2AM+PuviA@mail.gmail.com> <CAD5OKxuuC1q9uCnREqi_-i0unT=6Uza+oYsCWtanbSjmSi5_DQ@mail.gmail.com> <CALiegf=qo4uWjSBx6F5PmN_vqtbqYzQ9e5igqe_YJPKj0BHQvg@mail.gmail.com> <CAD5OKxu6n_yDAtsy9_pkcGyA8t15y3pY4sQoYmwoPnoL=8_=cA@mail.gmail.com> <4F7DD97D.6050109@jesup.org> <CAD5OKxvieFaapmjrxNs2WtcHbOVO1zKir5WC29UMtfs=dOBBMg@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Thu, 05 Apr 2012 20:21:04 +0200
Message-ID: <CALiegfnwjwKcYnSNxLZ=kXD1xPzv_qteSpMTUiTpFHc9otBRUA@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmlXbteP9ORFLQ1iUydz84nwCbEnCf1i8HZmfaMThYNRSufflCinKZkBaDps7E9S1zhpJ63
Cc: Randell Jesup <randell-ietf@jesup.org>, rtcweb@ietf.org
Subject: Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRTP is a need
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: Thu, 05 Apr 2012 18:21:26 -0000
2012/4/5 Roman Shpount <roman@telurix.com>: > I dislike SDES for being a "somewhat secure" protocol. This is a very > dangerous territory where end user is under impression of being protected, > but reality is different. IMHO, in such situations it is better to have no > security at all, so that users know not to do anything they will regret. And the same is true for DTLS, so? -- Iñaki Baz Castillo <ibc@aliax.net>
- [rtcweb] WebRTC-SIP interop: and why SDES-SRTP is… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Roman Shpount
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… jesse
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Roman Shpount
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Roni Even
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Ravindran, Parthasarathi
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Christer Holmberg
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Roman Shpount
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Roman Shpount
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Roman Shpount
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Randell Jesup
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Roman Shpount
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Roman Shpount
- Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRT… Iñaki Baz Castillo