Re: [pntaw] Real-time media over TCP

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 14 October 2013 21:42 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 A7E0E21E812E for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 14:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.262
X-Spam-Level:
X-Spam-Status: No, score=-0.262 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.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 l6lAOw27KU90 for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 14:42:54 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id CE2E621E812D for <pntaw@ietf.org>; Mon, 14 Oct 2013 14:42:53 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta14.westchester.pa.mail.comcast.net with comcast id d67N1m0081ei1Bg5E9itJ7; Mon, 14 Oct 2013 21:42:53 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta24.westchester.pa.mail.comcast.net with comcast id d9it1m0043ZTu2S3k9itJs; Mon, 14 Oct 2013 21:42:53 +0000
Message-ID: <525C655B.6020802@alum.mit.edu>
Date: Mon, 14 Oct 2013 17:42:51 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: pntaw@ietf.org
References: <CAGTXFp92jSzQz05uHngzscz88n=fT_JPbEvQRxgeUUqPVRQUyQ@mail.gmail.com> <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> <E44893DD4E290745BB608EB23FDDB7620A0E7172@008-AM1MPN1-043.mgdnok.nokia.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A0E7172@008-AM1MPN1-043.mgdnok.nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1381786973; bh=2EoNGSUV2vCP5L485n+D8JiVoXD3z4fCoOODvX21Lms=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=FFIBNAbMYYcM5MmL051+3Gk+lLckZSQevxJ7ktQmmGsp+4pKbNJCvyzSY/19rs4WQ /PIuR39Jh4HuVmoobTCe7lXL6hAnCRpD8eG6pb1kbzfgah36nxwtGJdo+/nByhDAK8 jYDKZr4UoGcrKmyRVZqdDqNbZ1/eq1FxaLUGhLVu9BPqiyekMhua1SNB4LK/z7E1DG xDKtSiqbLUFoFuuik6KaFQgqpsyGqSRGtfvNYQHKtXiIHBXdDXjhJwlWPyNSK/CO43 NpHdGJsxC6K8zMx9tAd9uZXRpGYto/afNhSgzObfaSsLJ/oZ6N9hKUO56Y33eTHA86 i+RKJYLJQrmdw==
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: Mon, 14 Oct 2013 21:42:58 -0000

On 10/14/13 3: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. 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.

Doesn't that depend on where the relay is?

UDP relayed across the world might not be preferable to TCP direct to a 
point down the street.

But in practice I suppose the relay will be conveniently located 
relative to one of the two endpoints.

	Thanks,
	Paul

> 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
>