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

Iñaki Baz Castillo <ibc@aliax.net> Thu, 05 April 2012 10:03 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 8EBEE21F86D8 for <rtcweb@ietfa.amsl.com>; Thu, 5 Apr 2012 03:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.612
X-Spam-Level:
X-Spam-Status: No, score=-2.612 tagged_above=-999 required=5 tests=[AWL=0.065, 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 wkr9qOsFVP4Q for <rtcweb@ietfa.amsl.com>; Thu, 5 Apr 2012 03:03:14 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id DE5E421F86D1 for <rtcweb@ietf.org>; Thu, 5 Apr 2012 03:03:13 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1032563vbb.31 for <rtcweb@ietf.org>; Thu, 05 Apr 2012 03:03:13 -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=/FacmTT5EosJuRZ6d9Ta+Admvcl5Ya6CnhmO1dgrzJk=; b=erGAR67BeuBLOdEe4ZX8ScJC+gqS8afwz6KWSbIt2K5CiGhRl/Kygc355u3gxj3G7n I+zh9IOCzjfXdV0ahV/JHwWOV4DTgbC8FXcZEcbQGPL6Vy14zFUZdPeDuaxQf5Ad+v3s sVuN0FXGrhHERbLRhKOASUFlXd745jb2nT1iQR4D8VLigpFDKs7q0x8f6KGlsaf1BVC0 kmL9iTv4/rSdAi+71Y17AtuymWjfsj9HNyK/1wiOMT8VgRnkTFC0yFhptLsB0C1dDFjn C8RQ3AfgxzzhDxpBpSNLeOpdqcJD/3AHHic061vti+pHdv6zdjpzAi2KrmEwPiMBIXKu QDhw==
Received: by 10.52.88.4 with SMTP id bc4mr1192218vdb.51.1333620193304; Thu, 05 Apr 2012 03:03:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.170.165 with HTTP; Thu, 5 Apr 2012 03:02:53 -0700 (PDT)
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C0E2251F8@inba-mail01.sonusnet.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> <387F9047F55E8C42850AD6B3A7A03C6C0E2251F8@inba-mail01.sonusnet.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Thu, 05 Apr 2012 12:02:53 +0200
Message-ID: <CALiegfk4KFRZNwxrTfUKgsXdN+UrxVao7inggvyPx7KjLKCi4w@mail.gmail.com>
To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnYKBo3wvZvgrZaNQROULanJkSBiugvwoNuy5b/kubswafQ3I7jaNRT/RXA8kxdzKnzY4Fc
Cc: "rtcweb@ietf.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 10:03:14 -0000

2012/4/5 Ravindran, Parthasarathi <pravindran@sonusnet.com>:
> IMHO, there is no need to tweak WebRTC recommendation for the sake of SIP proxy. I'm fine as long as there is a way in WebRTC to interop with SIP. For example, SIP proxy is not suitable for IETF SIPREC recording implementation itself!!!

For the cases in which you need recording, ok, go ahead with a SIP
SBC/B2BUA/server or whatever you need, but please let using a pure SIP
proxy for those not interested in media recording ;)


> But I'm also surprised to see that there is no response for Fabio Pietrosanti mail on DTLS-SRTP trust model mail thread.

Me too. I hope Fabio's nice explanations will be considered by the WG
rather than continuing with "DTLS (which has been NEVER tested with
SRTP) is the only magical solution for the multimedia communications".

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