Re: [pntaw] Real-time media over TCP

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 09 October 2013 16:01 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 E935521F9DDE for <pntaw@ietfa.amsl.com>; Wed, 9 Oct 2013 09:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.168
X-Spam-Level:
X-Spam-Status: No, score=-0.168 tagged_above=-999 required=5 tests=[AWL=0.269, 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 ihaVdTJ7Sp-D for <pntaw@ietfa.amsl.com>; Wed, 9 Oct 2013 09:01:31 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id A0A1C11E81C7 for <pntaw@ietf.org>; Wed, 9 Oct 2013 08:59:06 -0700 (PDT)
Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by qmta05.westchester.pa.mail.comcast.net with comcast id b15F1m0050cZkys553z4rj; Wed, 09 Oct 2013 15:59:04 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta10.westchester.pa.mail.comcast.net with comcast id b3z41m0073ZTu2S3W3z4K6; Wed, 09 Oct 2013 15:59:04 +0000
Message-ID: <52557D47.3050402@alum.mit.edu>
Date: Wed, 09 Oct 2013 11:59:03 -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> <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> <52538AC4.5060500@alvestrand.no>
In-Reply-To: <52538AC4.5060500@alvestrand.no>
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=1381334344; bh=MM6WNrOtCGuDCc4RyVLQsogVg3a8/irxyLkS76K1OfQ=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=j47q5f3AAlOw6JxVPAeQXOWfMpYZIDLVsBaPJwYXSWGqFIDTonVBU/kedqnwBBSH2 vmnuhwtuoiKJmZs53jx6TxLVkG1pynS6KQjmzLopJgmwvRo9bHQ0Q6lUJoTxxtSKgp btM1Mu/rn30c8+j34gzbxQ0R1u1ZEsGWx2oROOoPl1v4EaM4QqL88UzCvamiqwYG66 6XJ0MDzocrHnxlEglwGW2QoFPWvhT3BgWonHagNgMtRpuLdARP5L3SALQd1sqTT65i G9O7a8sRkLZ6M34OpmXVYysWHqDn3KTzrznXwPa5XYf2p3+50UvkGEdst5j/6/upP3 L5+xWfA8vAZEw==
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: Wed, 09 Oct 2013 16:01:52 -0000

On 10/8/13 12:32 AM, Harald Alvestrand wrote:

> Don't forget the (likely) case where the destination is also reached
> through a TURN server, so that the path is
>
> user 1->TCP->TURN server 1->UDP->TURN server 2->TCP->user 2
>
> For extra irony, the two clients may be using the same TURN service, so
> that the UDP hop is an intra-datacenter or even intra-machine hop :-)

If that happens, its time to seek out a new TURN server vendor.
A good one should be able to figure this out and optimize it.

	Thanks,
	Paul