Re: [pntaw] Real-time media over TCP

Simon Perreault <simon.perreault@viagenie.ca> Tue, 08 October 2013 18:25 UTC

Return-Path: <simon.perreault@viagenie.ca>
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 0BB2921E827B for <pntaw@ietfa.amsl.com>; Tue, 8 Oct 2013 11:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 JXpUounh2EKI for <pntaw@ietfa.amsl.com>; Tue, 8 Oct 2013 11:25:24 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id BFF0D21E8221 for <pntaw@ietf.org>; Tue, 8 Oct 2013 11:25:20 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:2002::1004]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 13DD5401FD for <pntaw@ietf.org>; Tue, 8 Oct 2013 14:25:19 -0400 (EDT)
Message-ID: <52544E0E.5080405@viagenie.ca>
Date: Tue, 08 Oct 2013 20:25:18 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: pntaw@ietf.org
References: <CAGTXFp92jSzQz05uHngzscz88n=fT_JPbEvQRxgeUUqPVRQUyQ@mail.gmail.com> <52244DD7.1020900@alvestrand.no> <BLU405-EAS183E36A927CA42270B6936D93300@phx.gbl> <522590EE.7070508@alvestrand.no> <C632A223-A55A-47F4-B083-9BDC447DA959@cisco.com> <52262657.3080208@alvestrand.no> <A2C315DB-1882-4BD1-A8C0-E8AF7DEA48F4@cisco.com> <00ca01cec387$f881cae0$e98560a0$@co.in> <BLU406-EAS274696C3D9DFE505F96B8E393130@phx.gbl> <004201cec44f$381a47f0$a84ed7d0$@co.in>
In-Reply-To: <004201cec44f$381a47f0$a84ed7d0$@co.in>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [pntaw] Real-time media over TCP
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: Tue, 08 Oct 2013 18:25:26 -0000

Le 2013-10-08 19:52, Parthasarathi R a écrit :
> I understand that two WebRTC endpoint are behind firewall scenario wherein
> TURN server is unavoidable. Most of the SP & Enterprise deployment wherein
> one of the endpoint is not surely going to be behind UDP blocking Firewall,
> mandating TURN server as a mechanism is overkill. As ICE is mandated in
> WebRTC, supporting ICE-TCP should not be such a complex activity.

A firewall that blocks UDP but allows incoming TCP is not very common, 
is it?

Or did I miss something?

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca