Re: [pntaw] TURN over websockets or just TURN.

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Wed, 25 September 2013 18:32 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 7AACF21F969F for <pntaw@ietfa.amsl.com>; Wed, 25 Sep 2013 11:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level:
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599]
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 Iej+-d5PmGdj for <pntaw@ietfa.amsl.com>; Wed, 25 Sep 2013 11:32:29 -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 6524C21F9E0B for <pntaw@ietf.org>; Wed, 25 Sep 2013 11:32:27 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id C104023F067D; Wed, 25 Sep 2013 20:32:26 +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; Wed, 25 Sep 2013 20:32:07 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Thread-Topic: [pntaw] TURN over websockets or just TURN.
Thread-Index: Ac651aqKgci54WbeToGdcCETWYgQigAAvTwAAAANf1AAAWRD2QAA3kSAAA64gqA=
Date: Wed, 25 Sep 2013 18:32:06 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17BD5487@MCHP04MSX.global-ad.net>
References: <9F33F40F6F2CD847824537F3C4E37DDF17BD44F6@MCHP04MSX.global-ad.net> <5242B888.6010000@gmail.com>, <E44893DD4E290745BB608EB23FDDB7620A0CB1CD@008-AM1MPN1-042.mgdnok.nokia.com> <86E1F066-5AF5-47B2-B6E5-10869E09A651@siemens-enterprise.com> <5242E42D.6020100@gmail.com>
In-Reply-To: <5242E42D.6020100@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pntaw@ietf.org" <pntaw@ietf.org>, "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>
Subject: Re: [pntaw] TURN over websockets or just TURN.
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: Wed, 25 Sep 2013 18:32:29 -0000

On: 25 September 2013 14:25 Sergio Garcia Murillo: Wrote:

> Anyway, the argument is still the same, turn over websockets will work
> on every scenario where turn over tls works, and in addition it may
> work
> in some others. Also, given that most people are using websockets for
> signaling anyway, we will ensure that in 100% of the cases if signaling
> over websockets works, media over websockets will work (except if
> explicitly forbidden by enterprises policies).
> 
> We can argue later if the percentage of cases additionally covered by
> turn over ws is significant enough so it is worthy to add a new
> protocol
> and change both clients and server (while I see that other initiatives
> are requiring it already). But I think that at least having an
> alternative proposal is a good thing.
> 

This debate is definitely a good thing and we seem to be agreed that there is a problem to solve so we are making progress. I was trying to have the debate now on whether the websockets overhead is worthwhile or not I don't see any reason to delay that discussion.

I am still to see any concrete examples of scenarios where the websockets approach provides better connectivity which is what I think we need to see before we can say that it is worthwhile.

Regards
Andy