IETF Logo Mail Archive

Re: [rtcweb] Same location media

Roman Shpount <roman@telurix.com> Thu, 20 October 2011 16:52 UTC

Return-Path: <roman@telurix.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 723FA21F8C48 for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 09:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.887
X-Spam-Level:
X-Spam-Status: No, score=-2.887 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 f3l5LkHLuTEM for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 09:52:55 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7A90421F8BA7 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 09:52:54 -0700 (PDT)
Received: by ggnv1 with SMTP id v1so3581766ggn.31 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 09:52:54 -0700 (PDT)
Received: by 10.101.158.4 with SMTP id k4mr2558844ano.94.1319129574060; Thu, 20 Oct 2011 09:52:54 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by mx.google.com with ESMTPS id n7sm27335671ano.17.2011.10.20.09.52.53 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Oct 2011 09:52:53 -0700 (PDT)
Received: by ywa8 with SMTP id 8so3589483ywa.31 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 09:52:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.74.4 with SMTP id p4mr21262483pbv.47.1319129572884; Thu, 20 Oct 2011 09:52:52 -0700 (PDT)
Received: by 10.68.47.40 with HTTP; Thu, 20 Oct 2011 09:52:52 -0700 (PDT)
In-Reply-To: <BLU152-W6591495353D395650050F293EB0@phx.gbl>
References: <CAD5OKxuJi_VS9fRc4P6GN-StWzMhMHAQ2MyO8zJVsMfEeQRftg@mail.gmail.com> <BLU152-W274DC7DC92EF49307BC57D93EB0@phx.gbl> <CAD5OKxuooQzhmyHFi87XNPwiNqB7ohzhcbOWEsvCn-Zkshc9kQ@mail.gmail.com> <BLU152-W6591495353D395650050F293EB0@phx.gbl>
Date: Thu, 20 Oct 2011 12:52:52 -0400
Message-ID: <CAD5OKxtr=TGj4tCSCUsYxL=+Qturw-CKrTptDAkk=EQgQAVR2A@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: multipart/alternative; boundary="f46d0413911d9ac26a04afbdc943"
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 16:52:55 -0000

On Thu, Oct 20, 2011 at 12:48 PM, Bernard Aboba
<bernard_aboba@hotmail.com>wrote:

>  Roman said:
>
> "Technically speaking, if TURN server relay address is used, connectivity
> between the RTC client and TURN server can be TCP (or TLS). So, ICE check
> would be delivered to the RTC client via TCP tunnel."
>
> [BA] Yes, that can be done.  But often we find that a firewall that does
> not permit UDP traversal also has strict policies about TCP (e.g. only to a
> strict set of destination ports).    This is why HTTP traversal is
> implemented by almost all Web conferencing services.
>
>
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.
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email