Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRTP is a need

Iñaki Baz Castillo <ibc@aliax.net> Thu, 05 April 2012 16:35 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 EF68C21F8710 for <rtcweb@ietfa.amsl.com>; Thu, 5 Apr 2012 09:35:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level:
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[AWL=0.081, 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 RFgQNxltDm76 for <rtcweb@ietfa.amsl.com>; Thu, 5 Apr 2012 09:35:31 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0954F21F8709 for <rtcweb@ietf.org>; Thu, 5 Apr 2012 09:35:30 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so902189ggm.31 for <rtcweb@ietf.org>; Thu, 05 Apr 2012 09:35:30 -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=9UcdCj2iKzaxzXyJCYHg3PTsekNWvwtdKcK75mM6oBQ=; b=WGC1cpOE1GHnbK/shqANCJNpxigFY6QtE1aEFQEhTdHe37qtFJsBRSqXEuAAaApZtO jRJusEarfpe/lMxySNZeIlRr/OUD2LIbmaNrTeDAnAM9LH/b0nY9+YnW2+ljpAbcSr0P /GCVwHrFtmkOksUZYLkUmMKHLVLxZnpoRc6BMI+1b//TnbUMJvhOHlsbDcRGDtc9uQjM sHcCeQpyvuH6JGH+vMggwyH7TEq16Gqp0To6FiKxF1Una/LfsI+9jwkyQtJzlBfOxtyK LauwDvsrtMcpRRAHOvBF6CYNwwfyFaJ07r43lTU2zWPojAJHL1+jOmjlYT7v+2ryN3Uw xmxA==
Received: by 10.236.136.33 with SMTP id v21mr2926653yhi.17.1333643730518; Thu, 05 Apr 2012 09:35:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.170.165 with HTTP; Thu, 5 Apr 2012 09:35:10 -0700 (PDT)
In-Reply-To: <CAD5OKxsMhOR9wmKGc6w6SuobH=+dXqTAUPRMYzE8cw_mP0qPWw@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> <CALiegfngqJLRdNPsyBtVMouD_yh+3FiUNAWBuq3vb8BbbjgTqw@mail.gmail.com> <CAD5OKxu+gAS2HGD9HNfSRUX-HMWjzmb6++tv0VWX5s0Ldzqz0Q@mail.gmail.com> <CALiegfmpVRHw4B8TVyt4GNVkktgVz_nQUzFOye9zCJ2hvdY6Rw@mail.gmail.com> <CAD5OKxsMhOR9wmKGc6w6SuobH=+dXqTAUPRMYzE8cw_mP0qPWw@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Thu, 5 Apr 2012 18:35:10 +0200
Message-ID: <CALiegfm+foV-ec3W=j4XAggNXwiDzaw2qKHdKJ9GUZoKX8DP2Q@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: ALoCoQkXQBSm0i9O4caFZgC7BizleKBjHtbyh9/2mQYWQrIMYErnivs+3aehXCchnaOEOMJvoT9W
Cc: 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 16:35:32 -0000

2012/4/5 Roman Shpount <roman@telurix.com>:
>> 2012/4/5 Roman Shpount <roman@telurix.com>:
>> It's possible, sure. First packets are handled in user space, and
>> later go to kernel space with conntrack rules. It's real and there are
>> two RTP proxies doing that: MediaProxy and irtpProxy.
>>
> I do not believe either one of them does ICE-Lite to RTP. As far as I know,
> they are both RTP-to-RTP only.

Sure. I just say that "it's feasible" to do.



> I am still proposing the same thing -- some new protocol instead of
> DTLS-SRTP, which does public key key exchange, and SDES-SRTP from HTTPS with
> RTP from HTTP if enabled. This should allow the widest possible interop
> without forcing a security model on them. I do not belive this compromises
> security since it allows the application developer pick the security model
> they want (new and most secure, old but interoperable, or none at all).

draft required :)


-- 
Iñaki Baz Castillo
<ibc@aliax.net>