IETF Logo Mail Archive

Re: [rtcweb] Same location media

Bernard Aboba <bernard_aboba@hotmail.com> Thu, 20 October 2011 17:02 UTC

Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5452B21F8C08 for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 10:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.447
X-Spam-Level:
X-Spam-Status: No, score=-102.447 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 mimvSzdI1Pa7 for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 10:02:36 -0700 (PDT)
Received: from blu0-omc1-s25.blu0.hotmail.com (blu0-omc1-s25.blu0.hotmail.com [65.55.116.36]) by ietfa.amsl.com (Postfix) with ESMTP id BF6F421F8BFE for <rtcweb@ietf.org>; Thu, 20 Oct 2011 10:02:36 -0700 (PDT)
Received: from BLU152-W40 ([65.55.116.8]) by blu0-omc1-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 20 Oct 2011 10:02:30 -0700
Message-ID: <BLU152-W404F6E9A2510EBAC9F1C1F93EB0@phx.gbl>
Content-Type: multipart/alternative; boundary="_077a6252-5e01-4004-b065-786c0196a5fa_"
X-Originating-IP: [24.17.217.162]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: roman@telurix.com
Date: Thu, 20 Oct 2011 10:02:29 -0700
Importance: Normal
In-Reply-To: <CAD5OKxtr=TGj4tCSCUsYxL=+Qturw-CKrTptDAkk=EQgQAVR2A@mail.gmail.com>
References: <CAD5OKxuJi_VS9fRc4P6GN-StWzMhMHAQ2MyO8zJVsMfEeQRftg@mail.gmail.com>, <BLU152-W274DC7DC92EF49307BC57D93EB0@phx.gbl>, <CAD5OKxuooQzhmyHFi87XNPwiNqB7ohzhcbOWEsvCn-Zkshc9kQ@mail.gmail.com>, <BLU152-W6591495353D395650050F293EB0@phx.gbl>, <CAD5OKxtr=TGj4tCSCUsYxL=+Qturw-CKrTptDAkk=EQgQAVR2A@mail.gmail.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Oct 2011 17:02:30.0048 (UTC) FILETIME=[0D4E2A00:01CC8F4A]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Same location media
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Oct 2011 17:02:37 -0000

Roman said:

"You can also operate a TURN server on  TCP port 80 and TLS port 443. In case of TLS connection firewall will have no way to distinguish TURN TLS traffic from HTTPS traffic. Support for HTTP/SOCKS based connections to TURN servers can be implemented as well. BTW, this is why it is essential to be able to specify TURN server location via JavaScript to the RTC client."

[BA] With respect to TURN with TCP/TLS we have found some firewalls that actually do deep packet inspection.  So if you're sending to TCP port 80 and aren't using HTTP, or are sending to port 443 and aren't using TLS (or are using TLS extensions the firewall doesn't understand), the firewall can block.   So yes, it is important to support TURN with TCP/TLS, but it should be recognized that even with that, there will still be a significant percentage of failures.

v2.29.0 | Report a Bug | By Email | System Status