Re: [pntaw] Real-time media over TCP

Dan Wing <dwing@cisco.com> Tue, 15 October 2013 00:01 UTC

Return-Path: <dwing@cisco.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 64EE821E8137 for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 17:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 vEd185h0Sy7j for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 17:01:29 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1424F21F9FCF for <pntaw@ietf.org>; Mon, 14 Oct 2013 17:01:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2269; q=dns/txt; s=iport; t=1381795287; x=1383004887; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=uC6lPDTH7xe9kIuH0KC3mXPo4mJ5brDWtVZK1qNKEcU=; b=anyP/yrXEwNaGIcOxOLryJtpZ3vTaC7c2kPpzQ5vy9QF3lsMuwZ3wwk2 GiNNkJ0fCE07IoUbljfk3GUQzoE+c5IBd+l4H+EYrKvb85BmFj9XKBNYE r9QZz2bVRjh/0glf3kM9USAKmURWmerON5JoiUDvb9EFVUTZDM1c8VZ7T w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAN6EXFKrRDoH/2dsb2JhbABZgwc4wnKBKBZ0giUBAQEDAQEBATc0CwUHBAsRBAEBKAcnHwkIGYgABQ29aASOEYEGMwcGEIMJgQYDiTyOSJICg0QcgTQ
X-IronPort-AV: E=Sophos;i="4.93,494,1378857600"; d="scan'208";a="94716603"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 15 Oct 2013 00:01:26 +0000
Received: from dhcp-10-155-84-77.cisco.com (dhcp-10-155-84-77.cisco.com [10.155.84.77]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9F01Pe7006974; Tue, 15 Oct 2013 00:01:25 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A0E7172@008-AM1MPN1-043.mgdnok.nokia.com>
Date: Mon, 14 Oct 2013 17:01:26 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A51F486D-3BC0-4090-80CD-B4A15AC3EE69@cisco.com>
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> <52544E0E.5080405@viagenie.ca> <003b01cec511$27e1abe0$77a503a0$@co.in> <E44893DD4E290745BB608EB23FDDB7620A0D672F@008-AM1MPN1-042.mgdnok.nokia.com> <9E34D50A21D1D1489134B4D770CE039768081AC9@SZXEMA504-MBX.china.huawei.com> <004e01cec5df$cf8daaf0$6ea900d0$@co.in> <E44893DD4E290745BB608EB23FDDB7620A0E2DC6@008-AM1MPN1-043.mgdnok.nokia.com> <9F33F40F6F2CD847824537F3C4E37DDF17BEFB3E@MCHP04MSX.global-ad.net> <BLU402-EAS357ECBFC621A567B9D3A7B4931A0@phx.gbl> <525C148F.8070502@gmail.com> <00d401cec90e$d688d5a0$839a80e0$@co.in> <E44893DD4E2 90745BB608EB23FDDB7620A0E7172@008-AM1MPN1-043.mgdnok.nokia.com>
To: Markus.Isomaki@nokia.com
X-Mailer: Apple Mail (2.1510)
Cc: pntaw@ietf.org, partha@parthasarathi.co.in
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, 15 Oct 2013 00:01:33 -0000

On Oct 14, 2013, at 12:06 PM, Markus.Isomaki@nokia.com wrote:

> Hi,
> 
> In practice I doubt you find many situations where UDP is completely blocked but incoming TCP connections from anywhere are allowed.

Agreed.  

But if both ends are trying to communicate with each other, their communications will appear as a TCP simultaneous-open.  That could (in fact, "should") work across a firewall because the firewall will see an outbound SYN to a host/port after which it will see an inbound SYN from that same host/port.

-d


> I'm not sure the use cases and requirements document really claims that to be the case, but I agree it is somewhat ambiguous. That means that while direct TCP connection would be better than TCP based relay, its success rate would be very small. I suppose we agree that UDP based relay would still be better than direct TCP for real-time media.
> 
> Markus
> 
>> -----Original Message-----
>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
>> Of ext Parthasarathi R
>> Sent: 14 October, 2013 21:55
>> To: pntaw@ietf.org
>> Subject: Re: [pntaw] Real-time media over TCP
>> 
>> Hi all,
>> 
>> My point is that the direct media connection has to be given priority over
>> TURN based mechanism. In case of ICE-TCP, there is a possibility for the
>> direction connection between two browsers involved in the WebRTC session
>> and should be given priority over TURN based mechanism. So, 6) TCP based
>> candidates (ICE-TCP) - MUST
>> 
>> There is an assumption in the discussion that the incoming TCP traffic is not
>> allowed through firewall. In case it is the problem to be solved, RTCWeb
>> usecase and requirement has to be updated. I noticed in
>> draft-ietf-rtcweb-use-cases-and-requirements-12 (published today) that
>> there is no such requirement. I'll write the mail in RTCWeb WG to get the
>> clarity on the requirement in case the firewall forbidding incoming TCP traffic
>> is a matter of missing text in the requirement.
>> 
>> Thanks
>> Partha
>> 
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw