IETF Logo Mail Archive

Re: [rtcweb] How to determine TLS roles?

"Parthasarathi R" <partha@parthasarathi.co.in> Tue, 11 February 2014 17:28 UTC

Return-Path: <partha@parthasarathi.co.in>
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 825651A05CD for <rtcweb@ietfa.amsl.com>; Tue, 11 Feb 2014 09:28:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.108
X-Spam-Level:
X-Spam-Status: No, score=0.108 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
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 zjOEWAZZenfv for <rtcweb@ietfa.amsl.com>; Tue, 11 Feb 2014 09:28:40 -0800 (PST)
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.19]) by ietfa.amsl.com (Postfix) with ESMTP id 371711A063F for <rtcweb@ietf.org>; Tue, 11 Feb 2014 09:28:40 -0800 (PST)
Received: from userPC (unknown [122.172.226.139]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id AEBF2638C68; Tue, 11 Feb 2014 17:28:35 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1392139719; bh=DfOgxAdP18paLTHN7BAoL93wTzTHTBwiu7Y1uG8ZiEY=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=T9wofR+vXFKguL6/RCn8aiVybMe8/VbTl63iYMUtkyRgSo2TIBPAwBST6AK141V6A vvPurJpFsnr+JqNUlMORg97ZKI48nRC8MINdm0jtEoPLM0ZRxXWkIcIYKimF3siOPo CPKwXbaJWp1Fv5e5LDUcfL4bR4JaWtsKd84c10Pc=
From: Parthasarathi R <partha@parthasarathi.co.in>
To: 'Christer Holmberg' <christer.holmberg@ericsson.com>, 'Tim Panton' <tim@phonefromhere.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1672FC@ESESSMB209.ericsson.se> <9ADA7473-1F36-4D96-A875-D2DC0762E9C2@phonefromhere.com> <7594FB04B1934943A5C02806D1A2204B1D1673C4@ESESSMB209.ericsson.se> <54B6400D-3753-4285-96DB-08EDB23BD03F@phonefromhere.com> <7594FB04B1934943A5C02806D1A2204B1D1674E9@ESESSMB209.ericsson.se>, <CABcZeBOyQeLSwYjKt7hNqn0WViHYhvLmsGecmwCWyGNgUdgSnA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D167825@ESESSMB209.ericsson.se> <8991EDBE-71F3-4456-A614-A9F4926F4955@phonefromhere.com> <7594FB04B1934943A5C02806D1A2204B1D167CF8@ESESSMB209.ericsson.se> <1FC0C1C7-E5AB-4D4C-ABCC-8371457DCBF0@phonefromhere.com> <7594FB04B1934943A5C02806D1A2204B1D167EAC@ESESSMB209.ericsson.se> <FB2E27C9-EE06-4EC8-95DF-E0B18CCFC216@phonefromhere.com> <7594FB04B1934943A5C02806D1A2204B1D1695A8@ESESSMB209.ericsson.se>, <03B88F25-D4A7-468F-B9CE-165A1E6E4D10@phonefromhere.com> <7594FB04B1934943A5C02806D1A2204B1D169D3B@ESESSMB209.ericsson.se>, <44BD6D91-AF9F-47B1-AC79-6F3E86F016C 7@phonefromhere.com> < 7594FB04B1934943A5C02806D1A2204B1D169F84@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D169F84@ESESSMB209.ericsson.se>
Date: Tue, 11 Feb 2014 22:58:29 +0530
Message-ID: <016b01cf274e$b15a6f20$140f4d60$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac8mZBiXQux1+cpSRGeFwm+/NhCfyP//88iA///u0BCAABk5gP//7dswgAAbnoCAAC3h+IAAAg0A///I9eAADI1GgP//7kBQ//8EUwD//fBFYP/7rEAA//dGHqv/7pWMAP/dEq7V/7oM0wA=
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020205.52FA5DC7.019A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules:
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.142
Cc: 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: Tue, 11 Feb 2014 17:28:42 -0000

Hi Christer,

I agree with you that SDP setup attribute has to be used to determine the
TLS role as it is not required that the remote side is also WebRTC endpoint.

Thanks
Partha

> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Christer
> Holmberg
> Sent: Tuesday, February 11, 2014 9:26 PM
> To: Tim Panton
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] How to determine TLS roles?
> 
> 
> Hi,
> 
> >>> However, signalling it over your high level signalling protocol is
> the wrong way to do it (IMHO). Your peer should
> >>> deduce the appropriate DTLS role from the 'signalling' in the ICE
> packets, by looking at the ICE CONTROLLING flag.
> >>
> >> In SIP/SDP O/A it is done using the setup attribute (red: high level
> signalling protocol), and JSEP is based on SDP O/A, so...
> >>
> >> If we do NOT want to use the setup attribute to determine the DTLS
> roles, then I think we need to have a separate discussion about that.
> >
> > we are using the  setup attribute in a way. - actpass means we are
> saying "we don't care".
> 
> That is NOT what it means in SDP O/A - it means "the other side
> decides" :)
> 
> > That leaves it to the lower levels to sort it out - via the
> iceControlling flag.
> >
> > So now you see what caused the rant :-)
> 
> One way would be to add some flag/parameter, to explicitly indicate the
> usage of the iceControlling flag to determine the roles - if people
> want to do that. The advantage is that it would be independent of the
> signalling protocol used between the peers.
> 
> Regards,
> 
> Chrsiter
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email