Re: [rtcweb] Why http://www.ietf.org/id/draft-miniero-rtcweb-http-fallback-00.txt ?

Lorenzo Miniero <lorenzo@meetecho.com> Tue, 07 August 2012 19:06 UTC

Return-Path: <lorenzo@meetecho.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 8481521F87C7 for <rtcweb@ietfa.amsl.com>; Tue, 7 Aug 2012 12:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.569
X-Spam-Level:
X-Spam-Status: No, score=-0.569 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, MIME_8BIT_HEADER=0.3]
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 aGrZqy7NsiUn for <rtcweb@ietfa.amsl.com>; Tue, 7 Aug 2012 12:06:50 -0700 (PDT)
Received: from smtplq04.aruba.it (smtplq-out6.aruba.it [62.149.158.26]) by ietfa.amsl.com (Postfix) with SMTP id 1DC6621F8604 for <rtcweb@ietf.org>; Tue, 7 Aug 2012 12:06:49 -0700 (PDT)
Received: (qmail 27446 invoked by uid 89); 7 Aug 2012 19:06:48 -0000
Received: from unknown (HELO smtp5.aruba.it) (62.149.158.225) by smtplq04.aruba.it with SMTP; 7 Aug 2012 19:06:48 -0000
Received: (qmail 31326 invoked by uid 89); 7 Aug 2012 19:06:48 -0000
Received: from unknown (HELO rainpc) (lorenzo@meetecho.com@80.181.173.222) by smtp5.ad.aruba.it with SMTP; 7 Aug 2012 19:06:47 -0000
Date: Tue, 7 Aug 2012 21:00:42 +0200
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: =?UTF-8?B?ScOxYWtp?= Baz Castillo <ibc@aliax.net>
Message-ID: <20120807210042.7e1fb9fa@rainpc>
In-Reply-To: <CALiegf=9BaAnh+RLzihCKmVUTAbEZQ3py8xt53313nvU8a1bkg@mail.gmail.com>
References: <CALiegf=GqR+J3YcAgpRtxid+aDsKeiQttRm8JbjT6RrQWaMG=w@mail.gmail.com> <50215A96.20604@acm.org> <CALiegf=9BaAnh+RLzihCKmVUTAbEZQ3py8xt53313nvU8a1bkg@mail.gmail.com>
Organization: Meetecho
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.8; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Rating: smtp5.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplq04.aruba.it 1.6.2 0/1000/N
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Why http://www.ietf.org/id/draft-miniero-rtcweb-http-fallback-00.txt ?
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: Tue, 07 Aug 2012 19:06:51 -0000

Iñaki,

discussions would be much easier to follow if you just answered to the original thread, rather than opening a new one... about your question, please see inline.


On Tue, 7 Aug 2012 20:18:58 +0200
Iñaki Baz Castillo <ibc@aliax.net> wrote:

> 2012/8/7 Marc Petit-Huguenin <petithug@acm.org>rg>:
> > Or TURN over Websocket.
> 
> Why do we need that? By using TURN over TLS we have all we need to
> avoid stupid hotel's firewalls (that provide "Internet free access"
> but just for HTTP port 80 and HTTPS port 443). It just about setting a
> TURN server listening TLS on port 443, am I right?
> 


"Do we need that" is exactly what I wanted to ask by publishing the draft. There was already some discussions in the past, someone even suggested just deploying TURN over HTTP (a bit like Marc's point on WebSockets), and TURN over TLS (or just anything on 443, for what matters) is another viable solution.

The problem IMHO is that, just as Roman pointed out in his reply, that's not always a way out. In my experience such a scenario is not only limited to those ultra-closed environments he mentioned, but that's probably debatable (who closes his network that way, probably doesn't want anything else to go through anyway).

About the "just pipe everything on 443", please refer to my reply to Hannes in the original thread, as I've answered more extensively there.

Lorenzo

> -- 
> Iñaki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb


-- 
Lorenzo Miniero, COB

Meetecho s.r.l.
Web Conferencing and Collaboration Tools
http://www.meetecho.com