IETF Logo Mail Archive

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

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Wed, 25 September 2013 13:25 UTC

Return-Path: <sergio.garcia.murillo@gmail.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 EFFEF11E810D for <pntaw@ietfa.amsl.com>; Wed, 25 Sep 2013 06:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level:
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.063, 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 SO2Pw2smInUv for <pntaw@ietfa.amsl.com>; Wed, 25 Sep 2013 06:25:06 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id BF9F421F9FB6 for <pntaw@ietf.org>; Wed, 25 Sep 2013 06:25:05 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id k14so6110309wgh.25 for <pntaw@ietf.org>; Wed, 25 Sep 2013 06:25:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=OjG6PY7dNGtRXQqVjIAUqgzNkVKw1kiRbwhjeLHF358=; b=GCdnhHP4pLmG4tlPVNoDigEQ/qImpdkQUcopk4vAeFuhlRfPqGy5OoiJsUr/HhTpiL jLVExky26D2UuZL0i/GakVfBgh5cPY0f67zMMvqi1eXV6+Ol86gFHU7SUxHbAxMYMdv1 kbWVXP73gVOCt/V5iwKUPbWCXCzGHaleSmIzSiDKgQQVvVLSfngcszqBcQxfOR/uK4YD W3oSlW1IYl5CKM7Rrivypi+sc+mQCPWt5oNBxHoWdb/CBPZPx0SsVoNB4flFjhiNp4Dt bFOkOwkRhUsU6BaB0FlGich6/S6Ui+UY3B8tC+g38L8FOGxhsv5OtdBOY2aX8wJQSJmY 3QpA==
X-Received: by 10.180.85.65 with SMTP id f1mr22535293wiz.33.1380115503722; Wed, 25 Sep 2013 06:25:03 -0700 (PDT)
Received: from [192.168.1.45] (54.Red-83-61-124.dynamicIP.rima-tde.net. [83.61.124.54]) by mx.google.com with ESMTPSA id i8sm17949727wib.1.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 25 Sep 2013 06:25:03 -0700 (PDT)
Message-ID: <5242E42D.6020100@gmail.com>
Date: Wed, 25 Sep 2013 15:25:01 +0200
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
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>
In-Reply-To: <86E1F066-5AF5-47B2-B6E5-10869E09A651@siemens-enterprise.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
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 13:25:07 -0000

El 25/09/2013 13:00, Hutton, Andrew escribió:
> At least according to RFC 6455 the use of HTTP CONNECT for websockets is independent of whether the connection is secure or not.
>
Hi Andy,

Please correct me if I am wrong, but would browsers still do an HTTP 
connect for http 1.1 request? I thought it was only for HTTPS requests.

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.

Best regards
Sergio

v2.23.0 | Report a Bug | By Email