IETF Logo Mail Archive

Re: [pntaw] Real-time media over TCP

<Markus.Isomaki@nokia.com> Mon, 14 October 2013 19:15 UTC

Return-Path: <Markus.Isomaki@nokia.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 1E52421F9FB3 for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 12:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 U+1cOelDA9sL for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 12:15:35 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 98A4C21E80D4 for <pntaw@ietf.org>; Mon, 14 Oct 2013 12:15:32 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.26]) by mgw-da01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r9EJ6G8I017449 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 14 Oct 2013 22:06:17 +0300
Received: from 008-AM1MPN1-043.mgdnok.nokia.com ([169.254.3.235]) by 008-AM1MMR1-010.mgdnok.nokia.com ([65.54.30.26]) with mapi id 14.03.0136.001; Mon, 14 Oct 2013 19:06:16 +0000
From: Markus.Isomaki@nokia.com
To: partha@parthasarathi.co.in, pntaw@ietf.org
Thread-Topic: [pntaw] Real-time media over TCP
Thread-Index: AQHOpWlrwk9eq/rvIEmYBkw2NSNGdZmyI/aAgACifgCAAN6pAIAApSuAgAAM8oCAACMQgIA1SsoAgAAHUgCAAYcrAIAACRcAgAF6zgCAAAPgcIAAkKAAgAEIx4CAAS4k0IAE5epggAAK6QCAAA3RgIAAMVCAgAAA0lA=
Date: Mon, 14 Oct 2013 19:06:15 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A0E7172@008-AM1MPN1-043.mgdnok.nokia.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>
In-Reply-To: <00d401cec90e$d688d5a0$839a80e0$@co.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Nokia Internal Use Only; Project=None;
x-titus-version: 3.5.9.3
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IhueGIqUfGX1Vo3TN0QuXNLYJ0nYlxFdLFJ5gcB/PGe53F84VK518ganGlutIy+o0MU6sTNCUH7/ZKSzG1tsY08YZ1WSe3114qbZYLHJo/sijV3LmoKgzfDvxeg6LXMqY0XjGFDVD13ObRalSFs0aBBTUObDVKdYN/pUpib2TAy6Ie0vW48/ap31ZEtJhVVVpx2PW4Gb8laD1xJakbzopy9luigbwLJJQAWEdev5+7Kn
x-originating-ip: [172.16.99.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Nokia-AV: Clean
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 19:15:41 -0000

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.

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
>

v2.23.0 | Report a Bug | By Email