IETF Logo Mail Archive

Re: [pntaw] New version of draft-hutton-rtcweb-nat-firewall-considerations

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Sat, 21 September 2013 22:48 UTC

Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9387E11E81AC for <pntaw@ietfa.amsl.com>; Sat, 21 Sep 2013 15:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level:
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156]
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 8XD7zOtA+huY for <pntaw@ietfa.amsl.com>; Sat, 21 Sep 2013 15:48:28 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 7B25911E81B6 for <pntaw@ietf.org>; Sat, 21 Sep 2013 15:48:28 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id E8A7F23F04A6; Sun, 22 Sep 2013 00:48:24 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.31]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Sun, 22 Sep 2013 00:48:09 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, Bernard Aboba <bernard_aboba@hotmail.com>
Thread-Topic: [pntaw] New version of draft-hutton-rtcweb-nat-firewall-considerations
Thread-Index: AQHOtp7QEOTTdbUJCU2Dt1KADZwEFZnQyupU
Date: Sat, 21 Sep 2013 22:48:08 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17BD01A8@MCHP04MSX.global-ad.net>
References: <9F33F40F6F2CD847824537F3C4E37DDF17BCF3A5@MCHP04MSX.global-ad.net>, , <523CCD06.3030902@gmail.com>, <BLU169-W136A55AC013DA147313576D93220@phx.gbl>, <523CD42E.8070102@gmail.com> <BLU169-W82036280852F26ED26283C93230@phx.gbl>, <523D4F17.2040202@gmail.com>
In-Reply-To: <523D4F17.2040202@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.42.196]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pntaw@ietf.org" <pntaw@ietf.org>
Subject: Re: [pntaw] New version of draft-hutton-rtcweb-nat-firewall-considerations
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Sep 2013 22:48:32 -0000

I just don't see any advantage in the TURN over Websockets approach over the HTTP Connect initiated tunnel which works without any new protocol and therefore works with existing TURN servers.

Andy



________________________________________
From: pntaw-bounces@ietf.org [pntaw-bounces@ietf.org] on behalf of Sergio Garcia Murillo [sergio.garcia.murillo@gmail.com]
Sent: Saturday, September 21, 2013 8:47 AM
To: Bernard Aboba
Cc: pntaw@ietf.org
Subject: Re: [pntaw] New version of     draft-hutton-rtcweb-nat-firewall-considerations

>
> "So in 100% cases that TURN over TLS works, TURN over (secure)
> websockets works too."
>
> [BA] Agree they would both traverse that firewall equally well, but
> TURN over (secure) websockets only works if the TURN server supports
> it, which most won't.   This makes mandating TURN over Webosckets
> support in the browser a hard sell.

We are already working on providing a working prototype of TURN over
websocket that will show how easy would be to add it to both browser and
server. In fact, on first phase, we will not change the TURN server at
all but use a websockify proxy https://github.com/kanaka/websockify to
the WS to TCP conversion.

Best regards
Sergio

_______________________________________________
pntaw mailing list
pntaw@ietf.org
https://www.ietf.org/mailman/listinfo/pntaw

v2.23.0 | Report a Bug | By Email