IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Tue, 20 March 2012 11:20 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 8B86921F8655 for <rtcweb@ietfa.amsl.com>; Tue, 20 Mar 2012 04:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.607
X-Spam-Level:
X-Spam-Status: No, score=-2.607 tagged_above=-999 required=5 tests=[AWL=0.070, 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 YfQ1SUxvSHvm for <rtcweb@ietfa.amsl.com>; Tue, 20 Mar 2012 04:20:32 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E29B321F860F for <rtcweb@ietf.org>; Tue, 20 Mar 2012 04:20:31 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so8761852vcb.31 for <rtcweb@ietf.org>; Tue, 20 Mar 2012 04:20:31 -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=zye9UXJvN1NEsFVji1/ud1O3oOEWPx0tARwGmKqyR0g=; b=ZHm0mfjS97nIsPPa8hATzm45m2XaRSfI3xNbUt0drytgDMNVTlYbw9tXwu6+ZBCDGd vNh9vu2DkVLFsQlpuRLlTpAhGPZqBeYGsycFot6xXQ1n7X102lUs29VPoO5p0IWc1krz MumCuwxqxowGERj8P0/eFk2KKWhP65puT4jxP/0Cl6azSsC1DASG4+ZOpovBBhGy4zOF 0Gnp4KavGBlUJVu5scmUYD3kjCeSa5X/h7BgcB4Bn/iINjUywa39CUnz958C7em+b9Em VGyCpxWJaXj7IPcd1xTcQrfFB40A9ZKZjr4rZB3V1nx2S/IO9oi8RSDYGaihJGsgGf0N YxNQ==
Received: by 10.220.152.205 with SMTP id h13mr7108554vcw.12.1332242431304; Tue, 20 Mar 2012 04:20:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.170.165 with HTTP; Tue, 20 Mar 2012 04:20:10 -0700 (PDT)
In-Reply-To: <CAD5OKxujAoGaqpAG62X6EQVu5bS5m2a+9DYBP=LYjo1qGtQS6w@mail.gmail.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> <6F428EFD2B8C2F49A2FB1317291A76C113564482A7@USNAVSXCHMBSA1.ndc.alcatel-lucent.com> <ADBB75F3-E20C-4EC4-B9C3-EF2E4BFF409C@phonefromhere.com> <CAD5OKxvuEV8Vbq3h7=ZgcKmREjmguvz5n-SpXr2n-EY7a_ddxg@mail.gmail.com> <CALiegfk1ozOKPcDjbd3H_z2Edzh4RcZpYyJSWdw_1DJ04muQXA@mail.gmail.com> <CAD5OKxu8-+0O0=eE7mD1hi=nPUpEXczGj=bRNQCQL1BW8c-c-Q@mail.gmail.com> <D75A384B-0F38-4E30-8C03-12E903A69B64@acmepacket.com> <CAD5OKxustPmGJRMKoUU4kXosALpG8RzHC50-sjb5KKUPq3L3XA@mail.gmail.com> <CABcZeBNHY8k5YNiZt2=wqKo1Bkecxvyw4kyGi9W235fmdhwjGw@mail.gmail.com> <CAD5OKxujAoGaqpAG62X6EQVu5bS5m2a+9DYBP=LYjo1qGtQS6w@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 20 Mar 2012 12:20:10 +0100
Message-ID: <CALiegfkd5q2OzDTddQX2emhycVkwpnAD1SrF-iofVe6wVJD1pw@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: ALoCoQmKf8NMzEjGwhxC5DpTOLShCpJxTPaTPYZNcu0mZLOu58tKvzrIhBhz/Yd9MI/wj7WqLFoF
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: Tue, 20 Mar 2012 11:20:33 -0000

2012/3/20 Roman Shpount <roman@telurix.com>:
> I would also like to have a simplified DTLS specification for DTLS-SRTP,
> with as many as possible unnecessary features (encryption algorithms,
> cookies and such) removed and only a few required scenarios supported. For
> instance, I do not want DTLS on a WebRTC channel start negotiation and end
> up with anything except SRTP as an encryption protocol. Ideally, I want
> something were an interop test can be developed with a manageable number of
> scenarios.
>
> P.S. Sending RSA public key in the session description instead of
> fingerprint and then encrypting the SRTP key using this public key and
> sending it in the ICE message might be a much simpler call setup mechanism
> to implement then bringing the whole DTLS into the stack. This should also
> allow us to setup a secure call with no overhead in addition to ICE.

Would this DTLS-SRTP simplification interoperate with other
technologies also implementing DTLS-SRTP+SDP?

AFAIK there are (not yet) SIP devices supporting DTLS-SRTP (maybe I'm
wrong), however my question is: once there are SIP implementations (or
Jingle ones implementing DTLS-SRTP) would those implementations
interoperate with your simplified version of DTLS for WebRTC?

Regards.

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

v2.23.0 | Report a Bug | By Email