Re: [rtcweb] How to determine TLS roles?

Tim Panton <tim@phonefromhere.com> Mon, 10 February 2014 13:45 UTC

Return-Path: <tim@phonefromhere.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3DAB1A0835 for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 05:45:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6-KlTijiFRrd for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 05:45:44 -0800 (PST)
Received: from smtp001.apm-internet.net (smtp001-out.apm-internet.net [85.119.248.222]) by ietfa.amsl.com (Postfix) with ESMTP id 3E3A21A05EF for <rtcweb@ietf.org>; Mon, 10 Feb 2014 05:45:43 -0800 (PST)
Received: (qmail 25464 invoked from network); 10 Feb 2014 13:45:42 -0000
X-AV-Scan: clean
X-APM-Authkey: 83769 11062
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp001.apm-internet.net with SMTP; 10 Feb 2014 13:45:42 -0000
Received: from zimbra003.verygoodemail.com (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id 2027E18A05E8; Mon, 10 Feb 2014 13:45:42 +0000 (GMT)
Received: from limit.westhawk.co.uk (limit.westhawk.co.uk [192.67.4.33]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id DF49A18A05BC; Mon, 10 Feb 2014 13:45:41 +0000 (GMT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Tim Panton <tim@phonefromhere.com>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1672FC@ESESSMB209.ericsson.se>
Date: Mon, 10 Feb 2014 13:45:33 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <9ADA7473-1F36-4D96-A875-D2DC0762E9C2@phonefromhere.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1672FC@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1827)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] How to determine TLS roles?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 10 Feb 2014 13:45:46 -0000

On 10 Feb 2014, at 13:29, Christer Holmberg <christer.holmberg@ericsson.com> wrote:

> Hi,
> 
> If I understand correctly, in RTCWEB we are going to use a single DTLS association for two things:
> 
> 1)      Key exchange for SRTP
> 2)      The data channel
> 
> Now, this means that there needs to be a generic way to determine the TLS roles.
> 
> In WEBRTC, how are the TLS roles determined?


That was the subject of a rant of mine.

I think the correct answer is that the party that ends up being IceControlling then becomes the
DTLS client. Typically the initiator of a session is IceControlling. 

However the recent addition of 
a=setup:passive 
to chrome's SDP clouds the story somewhat, allowing an IceController to say that it is DTLS passive
and allow the non-initiator to be the DTLS client.

Ostensibly this is to support early media - where the receiver of a call wishes to send media before the
initiator does.

As I said (rather intemperately) this added complexity is not worth the benefit.

Tim.

http://webrtchacks.com/tim-rant/

> 
> Regards,
> 
> Christer
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

Tim Panton - Web/VoIP consultant and implementor
www.westhawk.co.uk