
From partha@parthasarathi.co.in  Mon Oct  7 11:06:46 2013
Return-Path: <partha@parthasarathi.co.in>
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 CDE2821E81B4 for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 11:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.776
X-Spam-Level: 
X-Spam-Status: No, score=-0.776 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334]
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 khEJ6eVve43u for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 11:06:41 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us2.mailhostbox.com [69.93.141.235]) by ietfa.amsl.com (Postfix) with ESMTP id 9374411E8103 for <pntaw@ietf.org>; Mon,  7 Oct 2013 11:06:41 -0700 (PDT)
Received: from userPC (unknown [122.178.221.13]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id ED23B6395DF; Mon,  7 Oct 2013 18:06:34 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1381169200; bh=GvWYZqJ6G4ASJXN6RtjjjshMN3xuYlmVKHOrJXDvTz0=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=RrYf0+B0C2N98vRu4qQkFPUpwE5TqrUSVUKavT+QrTV3fYc48bBi8Mv+tVB+YDfXQ l00v0tlslmGXPIjZq7/TBVgSbBn2msgEjmgBRSk8GW3vpIM7VEfP5ao0tD34EYlO/G hyKzj05+F3j5c/edDtWrkuJIcRwx4py5nt3hdpf8=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Dan Wing'" <dwing@cisco.com>, "'Harald Alvestrand'" <harald@alvestrand.no>, "'Bernard Aboba'" <bernard_aboba@hotmail.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>
In-Reply-To: <A2C315DB-1882-4BD1-A8C0-E8AF7DEA48F4@cisco.com>
Date: Mon, 7 Oct 2013 23:36:32 +0530
Message-ID: <00ca01cec387$f881cae0$e98560a0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac6o4pXSw23jvZ0+Qrq30/A+rEnOQgaoU8bg
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020206.5252F82F.01AE, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.142
Cc: pntaw@ietf.org
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, 07 Oct 2013 18:06:46 -0000

Hi all,

RTP over TCP is unavoidable in case of RTCWeb media traffic has to traverse
through UDP blocking firewalls. TCP candidates with ICE (RFC 6544) may fail
due to the current OS implementation wherein TCP simultaneous Open will not
work. 

I have concern w.r.t TURN server as it introduces one extra network element
for RTCWeb session establishment. The current argument favoring for TURN
server is that RTP over TCP is required only till TURN server whereas the
media traffic between TURN server and the destination is UDP. In couple of
WebRTC deployment in Service provider network and Enterprise network, TURN
server will exist near to the destination and the WebRTC media traffic in
the internet is "RTP over TCP". I guess that Victor scenario falls under the
same category. In these deployment, RTP over TCP has advantage over TURN
over TCP as the extra element shall be avoided. 

Also, SCTP over DTLS over UDP will not work in case of RTCWeb media traffic
has to traverse through UDP blocking firewalls. So, there is a need of SCTP
over DTLS over TCP or multipath TCP kind of transport to meet this
requirement which needs separate discussion. 

Thanks
Partha

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of Dan Wing
> Sent: Wednesday, September 04, 2013 1:47 AM
> To: Harald Alvestrand
> Cc: Bernard Aboba; pntaw@ietf.org
> Subject: Re: [pntaw] Real-time media over TCP
> 
> 
> On Sep 3, 2013, at 11:11 AM, Harald Alvestrand <harald@alvestrand.no>
> wrote:
> 
> > On 09/03/2013 07:25 PM, Dan Wing wrote:
> >>> Multiple TCP connections seems like a suboptimal design, given the
> existence of other solutions like Minion or SCTP.
> >> Sure.  But those technologies weren't on the table when Victor did
> interactive audio/video over TCP, I'm sure.  Much like they weren't on
> the table when HTTP started doing multiple TCP connections back in the
> early days of Netscape.
> >
> > Victor didn't provide a date, so I was thinking "recently" - SCTP is
> 10 years old at this point.
> 
> SCTP has been around a long time as a protocol but for a variety of
> reasons has seen no deployment on the Internet to date, including no
> availability in the mainstream OSs which is everyone's interest.  SCTP-
> over-UDP was only recently defined and its user-mode release was only
> 12 or 18 months ago or so.
> 
> > Minion is newer than that, of course.
> >>
> >>> If both sides have TURN over TCP (or TURN over HTTP) enabled, and
> their respective TURN servers can talk UDP to each other, communication
> will occur, I think. I don't think we need to add TCP candidates for
> the TURN case in order to bypass firewalls.
> >>>
> >>> We might want to do so for the benefit of the pure peer-to-peer
> case, but I'm not sure it's a case that's important enough to make 6062
> (TURN TCP allocations) or 6544 (ICE TCP allocations, no TURN server)
> into MUSTs for RTCWEB.
> >> I agree.  Additionally, before anyone ventures too far down that
> path it would be useful to understand how well the expected RTCWeb
> endpoints could do peer-to-peer TCP connections.  Reliable peer-to-peer
> TCP needs TCP simultaneous open needs to work well on both hosts, per
> the research by Saikat Guha and Paul Francis
> http://conferences.sigcomm.org/imc/2005/papers/imc05efiles/guha/guha.pd
> f.  In that research, they found Windows XP SP1 doesn't do simultaneous
> open well, but Windows XP with SP2 and SP3 and Linux worked okay.  I
> have not seen similar research for Android, OS X, or Windows 7 or
> Windows 8.
> > Indeed; that article seemed to indicate that the brand of NAT you
> bought was a decisive factor - it would be interesting to see if the
> state of the art has become more or less symmetric-TCP hostile in the
> intervening 8 years.
> 
> -d
> 
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From bernard_aboba@hotmail.com  Mon Oct  7 11:32:53 2013
Return-Path: <bernard_aboba@hotmail.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 6A04521E81BD for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 11:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 pdNc-513dt7v for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 11:32:49 -0700 (PDT)
Received: from blu0-omc1-s27.blu0.hotmail.com (blu0-omc1-s27.blu0.hotmail.com [65.55.116.38]) by ietfa.amsl.com (Postfix) with ESMTP id 0B70E21E81A1 for <pntaw@ietf.org>; Mon,  7 Oct 2013 11:32:48 -0700 (PDT)
Received: from BLU406-EAS274 ([65.55.116.7]) by blu0-omc1-s27.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 7 Oct 2013 11:32:48 -0700
X-TMN: [zvfMKlSQ4hBBkftQ+wc2+N2MmmZjwMYo]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU406-EAS274696C3D9DFE505F96B8E393130@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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>
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <00ca01cec387$f881cae0$e98560a0$@co.in>
Date: Mon, 7 Oct 2013 11:32:44 -0700
To: Parthasarathi R <partha@parthasarathi.co.in>
X-OriginalArrivalTime: 07 Oct 2013 18:32:48.0314 (UTC) FILETIME=[9F7071A0:01CEC38B]
Cc: Harald Alvestrand <harald@alvestrand.no>, "pntaw@ietf.org" <pntaw@ietf.org>, Dan Wing <dwing@cisco.com>
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, 07 Oct 2013 18:32:53 -0000

As you point out, in most cases ICE-TCP will not avoid use of TURN, so we ar=
e only talking about a modest efficiency gain for ICE-TCP and RTP over TCP, b=
ut a substantial increase in complexity.=20

Running SCTP over TCP is undesirable because the congestion control in SCTP a=
nd TCP will interact poorly with each other. =20

> On Oct 7, 2013, at 11:07 AM, "Parthasarathi R" <partha@parthasarathi.co.in=
> wrote:
>=20
> Hi all,
>=20
> RTP over TCP is unavoidable in case of RTCWeb media traffic has to travers=
e
> through UDP blocking firewalls. TCP candidates with ICE (RFC 6544) may fai=
l
> due to the current OS implementation wherein TCP simultaneous Open will no=
t
> work.=20
>=20
> I have concern w.r.t TURN server as it introduces one extra network elemen=
t
> for RTCWeb session establishment. The current argument favoring for TURN
> server is that RTP over TCP is required only till TURN server whereas the
> media traffic between TURN server and the destination is UDP. In couple of=

> WebRTC deployment in Service provider network and Enterprise network, TURN=

> server will exist near to the destination and the WebRTC media traffic in
> the internet is "RTP over TCP". I guess that Victor scenario falls under t=
he
> same category. In these deployment, RTP over TCP has advantage over TURN
> over TCP as the extra element shall be avoided.=20
>=20
> Also, SCTP over DTLS over UDP will not work in case of RTCWeb media traffi=
c
> has to traverse through UDP blocking firewalls. So, there is a need of SCT=
P
> over DTLS over TCP or multipath TCP kind of transport to meet this
> requirement which needs separate discussion.=20
>=20
> Thanks
> Partha
>=20
>> -----Original Message-----
>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
>> Of Dan Wing
>> Sent: Wednesday, September 04, 2013 1:47 AM
>> To: Harald Alvestrand
>> Cc: Bernard Aboba; pntaw@ietf.org
>> Subject: Re: [pntaw] Real-time media over TCP
>>=20
>>=20
>> On Sep 3, 2013, at 11:11 AM, Harald Alvestrand <harald@alvestrand.no>
>> wrote:
>>=20
>>> On 09/03/2013 07:25 PM, Dan Wing wrote:
>>>>> Multiple TCP connections seems like a suboptimal design, given the
>> existence of other solutions like Minion or SCTP.
>>>> Sure.  But those technologies weren't on the table when Victor did
>> interactive audio/video over TCP, I'm sure.  Much like they weren't on
>> the table when HTTP started doing multiple TCP connections back in the
>> early days of Netscape.
>>>=20
>>> Victor didn't provide a date, so I was thinking "recently" - SCTP is
>> 10 years old at this point.
>>=20
>> SCTP has been around a long time as a protocol but for a variety of
>> reasons has seen no deployment on the Internet to date, including no
>> availability in the mainstream OSs which is everyone's interest.  SCTP-
>> over-UDP was only recently defined and its user-mode release was only
>> 12 or 18 months ago or so.
>>=20
>>> Minion is newer than that, of course.
>>>>=20
>>>>> If both sides have TURN over TCP (or TURN over HTTP) enabled, and
>> their respective TURN servers can talk UDP to each other, communication
>> will occur, I think. I don't think we need to add TCP candidates for
>> the TURN case in order to bypass firewalls.
>>>>>=20
>>>>> We might want to do so for the benefit of the pure peer-to-peer
>> case, but I'm not sure it's a case that's important enough to make 6062
>> (TURN TCP allocations) or 6544 (ICE TCP allocations, no TURN server)
>> into MUSTs for RTCWEB.
>>>> I agree.  Additionally, before anyone ventures too far down that
>> path it would be useful to understand how well the expected RTCWeb
>> endpoints could do peer-to-peer TCP connections.  Reliable peer-to-peer
>> TCP needs TCP simultaneous open needs to work well on both hosts, per
>> the research by Saikat Guha and Paul Francis
>> http://conferences.sigcomm.org/imc/2005/papers/imc05efiles/guha/guha.pd
>> f.  In that research, they found Windows XP SP1 doesn't do simultaneous
>> open well, but Windows XP with SP2 and SP3 and Linux worked okay.  I
>> have not seen similar research for Android, OS X, or Windows 7 or
>> Windows 8.
>>> Indeed; that article seemed to indicate that the brand of NAT you
>> bought was a decisive factor - it would be interesting to see if the
>> state of the art has become more or less symmetric-TCP hostile in the
>> intervening 8 years.
>>=20
>> -d
>>=20
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

From dwing@cisco.com  Mon Oct  7 13:08:40 2013
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 9A22511E8125 for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 13:08:40 -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=[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 uVV-cRVwO+Vx for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 13:08:36 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 7946111E8131 for <pntaw@ietf.org>; Mon,  7 Oct 2013 13:08:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5444; q=dns/txt; s=iport; t=1381176515; x=1382386115; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=kd8NP7yKgxTcHRy8rlo5Czc9cdA3EV2JFYViE+cdZYA=; b=ec4wvrgwljFXmzYgcNksTjp7hkfRcxYpxEBf/KBr2O0ZnwXmfkQHZ6N+ /zvDfODQMPzPC3NGUk5epQcxvwdvwfy9Yxi7uAvhAno1brkMW2/FwRavp /VgN3OOZlA/vWEhLUCzYAJhyrWUiC1Iqm3PTGAg8XcWO9v+ePusOtDdjB Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAPUTU1KrRDoG/2dsb2JhbABZgwc4rxySV4EiFnSCJQEBAQMBAQEBNy4EAggDBQcECxEEAQEBJwcnHwMBBQgGExuHWQMJBQ27F4xmgjgzBwaDGYEEA4FTh2aKa4F1gWiBL4sbhTaDRBw
X-IronPort-AV: E=Sophos;i="4.90,1051,1371081600"; d="scan'208";a="91573650"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 07 Oct 2013 20:08:33 +0000
Received: from sjc-vpn5-197.cisco.com (sjc-vpn5-197.cisco.com [10.21.88.197]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r97K8V4S018602; Mon, 7 Oct 2013 20:08:32 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: <BLU406-EAS274696C3D9DFE505F96B8E393130@phx.gbl>
Date: Mon, 7 Oct 2013 13:08:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2924C1EA-613D-4B05-BD24-4CFD1411386E@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>
To: Bernard Aboba <bernard_aboba@hotmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: Harald Alvestrand <harald@alvestrand.no>, "pntaw@ietf.org" <pntaw@ietf.org>, Parthasarathi R <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: Mon, 07 Oct 2013 20:08:41 -0000

On Oct 7, 2013, at 11:32 AM, Bernard Aboba <bernard_aboba@hotmail.com> =
wrote:

> As you point out, in most cases ICE-TCP will not avoid use of TURN, so =
we are only talking about a modest efficiency gain for ICE-TCP and RTP =
over TCP, but a substantial increase in complexity.=20
>=20
> Running SCTP over TCP is undesirable because the congestion control in =
SCTP and TCP will interact poorly with each other. =20

And, even if a full SCTP stack is run over a full TCP stack, that will =
work but I agree won't work well.  But working is better than not =
working in situations where UDP is blocked.

To work well, we might look at SCTP Minion =
(draft-iyengar-minion-concept, which disables TCP's congestion control =
in lieu of SCTP's congestion control) is one answer to those conflicting =
congestion controls.

-d




>=20
>> On Oct 7, 2013, at 11:07 AM, "Parthasarathi R" =
<partha@parthasarathi.co.in> wrote:
>>=20
>> Hi all,
>>=20
>> RTP over TCP is unavoidable in case of RTCWeb media traffic has to =
traverse
>> through UDP blocking firewalls. TCP candidates with ICE (RFC 6544) =
may fail
>> due to the current OS implementation wherein TCP simultaneous Open =
will not
>> work.=20
>>=20
>> I have concern w.r.t TURN server as it introduces one extra network =
element
>> for RTCWeb session establishment. The current argument favoring for =
TURN
>> server is that RTP over TCP is required only till TURN server whereas =
the
>> media traffic between TURN server and the destination is UDP. In =
couple of
>> WebRTC deployment in Service provider network and Enterprise network, =
TURN
>> server will exist near to the destination and the WebRTC media =
traffic in
>> the internet is "RTP over TCP". I guess that Victor scenario falls =
under the
>> same category. In these deployment, RTP over TCP has advantage over =
TURN
>> over TCP as the extra element shall be avoided.=20
>>=20
>> Also, SCTP over DTLS over UDP will not work in case of RTCWeb media =
traffic
>> has to traverse through UDP blocking firewalls. So, there is a need =
of SCTP
>> over DTLS over TCP or multipath TCP kind of transport to meet this
>> requirement which needs separate discussion.=20
>>=20
>> Thanks
>> Partha
>>=20
>>> -----Original Message-----
>>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On =
Behalf
>>> Of Dan Wing
>>> Sent: Wednesday, September 04, 2013 1:47 AM
>>> To: Harald Alvestrand
>>> Cc: Bernard Aboba; pntaw@ietf.org
>>> Subject: Re: [pntaw] Real-time media over TCP
>>>=20
>>>=20
>>> On Sep 3, 2013, at 11:11 AM, Harald Alvestrand =
<harald@alvestrand.no>
>>> wrote:
>>>=20
>>>> On 09/03/2013 07:25 PM, Dan Wing wrote:
>>>>>> Multiple TCP connections seems like a suboptimal design, given =
the
>>> existence of other solutions like Minion or SCTP.
>>>>> Sure.  But those technologies weren't on the table when Victor did
>>> interactive audio/video over TCP, I'm sure.  Much like they weren't =
on
>>> the table when HTTP started doing multiple TCP connections back in =
the
>>> early days of Netscape.
>>>>=20
>>>> Victor didn't provide a date, so I was thinking "recently" - SCTP =
is
>>> 10 years old at this point.
>>>=20
>>> SCTP has been around a long time as a protocol but for a variety of
>>> reasons has seen no deployment on the Internet to date, including no
>>> availability in the mainstream OSs which is everyone's interest.  =
SCTP-
>>> over-UDP was only recently defined and its user-mode release was =
only
>>> 12 or 18 months ago or so.
>>>=20
>>>> Minion is newer than that, of course.
>>>>>=20
>>>>>> If both sides have TURN over TCP (or TURN over HTTP) enabled, and
>>> their respective TURN servers can talk UDP to each other, =
communication
>>> will occur, I think. I don't think we need to add TCP candidates for
>>> the TURN case in order to bypass firewalls.
>>>>>>=20
>>>>>> We might want to do so for the benefit of the pure peer-to-peer
>>> case, but I'm not sure it's a case that's important enough to make =
6062
>>> (TURN TCP allocations) or 6544 (ICE TCP allocations, no TURN server)
>>> into MUSTs for RTCWEB.
>>>>> I agree.  Additionally, before anyone ventures too far down that
>>> path it would be useful to understand how well the expected RTCWeb
>>> endpoints could do peer-to-peer TCP connections.  Reliable =
peer-to-peer
>>> TCP needs TCP simultaneous open needs to work well on both hosts, =
per
>>> the research by Saikat Guha and Paul Francis
>>> =
http://conferences.sigcomm.org/imc/2005/papers/imc05efiles/guha/guha.pd
>>> f.  In that research, they found Windows XP SP1 doesn't do =
simultaneous
>>> open well, but Windows XP with SP2 and SP3 and Linux worked okay.  I
>>> have not seen similar research for Android, OS X, or Windows 7 or
>>> Windows 8.
>>>> Indeed; that article seemed to indicate that the brand of NAT you
>>> bought was a decisive factor - it would be interesting to see if the
>>> state of the art has become more or less symmetric-TCP hostile in =
the
>>> intervening 8 years.
>>>=20
>>> -d
>>>=20
>>> _______________________________________________
>>> pntaw mailing list
>>> pntaw@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pntaw
>>=20
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw


From Michael.Tuexen@lurchi.franken.de  Mon Oct  7 13:14:24 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 E0A9821E8190 for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 13:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 lLJZ92+8Mg4h for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 13:14:24 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 4A45921E80BD for <pntaw@ietf.org>; Mon,  7 Oct 2013 13:14:22 -0700 (PDT)
Received: from [192.168.1.200] (p508F03E8.dip0.t-ipconnect.de [80.143.3.232]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 5475B1C0C0693; Mon,  7 Oct 2013 22:14:20 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <2924C1EA-613D-4B05-BD24-4CFD1411386E@cisco.com>
Date: Mon, 7 Oct 2013 22:14:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <28C05866-180F-41B2-8466-502F57FF1DF1@lurchi.franken.de>
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> <2924C1EA-613D-4B05-BD24-4CFD1411386E@cisco.com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1510)
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, Harald Alvestrand <harald@alvestrand.no>, "pntaw@ietf.org" <pntaw@ietf.org>, Parthasarathi R <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: Mon, 07 Oct 2013 20:14:25 -0000

On Oct 7, 2013, at 10:08 PM, Dan Wing <dwing@cisco.com> wrote:

>=20
> On Oct 7, 2013, at 11:32 AM, Bernard Aboba <bernard_aboba@hotmail.com> =
wrote:
>=20
>> As you point out, in most cases ICE-TCP will not avoid use of TURN, =
so we are only talking about a modest efficiency gain for ICE-TCP and =
RTP over TCP, but a substantial increase in complexity.=20
>>=20
>> Running SCTP over TCP is undesirable because the congestion control =
in SCTP and TCP will interact poorly with each other. =20
>=20
> And, even if a full SCTP stack is run over a full TCP stack, that will =
work but I agree won't work well.  But working is better than not =
working in situations where UDP is blocked.
>=20
> To work well, we might look at SCTP Minion =
(draft-iyengar-minion-concept, which disables TCP's congestion control =
in lieu of SCTP's congestion control) is one answer to those conflicting =
congestion controls.
This would either require changing the TCP stack in the kernel or using =
a
userland TCP stack without CC, which would require using a raw socket =
for
sending, for receiving some other strategy, both would require root =
privileges...
Or am I missing something?

Best regards
Michael
>=20
> -d
>=20
>=20
>=20
>=20
>>=20
>>> On Oct 7, 2013, at 11:07 AM, "Parthasarathi R" =
<partha@parthasarathi.co.in> wrote:
>>>=20
>>> Hi all,
>>>=20
>>> RTP over TCP is unavoidable in case of RTCWeb media traffic has to =
traverse
>>> through UDP blocking firewalls. TCP candidates with ICE (RFC 6544) =
may fail
>>> due to the current OS implementation wherein TCP simultaneous Open =
will not
>>> work.=20
>>>=20
>>> I have concern w.r.t TURN server as it introduces one extra network =
element
>>> for RTCWeb session establishment. The current argument favoring for =
TURN
>>> server is that RTP over TCP is required only till TURN server =
whereas the
>>> media traffic between TURN server and the destination is UDP. In =
couple of
>>> WebRTC deployment in Service provider network and Enterprise =
network, TURN
>>> server will exist near to the destination and the WebRTC media =
traffic in
>>> the internet is "RTP over TCP". I guess that Victor scenario falls =
under the
>>> same category. In these deployment, RTP over TCP has advantage over =
TURN
>>> over TCP as the extra element shall be avoided.=20
>>>=20
>>> Also, SCTP over DTLS over UDP will not work in case of RTCWeb media =
traffic
>>> has to traverse through UDP blocking firewalls. So, there is a need =
of SCTP
>>> over DTLS over TCP or multipath TCP kind of transport to meet this
>>> requirement which needs separate discussion.=20
>>>=20
>>> Thanks
>>> Partha
>>>=20
>>>> -----Original Message-----
>>>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On =
Behalf
>>>> Of Dan Wing
>>>> Sent: Wednesday, September 04, 2013 1:47 AM
>>>> To: Harald Alvestrand
>>>> Cc: Bernard Aboba; pntaw@ietf.org
>>>> Subject: Re: [pntaw] Real-time media over TCP
>>>>=20
>>>>=20
>>>> On Sep 3, 2013, at 11:11 AM, Harald Alvestrand =
<harald@alvestrand.no>
>>>> wrote:
>>>>=20
>>>>> On 09/03/2013 07:25 PM, Dan Wing wrote:
>>>>>>> Multiple TCP connections seems like a suboptimal design, given =
the
>>>> existence of other solutions like Minion or SCTP.
>>>>>> Sure.  But those technologies weren't on the table when Victor =
did
>>>> interactive audio/video over TCP, I'm sure.  Much like they weren't =
on
>>>> the table when HTTP started doing multiple TCP connections back in =
the
>>>> early days of Netscape.
>>>>>=20
>>>>> Victor didn't provide a date, so I was thinking "recently" - SCTP =
is
>>>> 10 years old at this point.
>>>>=20
>>>> SCTP has been around a long time as a protocol but for a variety of
>>>> reasons has seen no deployment on the Internet to date, including =
no
>>>> availability in the mainstream OSs which is everyone's interest.  =
SCTP-
>>>> over-UDP was only recently defined and its user-mode release was =
only
>>>> 12 or 18 months ago or so.
>>>>=20
>>>>> Minion is newer than that, of course.
>>>>>>=20
>>>>>>> If both sides have TURN over TCP (or TURN over HTTP) enabled, =
and
>>>> their respective TURN servers can talk UDP to each other, =
communication
>>>> will occur, I think. I don't think we need to add TCP candidates =
for
>>>> the TURN case in order to bypass firewalls.
>>>>>>>=20
>>>>>>> We might want to do so for the benefit of the pure peer-to-peer
>>>> case, but I'm not sure it's a case that's important enough to make =
6062
>>>> (TURN TCP allocations) or 6544 (ICE TCP allocations, no TURN =
server)
>>>> into MUSTs for RTCWEB.
>>>>>> I agree.  Additionally, before anyone ventures too far down that
>>>> path it would be useful to understand how well the expected RTCWeb
>>>> endpoints could do peer-to-peer TCP connections.  Reliable =
peer-to-peer
>>>> TCP needs TCP simultaneous open needs to work well on both hosts, =
per
>>>> the research by Saikat Guha and Paul Francis
>>>> =
http://conferences.sigcomm.org/imc/2005/papers/imc05efiles/guha/guha.pd
>>>> f.  In that research, they found Windows XP SP1 doesn't do =
simultaneous
>>>> open well, but Windows XP with SP2 and SP3 and Linux worked okay.  =
I
>>>> have not seen similar research for Android, OS X, or Windows 7 or
>>>> Windows 8.
>>>>> Indeed; that article seemed to indicate that the brand of NAT you
>>>> bought was a decisive factor - it would be interesting to see if =
the
>>>> state of the art has become more or less symmetric-TCP hostile in =
the
>>>> intervening 8 years.
>>>>=20
>>>> -d
>>>>=20
>>>> _______________________________________________
>>>> pntaw mailing list
>>>> pntaw@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pntaw
>>>=20
>>> _______________________________________________
>>> pntaw mailing list
>>> pntaw@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pntaw
>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw
>=20


From dwing@cisco.com  Mon Oct  7 13:34:33 2013
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 3C47811E8138 for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 13:34: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=[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 IlM-16CbCc31 for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 13:34:29 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 870BF11E814C for <pntaw@ietf.org>; Mon,  7 Oct 2013 13:34:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6735; q=dns/txt; s=iport; t=1381178066; x=1382387666; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=YcPU0yR/HtkNWcFJ/9YTsOIK6193Hfe+9g5h405gKLk=; b=Kzrd2MLt03/SEiNBXHlMnyvCWYHw3R5k5PwaiNR6SL/1McVRnqPml8PF Y+XkoSpuoJwscCifyoXG8qFGmpZcjjh4y35/2Tq1TYIx6ndbRgK/w2EXE +41Sbvrnv3pbU7Z1kvibTQ4ZV4buQewqtjFYF8YnUm3KzT1M1Q6NUckDP Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFANcZU1KrRDoJ/2dsb2JhbABZgwc4rxySV4EiFnSCJQEBAQMBAQEBNy4EAggDBQcECxEEAQEBJwcnHwMBBQgGExuHWQMJBQ27I4xmgjgzBwaDGYEEA4k5imuBdYFogS+LG4U2g0Qc
X-IronPort-AV: E=Sophos;i="4.90,1051,1371081600"; d="scan'208";a="91575410"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 07 Oct 2013 20:34:25 +0000
Received: from sjc-vpn5-197.cisco.com (sjc-vpn5-197.cisco.com [10.21.88.197]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r97KYOrV006260; Mon, 7 Oct 2013 20:34:24 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: <28C05866-180F-41B2-8466-502F57FF1DF1@lurchi.franken.de>
Date: Mon, 7 Oct 2013 13:34:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <AFD4485E-B51C-4ADF-A89D-FDF50AB96894@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> <2924C1EA-613D-4B05-BD24-4CFD1411386E@cisco.com> <28C05866-180F-41B2-8466-502F57FF1DF1@lurchi.franken.de>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1510)
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, Harald Alvestrand <harald@alvestrand.no>, "pntaw@ietf.org" <pntaw@ietf.org>, Parthasarathi R <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: Mon, 07 Oct 2013 20:34:33 -0000

On Oct 7, 2013, at 1:14 PM, Michael Tuexen =
<Michael.Tuexen@lurchi.franken.de> wrote:

> On Oct 7, 2013, at 10:08 PM, Dan Wing <dwing@cisco.com> wrote:
>=20
>>=20
>> On Oct 7, 2013, at 11:32 AM, Bernard Aboba =
<bernard_aboba@hotmail.com> wrote:
>>=20
>>> As you point out, in most cases ICE-TCP will not avoid use of TURN, =
so we are only talking about a modest efficiency gain for ICE-TCP and =
RTP over TCP, but a substantial increase in complexity.=20
>>>=20
>>> Running SCTP over TCP is undesirable because the congestion control =
in SCTP and TCP will interact poorly with each other. =20
>>=20
>> And, even if a full SCTP stack is run over a full TCP stack, that =
will work but I agree won't work well.  But working is better than not =
working in situations where UDP is blocked.
>>=20
>> To work well, we might look at SCTP Minion =
(draft-iyengar-minion-concept, which disables TCP's congestion control =
in lieu of SCTP's congestion control) is one answer to those conflicting =
congestion controls.
> This would either require changing the TCP stack in the kernel or =
using a
> userland TCP stack without CC, which would require using a raw socket =
for
> sending, for receiving some other strategy, both would require root =
privileges...
> Or am I missing something?

Yes, start with something that works but is not optimal (SCTP over TCP) =
and expect/hope that one of the future paths are better:  OS vendors =
provide native SCTP support and networks support native SCTP, UDP is =
permitted by networks (allowing SCTP-over-UDP to work without competing =
CC), or OS vendors support SCTP Minion (which also avoids competing CC).

-d


>=20
> Best regards
> Michael
>>=20
>> -d
>>=20
>>=20
>>=20
>>=20
>>>=20
>>>> On Oct 7, 2013, at 11:07 AM, "Parthasarathi R" =
<partha@parthasarathi.co.in> wrote:
>>>>=20
>>>> Hi all,
>>>>=20
>>>> RTP over TCP is unavoidable in case of RTCWeb media traffic has to =
traverse
>>>> through UDP blocking firewalls. TCP candidates with ICE (RFC 6544) =
may fail
>>>> due to the current OS implementation wherein TCP simultaneous Open =
will not
>>>> work.=20
>>>>=20
>>>> I have concern w.r.t TURN server as it introduces one extra network =
element
>>>> for RTCWeb session establishment. The current argument favoring for =
TURN
>>>> server is that RTP over TCP is required only till TURN server =
whereas the
>>>> media traffic between TURN server and the destination is UDP. In =
couple of
>>>> WebRTC deployment in Service provider network and Enterprise =
network, TURN
>>>> server will exist near to the destination and the WebRTC media =
traffic in
>>>> the internet is "RTP over TCP". I guess that Victor scenario falls =
under the
>>>> same category. In these deployment, RTP over TCP has advantage over =
TURN
>>>> over TCP as the extra element shall be avoided.=20
>>>>=20
>>>> Also, SCTP over DTLS over UDP will not work in case of RTCWeb media =
traffic
>>>> has to traverse through UDP blocking firewalls. So, there is a need =
of SCTP
>>>> over DTLS over TCP or multipath TCP kind of transport to meet this
>>>> requirement which needs separate discussion.=20
>>>>=20
>>>> Thanks
>>>> Partha
>>>>=20
>>>>> -----Original Message-----
>>>>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On =
Behalf
>>>>> Of Dan Wing
>>>>> Sent: Wednesday, September 04, 2013 1:47 AM
>>>>> To: Harald Alvestrand
>>>>> Cc: Bernard Aboba; pntaw@ietf.org
>>>>> Subject: Re: [pntaw] Real-time media over TCP
>>>>>=20
>>>>>=20
>>>>> On Sep 3, 2013, at 11:11 AM, Harald Alvestrand =
<harald@alvestrand.no>
>>>>> wrote:
>>>>>=20
>>>>>> On 09/03/2013 07:25 PM, Dan Wing wrote:
>>>>>>>> Multiple TCP connections seems like a suboptimal design, given =
the
>>>>> existence of other solutions like Minion or SCTP.
>>>>>>> Sure.  But those technologies weren't on the table when Victor =
did
>>>>> interactive audio/video over TCP, I'm sure.  Much like they =
weren't on
>>>>> the table when HTTP started doing multiple TCP connections back in =
the
>>>>> early days of Netscape.
>>>>>>=20
>>>>>> Victor didn't provide a date, so I was thinking "recently" - SCTP =
is
>>>>> 10 years old at this point.
>>>>>=20
>>>>> SCTP has been around a long time as a protocol but for a variety =
of
>>>>> reasons has seen no deployment on the Internet to date, including =
no
>>>>> availability in the mainstream OSs which is everyone's interest.  =
SCTP-
>>>>> over-UDP was only recently defined and its user-mode release was =
only
>>>>> 12 or 18 months ago or so.
>>>>>=20
>>>>>> Minion is newer than that, of course.
>>>>>>>=20
>>>>>>>> If both sides have TURN over TCP (or TURN over HTTP) enabled, =
and
>>>>> their respective TURN servers can talk UDP to each other, =
communication
>>>>> will occur, I think. I don't think we need to add TCP candidates =
for
>>>>> the TURN case in order to bypass firewalls.
>>>>>>>>=20
>>>>>>>> We might want to do so for the benefit of the pure peer-to-peer
>>>>> case, but I'm not sure it's a case that's important enough to make =
6062
>>>>> (TURN TCP allocations) or 6544 (ICE TCP allocations, no TURN =
server)
>>>>> into MUSTs for RTCWEB.
>>>>>>> I agree.  Additionally, before anyone ventures too far down that
>>>>> path it would be useful to understand how well the expected RTCWeb
>>>>> endpoints could do peer-to-peer TCP connections.  Reliable =
peer-to-peer
>>>>> TCP needs TCP simultaneous open needs to work well on both hosts, =
per
>>>>> the research by Saikat Guha and Paul Francis
>>>>> =
http://conferences.sigcomm.org/imc/2005/papers/imc05efiles/guha/guha.pd
>>>>> f.  In that research, they found Windows XP SP1 doesn't do =
simultaneous
>>>>> open well, but Windows XP with SP2 and SP3 and Linux worked okay.  =
I
>>>>> have not seen similar research for Android, OS X, or Windows 7 or
>>>>> Windows 8.
>>>>>> Indeed; that article seemed to indicate that the brand of NAT you
>>>>> bought was a decisive factor - it would be interesting to see if =
the
>>>>> state of the art has become more or less symmetric-TCP hostile in =
the
>>>>> intervening 8 years.
>>>>>=20
>>>>> -d
>>>>>=20
>>>>> _______________________________________________
>>>>> pntaw mailing list
>>>>> pntaw@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/pntaw
>>>>=20
>>>> _______________________________________________
>>>> pntaw mailing list
>>>> pntaw@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pntaw
>>=20
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
>>=20
>=20


From harald@alvestrand.no  Mon Oct  7 21:09:46 2013
Return-Path: <harald@alvestrand.no>
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 CAECD21E8141 for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 21:09:46 -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=[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 LFDuzrmWXVJY for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 21:09:41 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 7C59021E81B7 for <pntaw@ietf.org>; Mon,  7 Oct 2013 21:09:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1762139E085; Tue,  8 Oct 2013 06:09:38 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5mK3a4BVP8Ka; Tue,  8 Oct 2013 06:09:37 +0200 (CEST)
Received: from [10.59.4.97] (unknown [212.91.240.155]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id CE2D339E070; Tue,  8 Oct 2013 06:09:36 +0200 (CEST)
Message-ID: <5253857F.6010802@alvestrand.no>
Date: Tue, 08 Oct 2013 06:09:35 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>,  Dan Wing <dwing@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> <2924C1EA-613D-4B05-BD24-4CFD1411386E@cisco.com> <28C05866-180F-41B2-8466-502F57FF1DF1@lurchi.franken.de>
In-Reply-To: <28C05866-180F-41B2-8466-502F57FF1DF1@lurchi.franken.de>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "pntaw@ietf.org" <pntaw@ietf.org>, Parthasarathi R <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, 08 Oct 2013 04:09:46 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/07/2013 10:14 PM, Michael Tuexen wrote:
> On Oct 7, 2013, at 10:08 PM, Dan Wing <dwing@cisco.com> wrote:
>
>>
>> On Oct 7, 2013, at 11:32 AM, Bernard Aboba
<bernard_aboba@hotmail.com> wrote:
>>
>>> As you point out, in most cases ICE-TCP will not avoid use of TURN,
so we are only talking about a modest efficiency gain for ICE-TCP and
RTP over TCP, but a substantial increase in complexity.
>>>
>>> Running SCTP over TCP is undesirable because the congestion control
in SCTP and TCP will interact poorly with each other. 
>>
>> And, even if a full SCTP stack is run over a full TCP stack, that
will work but I agree won't work well.  But working is better than not
working in situations where UDP is blocked.
>>
>> To work well, we might look at SCTP Minion
(draft-iyengar-minion-concept, which disables TCP's congestion control
in lieu of SCTP's congestion control) is one answer to those conflicting
congestion controls.
> This would either require changing the TCP stack in the kernel or using a
> userland TCP stack without CC, which would require using a raw socket for
> sending, for receiving some other strategy, both would require root
privileges...
> Or am I missing something?

If I remember the minion overview correctly, it will in fact work on an
unmodified TCP stack, but if there are ioctls available to get frames
out of order, it can work a good deal better.

But you should get Iengar himself to talk about it if it's of interest.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSU4V/AAoJEIjUFboxkRizAkQH/ixIr8I/pd/hb9FCdvJv9IaT
3Rgp/nYIQdaEUOdZNjdTFuoSU9ruhQ5G+Wd8PouDwS+8hdy8Dry/AOYbNxHrRjdO
4lvyLslOIwksOjMmkJ198RFzQTzvNjsCJQaDhmf/kMaZ0r1KF3lDjWXCzOPRetLs
fy+5nuzzuLrInG4rqkMX2nX4J5endXYxUoX8BOclDjm33YfxPw0/bJHQNE0Iq9Oi
mmw1zf8fzTze/ilqlEpFHv9T/CWGCQGoKinzUbWscOUZNpzPGnur/9pqfQTgMkL/
QWQcKuy2T7QxzIwMF9vz7xHfJvzDxD8fS9Fy1t65LScqFBnppR0qQrlxhYvnu+I=
=W/ti
-----END PGP SIGNATURE-----


From harald@alvestrand.no  Mon Oct  7 21:32:17 2013
Return-Path: <harald@alvestrand.no>
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 7DB3D21E81F9 for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 21:32:17 -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=[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 ZmuVtwyus5DH for <pntaw@ietfa.amsl.com>; Mon,  7 Oct 2013 21:32:11 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id B8F7A21E81F5 for <pntaw@ietf.org>; Mon,  7 Oct 2013 21:32:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 8AC1039E085 for <pntaw@ietf.org>; Tue,  8 Oct 2013 06:32:07 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lK2qiMbLEels for <pntaw@ietf.org>; Tue,  8 Oct 2013 06:32:06 +0200 (CEST)
Received: from [10.59.4.97] (unknown [212.91.240.155]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id EDFED39E070 for <pntaw@ietf.org>; Tue,  8 Oct 2013 06:32:05 +0200 (CEST)
Message-ID: <52538AC4.5060500@alvestrand.no>
Date: Tue, 08 Oct 2013 06:32:04 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
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>
In-Reply-To: <00ca01cec387$f881cae0$e98560a0$@co.in>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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 04:32:17 -0000

On 10/07/2013 08:06 PM, Parthasarathi R wrote:
> Hi all,
>
> RTP over TCP is unavoidable in case of RTCWeb media traffic has to traverse
> through UDP blocking firewalls. TCP candidates with ICE (RFC 6544) may fail
> due to the current OS implementation wherein TCP simultaneous Open will not
> work. 
>
> I have concern w.r.t TURN server as it introduces one extra network element
> for RTCWeb session establishment. The current argument favoring for TURN
> server is that RTP over TCP is required only till TURN server whereas the
> media traffic between TURN server and the destination is UDP.

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



From Michael.Tuexen@lurchi.franken.de  Tue Oct  8 05:39:00 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 60BC711E8197 for <pntaw@ietfa.amsl.com>; Tue,  8 Oct 2013 05:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 SR1-fF1KNzTd for <pntaw@ietfa.amsl.com>; Tue,  8 Oct 2013 05:38:59 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 995D921E8082 for <pntaw@ietf.org>; Tue,  8 Oct 2013 05:38:52 -0700 (PDT)
Received: from [192.168.1.200] (p508F3A21.dip0.t-ipconnect.de [80.143.58.33]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 5874E1C0C0693; Tue,  8 Oct 2013 14:38:48 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <5253857F.6010802@alvestrand.no>
Date: Tue, 8 Oct 2013 14:38:48 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <AC0ADD1C-C99C-4B62-BE0E-D52A2C7093A9@lurchi.franken.de>
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> <2924C1EA-613D-4B05-BD24-4CFD1411386E@cisco.com> <28C05866-180F-41B2-8466-502F57FF1DF1@lurchi.franken.de> <5253857F.6010802@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.1510)
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "pntaw@ietf.org" <pntaw@ietf.org>, Parthasarathi R <partha@parthasarathi.co.in>, Dan Wing <dwing@cisco.com>
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 12:39:00 -0000

On Oct 8, 2013, at 6:09 AM, Harald Alvestrand <harald@alvestrand.no> wrote:

> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 10/07/2013 10:14 PM, Michael Tuexen wrote:
>> On Oct 7, 2013, at 10:08 PM, Dan Wing <dwing@cisco.com> wrote:
>> 
>>> 
>>> On Oct 7, 2013, at 11:32 AM, Bernard Aboba
> <bernard_aboba@hotmail.com> wrote:
>>> 
>>>> As you point out, in most cases ICE-TCP will not avoid use of TURN,
> so we are only talking about a modest efficiency gain for ICE-TCP and
> RTP over TCP, but a substantial increase in complexity.
>>>> 
>>>> Running SCTP over TCP is undesirable because the congestion control
> in SCTP and TCP will interact poorly with each other. 
>>> 
>>> And, even if a full SCTP stack is run over a full TCP stack, that
> will work but I agree won't work well.  But working is better than not
> working in situations where UDP is blocked.
>>> 
>>> To work well, we might look at SCTP Minion
> (draft-iyengar-minion-concept, which disables TCP's congestion control
> in lieu of SCTP's congestion control) is one answer to those conflicting
> congestion controls.
>> This would either require changing the TCP stack in the kernel or using a
>> userland TCP stack without CC, which would require using a raw socket for
>> sending, for receiving some other strategy, both would require root
> privileges...
>> Or am I missing something?
> 
> If I remember the minion overview correctly, it will in fact work on an
> unmodified TCP stack, but if there are ioctls available to get frames
> out of order, it can work a good deal better.
> 
> But you should get Iengar himself to talk about it if it's of interest.
His point is that you can work with an unchanged stack, but don't
get any benefit. The point in the above is to use a TCP without CC,
which requires an end-host change. So it is not so easy to get rid
of the TCP CC when using a kernel TCP stack.

Best regards
Michael
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iQEcBAEBAgAGBQJSU4V/AAoJEIjUFboxkRizAkQH/ixIr8I/pd/hb9FCdvJv9IaT
> 3Rgp/nYIQdaEUOdZNjdTFuoSU9ruhQ5G+Wd8PouDwS+8hdy8Dry/AOYbNxHrRjdO
> 4lvyLslOIwksOjMmkJ198RFzQTzvNjsCJQaDhmf/kMaZ0r1KF3lDjWXCzOPRetLs
> fy+5nuzzuLrInG4rqkMX2nX4J5endXYxUoX8BOclDjm33YfxPw0/bJHQNE0Iq9Oi
> mmw1zf8fzTze/ilqlEpFHv9T/CWGCQGoKinzUbWscOUZNpzPGnur/9pqfQTgMkL/
> QWQcKuy2T7QxzIwMF9vz7xHfJvzDxD8fS9Fy1t65LScqFBnppR0qQrlxhYvnu+I=
> =W/ti
> -----END PGP SIGNATURE-----
> 
> 


From dwing@cisco.com  Tue Oct  8 08:04:28 2013
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 83A3521E80F0 for <pntaw@ietfa.amsl.com>; Tue,  8 Oct 2013 08:04:28 -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=[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 Kj7+DxpD37f8 for <pntaw@ietfa.amsl.com>; Tue,  8 Oct 2013 08:04:23 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 51A0021E81C0 for <pntaw@ietf.org>; Tue,  8 Oct 2013 08:04:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2874; q=dns/txt; s=iport; t=1381244644; x=1382454244; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=lI4OiUqcbhKt2dfzAYT/IZOGVMbbvxZZc5u6d+lQ++k=; b=R5l0aDZUyHhmQ2lU9YbsD0/I4Qk99dKAT/vpV0rnO40JXAZ8747sjkc/ 2uY0ooPK1aITtEJH32ZFDlzIDiTu3qA+OpguMspx8Us/+4eH3TQaPCadV M1WDOiaUPmu882aOKtBq4tyl8mg74o98rNJiLUT4xJIO06qKJgc8Nm8mM g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAMMdVFKrRDoH/2dsb2JhbABZgwc4rx6SV4EeFnSCJQEBAQMBbAoDBQsLGC5XBhOHdAMJBbpdjFeCODMHgx+BBAOJOYprgXWBaIxKhTaDRBw
X-IronPort-AV: E=Sophos;i="4.90,1056,1371081600"; d="scan'208";a="94169477"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 08 Oct 2013 15:04:03 +0000
Received: from sjc-vpn4-1389.cisco.com (sjc-vpn4-1389.cisco.com [10.21.85.108]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r98F42Wa018390; Tue, 8 Oct 2013 15:04:02 GMT
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <AC0ADD1C-C99C-4B62-BE0E-D52A2C7093A9@lurchi.franken.de>
Date: Tue, 8 Oct 2013 08:04:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <16DC7356-9D5F-4C87-A828-19B407DCCB27@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> <2924C1EA-613D-4B05-BD24-4CFD1411386E@cisco.com> <28C05866-180F-41B2-8466-502F57FF1DF1@lurchi.franken.de> <5253857F.6010802@alvestrand.no> <AC0ADD1C-C99C-4B62-BE0E-D52A2C7093A9@lurchi.franken.de>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1510)
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, Harald Alvestrand <harald@alvestrand.no>, "pntaw@ietf.org" <pntaw@ietf.org>, Parthasarathi R <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, 08 Oct 2013 15:04:28 -0000

On Oct 8, 2013, at 5:38 AM, Michael Tuexen =
<Michael.Tuexen@lurchi.franken.de> wrote:

> On Oct 8, 2013, at 6:09 AM, Harald Alvestrand <harald@alvestrand.no> =
wrote:
>=20
>>=20
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>=20
>> On 10/07/2013 10:14 PM, Michael Tuexen wrote:
>>> On Oct 7, 2013, at 10:08 PM, Dan Wing <dwing@cisco.com> wrote:
>>>=20
>>>>=20
>>>> On Oct 7, 2013, at 11:32 AM, Bernard Aboba
>> <bernard_aboba@hotmail.com> wrote:
>>>>=20
>>>>> As you point out, in most cases ICE-TCP will not avoid use of =
TURN,
>> so we are only talking about a modest efficiency gain for ICE-TCP and
>> RTP over TCP, but a substantial increase in complexity.
>>>>>=20
>>>>> Running SCTP over TCP is undesirable because the congestion =
control
>> in SCTP and TCP will interact poorly with each other.=20
>>>>=20
>>>> And, even if a full SCTP stack is run over a full TCP stack, that
>> will work but I agree won't work well.  But working is better than =
not
>> working in situations where UDP is blocked.
>>>>=20
>>>> To work well, we might look at SCTP Minion
>> (draft-iyengar-minion-concept, which disables TCP's congestion =
control
>> in lieu of SCTP's congestion control) is one answer to those =
conflicting
>> congestion controls.
>>> This would either require changing the TCP stack in the kernel or =
using a
>>> userland TCP stack without CC, which would require using a raw =
socket for
>>> sending, for receiving some other strategy, both would require root
>> privileges...
>>> Or am I missing something?
>>=20
>> If I remember the minion overview correctly, it will in fact work on =
an
>> unmodified TCP stack, but if there are ioctls available to get frames
>> out of order, it can work a good deal better.
>>=20
>> But you should get Iengar himself to talk about it if it's of =
interest.
> His point is that you can work with an unchanged stack, but don't
> get any benefit.

The application sees SCTP -- that must have some benefit.

-d


> The point in the above is to use a TCP without CC,
> which requires an end-host change. So it is not so easy to get rid
> of the TCP CC when using a kernel TCP stack.
>=20
> Best regards
> Michael
>>=20
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>=20
>> iQEcBAEBAgAGBQJSU4V/AAoJEIjUFboxkRizAkQH/ixIr8I/pd/hb9FCdvJv9IaT
>> 3Rgp/nYIQdaEUOdZNjdTFuoSU9ruhQ5G+Wd8PouDwS+8hdy8Dry/AOYbNxHrRjdO
>> 4lvyLslOIwksOjMmkJ198RFzQTzvNjsCJQaDhmf/kMaZ0r1KF3lDjWXCzOPRetLs
>> fy+5nuzzuLrInG4rqkMX2nX4J5endXYxUoX8BOclDjm33YfxPw0/bJHQNE0Iq9Oi
>> mmw1zf8fzTze/ilqlEpFHv9T/CWGCQGoKinzUbWscOUZNpzPGnur/9pqfQTgMkL/
>> QWQcKuy2T7QxzIwMF9vz7xHfJvzDxD8fS9Fy1t65LScqFBnppR0qQrlxhYvnu+I=3D
>> =3DW/ti
>> -----END PGP SIGNATURE-----
>>=20
>>=20
>=20


From partha@parthasarathi.co.in  Tue Oct  8 10:53:35 2013
Return-Path: <partha@parthasarathi.co.in>
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 6123721E80BE for <pntaw@ietfa.amsl.com>; Tue,  8 Oct 2013 10:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.211
X-Spam-Level: 
X-Spam-Status: No, score=-1.211 tagged_above=-999 required=5 tests=[AWL=0.435,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_SORBS_WEB=0.619]
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 gYiLwdVzy2u4 for <pntaw@ietfa.amsl.com>; Tue,  8 Oct 2013 10:53:31 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us2.mailhostbox.com [69.93.141.234]) by ietfa.amsl.com (Postfix) with ESMTP id 9331D21E826D for <pntaw@ietf.org>; Tue,  8 Oct 2013 10:53:08 -0700 (PDT)
Received: from userPC (unknown [122.178.217.175]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id 5CB186395C1; Tue,  8 Oct 2013 17:52:52 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1381254777; bh=rMT8koNNI14N37dsXKWitodRxDZTld9cYzHU3S8L1vA=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=RYaR5w2Q9kvjEoISwYTolPXgfwE+TNJbbv9lsAAAhyiF1rL1CQzv3AVZwBXH/JzDN d6GFUSSdpHYBLtfkA/nC2ktr1ntKh4x5rsL6AASxdKrJ8dc8SuuWhSDws9PkxBEwnA 0znmsvC531scNQTf9IVeNQ8rN0Fl9yTbSAK+fKoY=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Bernard Aboba'" <bernard_aboba@hotmail.com>, "'Harald Alvestrand'" <harald@alvestrand.no>
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>
In-Reply-To: <BLU406-EAS274696C3D9DFE505F96B8E393130@phx.gbl>
Date: Tue, 8 Oct 2013 23:22:46 +0530
Message-ID: <004201cec44f$381a47f0$a84ed7d0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac7Di6NsQ2sl7Ad7Tsih2B5CdgVCfwAwNE/w
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020208.52544679.0080, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.142
Cc: pntaw@ietf.org, 'Dan Wing' <dwing@cisco.com>
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 17:53:35 -0000

Hi Bernard/Harald,

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.

Thanks
Partha

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of Bernard Aboba
> Sent: Tuesday, October 08, 2013 12:03 AM
> To: Parthasarathi R
> Cc: Harald Alvestrand; pntaw@ietf.org; Dan Wing
> Subject: Re: [pntaw] Real-time media over TCP
> 
> As you point out, in most cases ICE-TCP will not avoid use of TURN, so
> we are only talking about a modest efficiency gain for ICE-TCP and RTP
> over TCP, but a substantial increase in complexity.
> 
> Running SCTP over TCP is undesirable because the congestion control in
> SCTP and TCP will interact poorly with each other.
> 
> > On Oct 7, 2013, at 11:07 AM, "Parthasarathi R"
> <partha@parthasarathi.co.in> wrote:
> >
> > Hi all,
> >
> > RTP over TCP is unavoidable in case of RTCWeb media traffic has to
> traverse
> > through UDP blocking firewalls. TCP candidates with ICE (RFC 6544)
> may fail
> > due to the current OS implementation wherein TCP simultaneous Open
> will not
> > work.
> >
> > I have concern w.r.t TURN server as it introduces one extra network
> element
> > for RTCWeb session establishment. The current argument favoring for
> TURN
> > server is that RTP over TCP is required only till TURN server whereas
> the
> > media traffic between TURN server and the destination is UDP. In
> couple of
> > WebRTC deployment in Service provider network and Enterprise network,
> TURN
> > server will exist near to the destination and the WebRTC media
> traffic in
> > the internet is "RTP over TCP". I guess that Victor scenario falls
> under the
> > same category. In these deployment, RTP over TCP has advantage over
> TURN
> > over TCP as the extra element shall be avoided.
> >
> > Also, SCTP over DTLS over UDP will not work in case of RTCWeb media
> traffic
> > has to traverse through UDP blocking firewalls. So, there is a need
> of SCTP
> > over DTLS over TCP or multipath TCP kind of transport to meet this
> > requirement which needs separate discussion.
> >
> > Thanks
> > Partha
> >
> >> -----Original Message-----
> >> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> Behalf
> >> Of Dan Wing
> >> Sent: Wednesday, September 04, 2013 1:47 AM
> >> To: Harald Alvestrand
> >> Cc: Bernard Aboba; pntaw@ietf.org
> >> Subject: Re: [pntaw] Real-time media over TCP
> >>
> >>
> >> On Sep 3, 2013, at 11:11 AM, Harald Alvestrand
> <harald@alvestrand.no>
> >> wrote:
> >>
> >>> On 09/03/2013 07:25 PM, Dan Wing wrote:
> >>>>> Multiple TCP connections seems like a suboptimal design, given
> the
> >> existence of other solutions like Minion or SCTP.
> >>>> Sure.  But those technologies weren't on the table when Victor did
> >> interactive audio/video over TCP, I'm sure.  Much like they weren't
> on
> >> the table when HTTP started doing multiple TCP connections back in
> the
> >> early days of Netscape.
> >>>
> >>> Victor didn't provide a date, so I was thinking "recently" - SCTP
> is
> >> 10 years old at this point.
> >>
> >> SCTP has been around a long time as a protocol but for a variety of
> >> reasons has seen no deployment on the Internet to date, including no
> >> availability in the mainstream OSs which is everyone's interest.
> SCTP-
> >> over-UDP was only recently defined and its user-mode release was
> only
> >> 12 or 18 months ago or so.
> >>
> >>> Minion is newer than that, of course.
> >>>>
> >>>>> If both sides have TURN over TCP (or TURN over HTTP) enabled, and
> >> their respective TURN servers can talk UDP to each other,
> communication
> >> will occur, I think. I don't think we need to add TCP candidates for
> >> the TURN case in order to bypass firewalls.
> >>>>>
> >>>>> We might want to do so for the benefit of the pure peer-to-peer
> >> case, but I'm not sure it's a case that's important enough to make
> 6062
> >> (TURN TCP allocations) or 6544 (ICE TCP allocations, no TURN server)
> >> into MUSTs for RTCWEB.
> >>>> I agree.  Additionally, before anyone ventures too far down that
> >> path it would be useful to understand how well the expected RTCWeb
> >> endpoints could do peer-to-peer TCP connections.  Reliable peer-to-
> peer
> >> TCP needs TCP simultaneous open needs to work well on both hosts,
> per
> >> the research by Saikat Guha and Paul Francis
> >>
> http://conferences.sigcomm.org/imc/2005/papers/imc05efiles/guha/guha.pd
> >> f.  In that research, they found Windows XP SP1 doesn't do
> simultaneous
> >> open well, but Windows XP with SP2 and SP3 and Linux worked okay.  I
> >> have not seen similar research for Android, OS X, or Windows 7 or
> >> Windows 8.
> >>> Indeed; that article seemed to indicate that the brand of NAT you
> >> bought was a decisive factor - it would be interesting to see if the
> >> state of the art has become more or less symmetric-TCP hostile in
> the
> >> intervening 8 years.
> >>
> >> -d
> >>
> >> _______________________________________________
> >> pntaw mailing list
> >> pntaw@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pntaw
> >
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From simon.perreault@viagenie.ca  Tue Oct  8 11:25:26 2013
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

From pkyzivat@alum.mit.edu  Wed Oct  9 09:01:52 2013
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


From partha@parthasarathi.co.in  Wed Oct  9 10:02:13 2013
Return-Path: <partha@parthasarathi.co.in>
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 286F921E80A5 for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 10:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 1fZOe20jcrd5 for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 10:02:02 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us3.mailhostbox.com [70.87.28.154]) by ietfa.amsl.com (Postfix) with ESMTP id 77ECD21E809D for <pntaw@ietf.org>; Wed,  9 Oct 2013 10:01:20 -0700 (PDT)
Received: from userPC (unknown [122.172.188.193]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id 1C82914D823C; Wed,  9 Oct 2013 17:01:11 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1381338074; bh=ZH16iGt5Ep1vpwdu1ixa/zTMlhW1CxIr17HGvdDMJZI=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=YR3rxGqGUtTKNJh48eGdlrwS74jtIGeDNdH5TP4O/imttZSlWsEJzmO8Qe5TJ8gML vAk+lppvTQ0QPh6J3n4ON1KnJUtaNeO3Ue1UWIGnXuQroeuaG7WEE0gxoKDc4hUByb jxTOhcou1577pZWQ8YZe6RRdSrU/AE/fnst4hQzY=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Simon Perreault'" <simon.perreault@viagenie.ca>, <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> <52544E0E.5080405@viagenie.ca>
In-Reply-To: <52544E0E.5080405@viagenie.ca>
Date: Wed, 9 Oct 2013 22:31:06 +0530
Message-ID: <003b01cec511$27e1abe0$77a503a0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac7EU8SYNHwGb3I9RDK9g8AD3JEIJAAu9KNQ
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020209.52558BDA.00E1, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.155
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 17:02:19 -0000

Hi Simon,

I have seen only two requirements in
draft-ietf-rtcweb-use-cases-and-requirements-11, NAT/FW that blocks UDP =
and
FW that only allows http. The relevant draft snippet is attached as a =
note
of this mail. I'm discussing about NAT/FW that blocks UDP requirement. =
In
case you foresee that the requirement is not detailed now, we need to =
sort
out the requirement first before discussion the solutions.

Regards
Partha

PS: In draft-ietf-rtcweb-use-cases-and-requirements-11 snippet,

3.2.2.  Simple Video Communication Service, NAT/FW that blocks UDP

3.2.2.1.  Description

   This use-case is almost identical to the Simple Video Communication
   Service use-case (Section 3.2.1).  The difference is that one of the
   users is behind a NAT that blocks UDP traffic.

3.2.3.  Simple Video Communication Service, FW that only allows http

3.2.3.1.  Description

   This use-case is almost identical to the Simple Video Communication
   Service use-case (Section 3.2.1).  The difference is that one of the
   users is behind a FW that only allows http traffic.

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of Simon Perreault
> Sent: Tuesday, October 08, 2013 11:55 PM
> To: pntaw@ietf.org
> Subject: Re: [pntaw] Real-time media over TCP
>=20
> Le 2013-10-08 19:52, Parthasarathi R a =E9crit :
> > 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.
>=20
> A firewall that blocks UDP but allows incoming TCP is not very common,
> is it?
>=20
> Or did I miss something?
>=20
> 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
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From Markus.Isomaki@nokia.com  Wed Oct  9 10:36:59 2013
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 52E6421E814A for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 10:36:59 -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 e-rK-pfdCaXJ for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 10:36:54 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 951B421E805F for <pntaw@ietf.org>; Wed,  9 Oct 2013 10:36:54 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.26]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r99HTtZN021602 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 9 Oct 2013 20:29:55 +0300
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([169.254.2.224]) by 008-AM1MMR1-010.mgdnok.nokia.com ([65.54.30.26]) with mapi id 14.03.0136.001; Wed, 9 Oct 2013 17:29:54 +0000
From: <Markus.Isomaki@nokia.com>
To: <partha@parthasarathi.co.in>, <simon.perreault@viagenie.ca>, <pntaw@ietf.org>
Thread-Topic: [pntaw] Real-time media over TCP
Thread-Index: AQHOpWlrwk9eq/rvIEmYBkw2NSNGdZmyI/aAgACifgCAAN6pAIAApSuAgAAM8oCAACMQgIA1SsoAgAAHUgCAAYcrAIAACRcAgAF6zgCAAAPgcA==
Date: Wed, 9 Oct 2013 17:29:54 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A0D672F@008-AM1MPN1-042.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>
In-Reply-To: <003b01cec511$27e1abe0$77a503a0$@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: [10.163.168.177]
Content-Type: text/plain; charset="iso-8859-1"
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: Wed, 09 Oct 2013 17:36:59 -0000

Hi,

I think the clarification is that it is not possible to initiate TCP connec=
tions from the "outside" of any NAT or most of the firewalls. So even if th=
e FW does not block TCP per se, it only allows TCP connections to be opened=
 from the "inside".=20

I believe ICE-TCP will typically work only in cases where at least one of t=
he endpoints is NOT behind a NAT or FW. In cases where both endpoints are b=
ehind firewalls completely blocking all UDP, the only option is to use a re=
lay (TURN) with endpoint initiated TCP connections. ICE allows us to optimi=
ze connectivity in special cases, but I think we need also to make the wors=
t case scenarios to work. For that reason I don't see that ICE-TCP could re=
place TURN as a requirement for every browser to implement. In some specifi=
c deployments it may be that TURN does not get used much or at all, but bro=
wsers are used everywhere.

Markus=20

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of ext Parthasarathi R
> Sent: 09 October, 2013 20:01
> To: 'Simon Perreault'; pntaw@ietf.org
> Subject: Re: [pntaw] Real-time media over TCP
>=20
> Hi Simon,
>=20
> I have seen only two requirements in
> draft-ietf-rtcweb-use-cases-and-requirements-11, NAT/FW that blocks UDP
> and FW that only allows http. The relevant draft snippet is attached as a=
 note
> of this mail. I'm discussing about NAT/FW that blocks UDP requirement. In
> case you foresee that the requirement is not detailed now, we need to sor=
t
> out the requirement first before discussion the solutions.
>=20
> Regards
> Partha
>=20
> PS: In draft-ietf-rtcweb-use-cases-and-requirements-11 snippet,
>=20
> 3.2.2.  Simple Video Communication Service, NAT/FW that blocks UDP
>=20
> 3.2.2.1.  Description
>=20
>    This use-case is almost identical to the Simple Video Communication
>    Service use-case (Section 3.2.1).  The difference is that one of the
>    users is behind a NAT that blocks UDP traffic.
>=20
> 3.2.3.  Simple Video Communication Service, FW that only allows http
>=20
> 3.2.3.1.  Description
>=20
>    This use-case is almost identical to the Simple Video Communication
>    Service use-case (Section 3.2.1).  The difference is that one of the
>    users is behind a FW that only allows http traffic.
>=20
> > -----Original Message-----
> > From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> Behalf
> > Of Simon Perreault
> > Sent: Tuesday, October 08, 2013 11:55 PM
> > To: pntaw@ietf.org
> > Subject: Re: [pntaw] Real-time media over TCP
> >
> > Le 2013-10-08 19:52, Parthasarathi R a =E9crit :
> > > 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
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw
>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

From Markus.Isomaki@nokia.com  Wed Oct  9 10:46:18 2013
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 17EB421E80A1 for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 10:46:18 -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 kfj1fxJgSMc6 for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 10:46:12 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id D648221E8097 for <pntaw@ietf.org>; Wed,  9 Oct 2013 10:46:05 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.47]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r99HcuaT027738 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 9 Oct 2013 20:38:57 +0300
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([169.254.2.224]) by 008-AM1MMR1-013.mgdnok.nokia.com ([2002:4136:1e2f::4136:1e2f]) with mapi id 14.03.0136.001; Wed, 9 Oct 2013 17:38:56 +0000
From: <Markus.Isomaki@nokia.com>
To: <pkyzivat@alum.mit.edu>, <pntaw@ietf.org>
Thread-Topic: [pntaw] Real-time media over TCP
Thread-Index: AQHOpWlrwk9eq/rvIEmYBkw2NSNGdZmyI/aAgACifgCAAN6pAIAApSuAgAAM8oCAACMQgIA1SsoAgACuxgCAAlJGgIAAGaLg
Date: Wed, 9 Oct 2013 17:38:55 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A0D6767@008-AM1MPN1-042.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>	<52538AC4.5060500@alvestrand.no> <52557D47.3050402@alum.mit.edu>
In-Reply-To: <52557D47.3050402@alum.mit.edu>
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: [10.163.168.177]
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: Wed, 09 Oct 2013 17:46:18 -0000

Hi Paul,

Paul Kyzivat wrote:
>=20
> On 10/8/13 12:32 AM, Harald Alvestrand wrote:
>=20
> > 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
> > :-)
>=20
> 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.
>=20

I think it can happen even if the vendor and the service provider do all th=
ey can. For instance if both endpoints are behind a UDP blocking firewall a=
nd can only open TCP connections. So unless the endpoints support TCP-based=
 ICE candidates, I think they need to connect to their respective TURN rela=
ys and only via them they can reach each other's TURN-allocated UDP candida=
tes. So the transport will be split into 3 hops: TCP - UDP - TCP, where the=
 UDP part can be potentially very short.

Or is there some way to optimize from that? If I've understood correctly, I=
CE-TCP with TURN-allocated TCP ports would allow using just a single relay =
in the above scenario. It would be thus be better in case if the relays use=
d by the endpoints were NOT in the same DC.

Markus =20

From pkyzivat@alum.mit.edu  Wed Oct  9 12:07:20 2013
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 C39DC21F9F50 for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 12:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.231
X-Spam-Level: 
X-Spam-Status: No, score=-0.231 tagged_above=-999 required=5 tests=[AWL=0.206,  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 rovp3g3QdM+J for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 12:07:00 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id A5FC321E8194 for <pntaw@ietf.org>; Wed,  9 Oct 2013 12:06:31 -0700 (PDT)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta01.westchester.pa.mail.comcast.net with comcast id b62Y1m0091wpRvQ5176XQh; Wed, 09 Oct 2013 19:06:31 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta18.westchester.pa.mail.comcast.net with comcast id b76W1m0173ZTu2S3e76WpV; Wed, 09 Oct 2013 19:06:31 +0000
Message-ID: <5255A936.5000504@alum.mit.edu>
Date: Wed, 09 Oct 2013 15:06:30 -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: Markus.Isomaki@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>	<52538AC4.5060500@alvestrand.no> <52557D47.3050402@alum.mit.edu> <E44893DD4E290745BB608EB23FDDB7620A0D6767@008-AM1MPN1-042.mgdnok.nokia.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A0D6767@008-AM1MPN1-042.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=1381345591; bh=klbAUMLwN8XE4FxpV8SABVeAIvZQU0jTnIf5SUoL3Ko=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=KxyWyvFx8IiCITHAqrg4MNT3HE6SiKAAZTztYtCtFz+rmqYOL73HTMFyEV/xjlKHm zwPsSUNaOcX0Mwxt06bILFlU68YF9DmTY+GixvXZB1wbHDIKilt+pCxgQOexj/z0bs mCMfwnTjD4ggd9cfNu67AglNuTMk5rkH66ggmhBs70RTt4fHxotV7NtR7qqBNmtO2G uvCnEHOhASIJyEzVqRBCV4ls/RtK8cjVq2/JohRohHwpzmh7bwwo2NAa0hI2vl8H++ 50V8D1BrhemprqLpha3qVgHJXInbIjneG+/xLPESmkMViyYtiPGfjvPBtzDJ34oma4 vhCWsBzQlABGw==
Cc: pntaw@ietf.org
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 19:07:21 -0000

On 10/9/13 1:38 PM, Markus.Isomaki@nokia.com wrote:
> Hi Paul,
>
> Paul Kyzivat wrote:
>>
>> 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.
>>
>
> I think it can happen even if the vendor and the service provider do all they can. For instance if both endpoints are behind a UDP blocking firewall and can only open TCP connections. So unless the endpoints support TCP-based ICE candidates, I think they need to connect to their respective TURN relays and only via them they can reach each other's TURN-allocated UDP candidates. So the transport will be split into 3 hops: TCP - UDP - TCP, where the UDP part can be potentially very short.
>
> Or is there some way to optimize from that? If I've understood correctly, ICE-TCP with TURN-allocated TCP ports would allow using just a single relay in the above scenario. It would be thus be better in case if the relays used by the endpoints were NOT in the same DC.

My point was that if both use the *same* TURN server, then it should be 
smart enough to avoid establishing a UDP connection to itself.

	Thanks,
	Paul


From hangzhou.chenxin@huawei.com  Wed Oct  9 18:52:55 2013
Return-Path: <hangzhou.chenxin@huawei.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 2B2E821F9CB0 for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 18:52:55 -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 a5Y6ar+9KAit for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 18:52:51 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id E332221E825E for <pntaw@ietf.org>; Wed,  9 Oct 2013 18:52:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AWQ64041; Thu, 10 Oct 2013 01:52:45 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 10 Oct 2013 02:52:18 +0100
Received: from SZXEMA406-HUB.china.huawei.com (10.82.72.38) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 10 Oct 2013 02:52:43 +0100
Received: from SZXEMA504-MBX.china.huawei.com ([169.254.7.96]) by SZXEMA406-HUB.china.huawei.com ([10.82.72.38]) with mapi id 14.03.0146.000; Thu, 10 Oct 2013 09:52:37 +0800
From: "Chenxin (Xin)" <hangzhou.chenxin@huawei.com>
To: "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>, "partha@parthasarathi.co.in" <partha@parthasarathi.co.in>, "simon.perreault@viagenie.ca" <simon.perreault@viagenie.ca>, "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: [pntaw] Real-time media over TCP
Thread-Index: AQHOp7eh97CWvanNyUO4L+fWrmoYupmyO7sAgADeqQCAAKUrgIAADPKAgAAjEICANUrLAIAAB1IAgAGHKgCAAAkXAIABes4AgAAIDACAARCqIA==
Date: Thu, 10 Oct 2013 01:52:36 +0000
Message-ID: <9E34D50A21D1D1489134B4D770CE039768081AC9@SZXEMA504-MBX.china.huawei.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>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A0D672F@008-AM1MPN1-042.mgdnok.nokia.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.166.41.125]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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: Thu, 10 Oct 2013 01:52:55 -0000

Hi

 I agree that ICE-TCP should not replace TURN as a requirement for every br=
owser to implement. If we need support ICE-TCP , should we support TURN-TCP=
 too? I do not think ICE-TCP will be more useful without TURN-TCP in the sc=
enario where both browsers is under the NAT /FW which block UDP.=20

  I believe the user 1->TCP->TURN server 1->UDP->TURN server 2->TCP->user 2=
, which Harald wrote before is workable. It is easy to tunnel the data inte=
rnally if we need use the same server, right?

Best Regards,
     Xin=20


>-----Original Message-----
>From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf Of
>Markus.Isomaki@nokia.com
>Sent: Thursday, October 10, 2013 1:30 AM
>To: partha@parthasarathi.co.in; simon.perreault@viagenie.ca; pntaw@ietf.or=
g
>Subject: Re: [pntaw] Real-time media over TCP
>
>Hi,
>
>I think the clarification is that it is not possible to initiate TCP conne=
ctions from
>the "outside" of any NAT or most of the firewalls. So even if the FW does =
not
>block TCP per se, it only allows TCP connections to be opened from the "in=
side".
>
>I believe ICE-TCP will typically work only in cases where at least one of =
the
>endpoints is NOT behind a NAT or FW. In cases where both endpoints are beh=
ind
>firewalls completely blocking all UDP, the only option is to use a relay (=
TURN)
>with endpoint initiated TCP connections. ICE allows us to optimize connect=
ivity
>in special cases, but I think we need also to make the worst case scenario=
s to
>work. For that reason I don't see that ICE-TCP could replace TURN as a
>requirement for every browser to implement. In some specific deployments i=
t
>may be that TURN does not get used much or at all, but browsers are used
>everywhere.
>
>Markus
>
>> -----Original Message-----
>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
>> Of ext Parthasarathi R
>> Sent: 09 October, 2013 20:01
>> To: 'Simon Perreault'; pntaw@ietf.org
>> Subject: Re: [pntaw] Real-time media over TCP
>>
>> Hi Simon,
>>
>> I have seen only two requirements in
>> draft-ietf-rtcweb-use-cases-and-requirements-11, NAT/FW that blocks UDP
>> and FW that only allows http. The relevant draft snippet is attached as =
a note
>> of this mail. I'm discussing about NAT/FW that blocks UDP requirement. I=
n
>> case you foresee that the requirement is not detailed now, we need to so=
rt
>> out the requirement first before discussion the solutions.
>>
>> Regards
>> Partha
>>
>> PS: In draft-ietf-rtcweb-use-cases-and-requirements-11 snippet,
>>
>> 3.2.2.  Simple Video Communication Service, NAT/FW that blocks UDP
>>
>> 3.2.2.1.  Description
>>
>>    This use-case is almost identical to the Simple Video Communication
>>    Service use-case (Section 3.2.1).  The difference is that one of the
>>    users is behind a NAT that blocks UDP traffic.
>>
>> 3.2.3.  Simple Video Communication Service, FW that only allows http
>>
>> 3.2.3.1.  Description
>>
>>    This use-case is almost identical to the Simple Video Communication
>>    Service use-case (Section 3.2.1).  The difference is that one of the
>>    users is behind a FW that only allows http traffic.
>>
>> > -----Original Message-----
>> > From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
>> Behalf
>> > Of Simon Perreault
>> > Sent: Tuesday, October 08, 2013 11:55 PM
>> > To: pntaw@ietf.org
>> > Subject: Re: [pntaw] Real-time media over TCP
>> >
>> > Le 2013-10-08 19:52, Parthasarathi R a =E9crit :
>> > > 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
>> > _______________________________________________
>> > pntaw mailing list
>> > pntaw@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pntaw
>>
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
>_______________________________________________
>pntaw mailing list
>pntaw@ietf.org
>https://www.ietf.org/mailman/listinfo/pntaw

From harald@alvestrand.no  Wed Oct  9 20:23:52 2013
Return-Path: <harald@alvestrand.no>
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 5150A11E8116 for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 20:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 n+o7TE2CTxws for <pntaw@ietfa.amsl.com>; Wed,  9 Oct 2013 20:23:44 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id C63B721E80B4 for <pntaw@ietf.org>; Wed,  9 Oct 2013 20:23:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2537239E95A for <pntaw@ietf.org>; Thu, 10 Oct 2013 05:23:40 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ygwPgLqMrecQ for <pntaw@ietf.org>; Thu, 10 Oct 2013 05:23:39 +0200 (CEST)
Received: from [172.30.42.84] (unknown [62.109.39.85]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 626F439E42A for <pntaw@ietf.org>; Thu, 10 Oct 2013 05:23:39 +0200 (CEST)
Message-ID: <52561DBB.6010507@alvestrand.no>
Date: Thu, 10 Oct 2013 05:23:39 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: pntaw@ietf.org
References: <5232C18C.1030102@gmail.com> <523C8BDC.6050705@petit-huguenin.org>	<CALDtMrKwygUqNWKcB81F+M7Y8wBmwZtTACeYChpJVvWKbXLTEw@mail.gmail.com>	<523C9B03.2030002@petit-huguenin.org>	<CALDtMrJBQQZP4bbkLh6OcZhmOGFrP5bAJ8BDr0AY1zKjPXChPw@mail.gmail.com>	<523CAC92.2070102@petit-huguenin.org> <523CB114.20106@gmail.com>	<523CB437.6000806@petit-huguenin.org> <CALDtMr+Fc3G-H--n7DuKPMzx-6fo_XweuYd=LxdjRp+tgB_3NQ@mail.gmail.com>
In-Reply-To: <CALDtMr+Fc3G-H--n7DuKPMzx-6fo_XweuYd=LxdjRp+tgB_3NQ@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative; boundary="------------090301010501060904090303"
Subject: Re: [pntaw] New version of TURN over websockets draft
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: Thu, 10 Oct 2013 03:23:52 -0000

This is a multi-part message in MIME format.
--------------090301010501060904090303
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 09/20/2013 11:12 PM, Oleg Moskalenko wrote:
> RFC 6062 is not very important but I cannot say that it is not relevant. For the purpose of the new
proposal we do not make a distinction between RFC 5766 and RFC 6062 -
this new proposal is about a new TURN transport (Websockets). This
transport is supposed to work universally in all accepted TURN RFCs. So
it would be unnatural and illogical to remove RFC 6062 from the draft.
>


Note that the -transport- draft currently has RFC 5766 support as MUST,
while
RFC 6062 support is a MAY.

The main purpose of mentioning RFC 6062 in the draft is to show that
it's been mentioned in discussion, and that the WG has consensus to not
make it anything stronger than a MAY.

(I think it would be very strange if we were to attempt to forbid it.)


--------------090301010501060904090303
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 09/20/2013 11:12 PM, Oleg Moskalenko wrote:<br>
    <span style="white-space: pre;">&gt; RFC 6062 is not very important
      but I cannot say that it is not relevant. For the purpose of the
      new proposal we do not make a distinction between RFC 5766 and RFC
      6062 - this new proposal is about a new TURN transport
      (Websockets). This transport is supposed to work universally in
      all accepted TURN RFCs. So it would be unnatural and illogical to
      remove RFC 6062 from the draft.<br>
      &gt;<br>
      <br>
      <br>
      Note that the -transport- draft currently has RFC 5766 support as
      MUST, while</span><br>
    RFC 6062 support is a MAY.<br>
    <br>
    The main purpose of mentioning RFC 6062 in the draft is to show that
    it's been mentioned in discussion, and that the WG has consensus to
    not make it anything stronger than a MAY.<br>
    <br>
    (I think it would be very strange if we were to attempt to forbid
    it.)<br>
    <br>
  </body>
</html>

--------------090301010501060904090303--

From partha@parthasarathi.co.in  Thu Oct 10 10:41:46 2013
Return-Path: <partha@parthasarathi.co.in>
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 5E4E221F9385 for <pntaw@ietfa.amsl.com>; Thu, 10 Oct 2013 10:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.839
X-Spam-Level: 
X-Spam-Status: No, score=-1.839 tagged_above=-999 required=5 tests=[AWL=0.760,  BAYES_00=-2.599]
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 YMglbibY6PPP for <pntaw@ietfa.amsl.com>; Thu, 10 Oct 2013 10:41:29 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us3.mailhostbox.com [70.87.28.155]) by ietfa.amsl.com (Postfix) with ESMTP id 6451311E818A for <pntaw@ietf.org>; Thu, 10 Oct 2013 10:40:36 -0700 (PDT)
Received: from userPC (unknown [122.179.99.194]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id 7B2358693D5; Thu, 10 Oct 2013 17:40:24 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1381426833; bh=V44OEWpMsOeu6zlHpS1vl5UeKkIoq/MGnDwrRHAy5DI=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=d2ojIMIWfyEmi21iN2f9qyF4D6sGWUNyog0t8Nf42Q+90rrpWphCbQufLup4LAw7a Vbg5Xc29CPuEGqafUWhSbhbtIhJiIe6cVRS9fy/6NdsWi0Usf0DZCkVoSoR1ZjaMcA UZmWJx/YXUEFL8OfXygY2mMzPo8Z4mgL1LOmA/+4=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Chenxin \(Xin\)'" <hangzhou.chenxin@huawei.com>, <Markus.Isomaki@nokia.com>, <simon.perreault@viagenie.ca>, <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>	<52544E0E.5080405@viagenie.ca>	<003b01cec511$27e1abe0$77a503a0$@co.in>	<E44893DD4E290745BB608EB23FDDB7620A0D672F@008-AM1MPN1-042.mgdnok.nokia.com> <9E34D50A21D1D1489134B4D770CE039768081AC9@SZXEMA504-MBX.china.huawei.com>
In-Reply-To: <9E34D50A21D1D1489134B4D770CE039768081AC9@SZXEMA504-MBX.china.huawei.com>
Date: Thu, 10 Oct 2013 23:10:17 +0530
Message-ID: <004e01cec5df$cf8daaf0$6ea900d0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHOp7eh97CWvanNyUO4L+fWrmoYupmyO7sAgADeqQCAAKUrgIAADPKAgAAjEICANUrLAIAAB1IAgAGHKgCAAAkXAIABes4AgAAIDACAARCqIIAA8XlQ
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020205.5256E691.0071, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.155
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: Thu, 10 Oct 2013 17:41:46 -0000

Hi all,

As I mentioned below, ICE-TCP is not replacement for TURN but ICE-TCP =
helps
for the browser-to-browser media flow without middle box (TURN Server).
Also, please note that both browsers behind UDP blocked firewall is not =
the
worst case scenario for WebRTC firewall requirements. The actual worst =
case
scenario is that both browsers are behind HTTP only firewalls and in =
this
scenario, both TURN server and ICE-TCP will not work. There is a need of =
one
more solution.

AFAIK, HTTP allowing firewall is not happen by mis-configuration but it =
is
policy of the given network. It is more appropriate to pass the media =
over
HTTP based mechanism rather than finding the workarounds. The advantage =
with
Media over HTTP is that HTTP friendly firewall shall filter out media =
from
HTTP traffic if required. IMO, Media over HTTP based mechanism has to be
used for HTTP only firewall (Sec 3.2.3 of
draft-ietf-rtcweb-use-cases-and-requirements) requirement and ICE-TCP =
shall
be used for (Sec 3.2.3 of draft-ietf-rtcweb-use-cases-and-requirements)
requirement.=20

Thanks
Partha =20

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of Chenxin (Xin)
> Sent: Thursday, October 10, 2013 7:23 AM
> To: Markus.Isomaki@nokia.com; partha@parthasarathi.co.in;
> simon.perreault@viagenie.ca; pntaw@ietf.org
> Subject: Re: [pntaw] Real-time media over TCP
>=20
> Hi
>=20
>  I agree that ICE-TCP should not replace TURN as a requirement for
> every browser to implement. If we need support ICE-TCP , should we
> support TURN-TCP too? I do not think ICE-TCP will be more useful
> without TURN-TCP in the scenario where both browsers is under the NAT
> /FW which block UDP.
>=20
>   I believe the user 1->TCP->TURN server 1->UDP->TURN server 2->TCP-
> >user 2, which Harald wrote before is workable. It is easy to tunnel
> the data internally if we need use the same server, right?
>=20
> Best Regards,
>      Xin
>=20
>=20
> >-----Original Message-----
> >From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On =
Behalf
> Of
> >Markus.Isomaki@nokia.com
> >Sent: Thursday, October 10, 2013 1:30 AM
> >To: partha@parthasarathi.co.in; simon.perreault@viagenie.ca;
> pntaw@ietf.org
> >Subject: Re: [pntaw] Real-time media over TCP
> >
> >Hi,
> >
> >I think the clarification is that it is not possible to initiate TCP
> connections from
> >the "outside" of any NAT or most of the firewalls. So even if the FW
> does not
> >block TCP per se, it only allows TCP connections to be opened from =
the
> "inside".
> >
> >I believe ICE-TCP will typically work only in cases where at least =
one
> of the
> >endpoints is NOT behind a NAT or FW. In cases where both endpoints =
are
> behind
> >firewalls completely blocking all UDP, the only option is to use a
> relay (TURN)
> >with endpoint initiated TCP connections. ICE allows us to optimize
> connectivity
> >in special cases, but I think we need also to make the worst case
> scenarios to
> >work. For that reason I don't see that ICE-TCP could replace TURN as =
a
> >requirement for every browser to implement. In some specific
> deployments it
> >may be that TURN does not get used much or at all, but browsers are
> used
> >everywhere.
> >
> >Markus
> >
> >> -----Original Message-----
> >> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> Behalf
> >> Of ext Parthasarathi R
> >> Sent: 09 October, 2013 20:01
> >> To: 'Simon Perreault'; pntaw@ietf.org
> >> Subject: Re: [pntaw] Real-time media over TCP
> >>
> >> Hi Simon,
> >>
> >> I have seen only two requirements in
> >> draft-ietf-rtcweb-use-cases-and-requirements-11, NAT/FW that blocks
> UDP
> >> and FW that only allows http. The relevant draft snippet is =
attached
> as a note
> >> of this mail. I'm discussing about NAT/FW that blocks UDP
> requirement. In
> >> case you foresee that the requirement is not detailed now, we need
> to sort
> >> out the requirement first before discussion the solutions.
> >>
> >> Regards
> >> Partha
> >>
> >> PS: In draft-ietf-rtcweb-use-cases-and-requirements-11 snippet,
> >>
> >> 3.2.2.  Simple Video Communication Service, NAT/FW that blocks UDP
> >>
> >> 3.2.2.1.  Description
> >>
> >>    This use-case is almost identical to the Simple Video
> Communication
> >>    Service use-case (Section 3.2.1).  The difference is that one of
> the
> >>    users is behind a NAT that blocks UDP traffic.
> >>
> >> 3.2.3.  Simple Video Communication Service, FW that only allows =
http
> >>
> >> 3.2.3.1.  Description
> >>
> >>    This use-case is almost identical to the Simple Video
> Communication
> >>    Service use-case (Section 3.2.1).  The difference is that one of
> the
> >>    users is behind a FW that only allows http traffic.
> >>
> >> > -----Original Message-----
> >> > From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> >> Behalf
> >> > Of Simon Perreault
> >> > Sent: Tuesday, October 08, 2013 11:55 PM
> >> > To: pntaw@ietf.org
> >> > Subject: Re: [pntaw] Real-time media over TCP
> >> >
> >> > Le 2013-10-08 19:52, Parthasarathi R a =E9crit :
> >> > > 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
> >> > _______________________________________________
> >> > pntaw mailing list
> >> > pntaw@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/pntaw
> >>
> >> _______________________________________________
> >> pntaw mailing list
> >> pntaw@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pntaw
> >_______________________________________________
> >pntaw mailing list
> >pntaw@ietf.org
> >https://www.ietf.org/mailman/listinfo/pntaw
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From hangzhou.chenxin@huawei.com  Thu Oct 10 20:57:56 2013
Return-Path: <hangzhou.chenxin@huawei.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 6857521F9A90 for <pntaw@ietfa.amsl.com>; Thu, 10 Oct 2013 20:57:56 -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 SbJvkpLYkM5E for <pntaw@ietfa.amsl.com>; Thu, 10 Oct 2013 20:57:52 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D407321F9E43 for <pntaw@ietf.org>; Thu, 10 Oct 2013 20:57:50 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYY82746; Fri, 11 Oct 2013 03:57:49 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.146.0; Fri, 11 Oct 2013 04:57:17 +0100
Received: from SZXEMA404-HUB.china.huawei.com (10.82.72.36) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.146.0; Fri, 11 Oct 2013 04:57:45 +0100
Received: from SZXEMA504-MBX.china.huawei.com ([169.254.7.96]) by SZXEMA404-HUB.china.huawei.com ([10.82.72.36]) with mapi id 14.03.0146.000; Fri, 11 Oct 2013 11:57:40 +0800
From: "Chenxin (Xin)" <hangzhou.chenxin@huawei.com>
To: Parthasarathi R <partha@parthasarathi.co.in>, "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>, "simon.perreault@viagenie.ca" <simon.perreault@viagenie.ca>, "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: [pntaw] Real-time media over TCP
Thread-Index: AQHOp7eh97CWvanNyUO4L+fWrmoYupmyO7sAgADeqQCAAKUrgIAADPKAgAAjEICANUrLAIAAB1IAgAGHKgCAAAkXAIABes4AgAAIDACAARCqIIAA8XlQgADDLEA=
Date: Fri, 11 Oct 2013 03:57:39 +0000
Message-ID: <9E34D50A21D1D1489134B4D770CE039768081D1B@SZXEMA504-MBX.china.huawei.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>
In-Reply-To: <004e01cec5df$cf8daaf0$6ea900d0$@co.in>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.166.41.125]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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: Fri, 11 Oct 2013 03:57:56 -0000

Hi
>Hi all,
>
>As I mentioned below, ICE-TCP is not replacement for TURN but ICE-TCP help=
s
>for the browser-to-browser media flow without middle box (TURN Server).
>Also, please note that both browsers behind UDP blocked firewall is not th=
e
>worst case scenario for WebRTC firewall requirements. The actual worst cas=
e
>scenario is that both browsers are behind HTTP only firewalls and in this
>scenario, both TURN server and ICE-TCP will not work. There is a need of o=
ne
>more solution.
>
>AFAIK, HTTP allowing firewall is not happen by mis-configuration but it is
>policy of the given network. It is more appropriate to pass the media over
>HTTP based mechanism rather than finding the workarounds. The advantage
>with
>Media over HTTP is that HTTP friendly firewall shall filter out media from
>HTTP traffic if required.
[xin] And media over websocket should be a option. The sub-protocol attribu=
te in websokcet could also provide the firewall friendly information, so th=
e firewall could decide to filter out the media or not.=20

 IMO, Media over HTTP based mechanism has to be
>used for HTTP only firewall (Sec 3.2.3 of
>draft-ietf-rtcweb-use-cases-and-requirements) requirement and ICE-TCP shal=
l
>be used for (Sec 3.2.3 of draft-ietf-rtcweb-use-cases-and-requirements)
>requirement.

  [Xin] I think you means ICE-TCP shall be used for (*Sec 3.2.2* of draft-i=
etf-rtcweb-use-cases-and-requirements) requirement.:)

Thanks,
  Xin
>
>Thanks
>Partha
>
>> -----Original Message-----
>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
>> Of Chenxin (Xin)
>> Sent: Thursday, October 10, 2013 7:23 AM
>> To: Markus.Isomaki@nokia.com; partha@parthasarathi.co.in;
>> simon.perreault@viagenie.ca; pntaw@ietf.org
>> Subject: Re: [pntaw] Real-time media over TCP
>>
>> Hi
>>
>>  I agree that ICE-TCP should not replace TURN as a requirement for
>> every browser to implement. If we need support ICE-TCP , should we
>> support TURN-TCP too? I do not think ICE-TCP will be more useful
>> without TURN-TCP in the scenario where both browsers is under the NAT
>> /FW which block UDP.
>>
>>   I believe the user 1->TCP->TURN server 1->UDP->TURN server 2->TCP-
>> >user 2, which Harald wrote before is workable. It is easy to tunnel
>> the data internally if we need use the same server, right?
>>
>> Best Regards,
>>      Xin
>>
>>
>> >-----Original Message-----
>> >From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
>> Of
>> >Markus.Isomaki@nokia.com
>> >Sent: Thursday, October 10, 2013 1:30 AM
>> >To: partha@parthasarathi.co.in; simon.perreault@viagenie.ca;
>> pntaw@ietf.org
>> >Subject: Re: [pntaw] Real-time media over TCP
>> >
>> >Hi,
>> >
>> >I think the clarification is that it is not possible to initiate TCP
>> connections from
>> >the "outside" of any NAT or most of the firewalls. So even if the FW
>> does not
>> >block TCP per se, it only allows TCP connections to be opened from the
>> "inside".
>> >
>> >I believe ICE-TCP will typically work only in cases where at least one
>> of the
>> >endpoints is NOT behind a NAT or FW. In cases where both endpoints are
>> behind
>> >firewalls completely blocking all UDP, the only option is to use a
>> relay (TURN)
>> >with endpoint initiated TCP connections. ICE allows us to optimize
>> connectivity
>> >in special cases, but I think we need also to make the worst case
>> scenarios to
>> >work. For that reason I don't see that ICE-TCP could replace TURN as a
>> >requirement for every browser to implement. In some specific
>> deployments it
>> >may be that TURN does not get used much or at all, but browsers are
>> used
>> >everywhere.
>> >
>> >Markus
>> >
>> >> -----Original Message-----
>> >> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
>> Behalf
>> >> Of ext Parthasarathi R
>> >> Sent: 09 October, 2013 20:01
>> >> To: 'Simon Perreault'; pntaw@ietf.org
>> >> Subject: Re: [pntaw] Real-time media over TCP
>> >>
>> >> Hi Simon,
>> >>
>> >> I have seen only two requirements in
>> >> draft-ietf-rtcweb-use-cases-and-requirements-11, NAT/FW that blocks
>> UDP
>> >> and FW that only allows http. The relevant draft snippet is attached
>> as a note
>> >> of this mail. I'm discussing about NAT/FW that blocks UDP
>> requirement. In
>> >> case you foresee that the requirement is not detailed now, we need
>> to sort
>> >> out the requirement first before discussion the solutions.
>> >>
>> >> Regards
>> >> Partha
>> >>
>> >> PS: In draft-ietf-rtcweb-use-cases-and-requirements-11 snippet,
>> >>
>> >> 3.2.2.  Simple Video Communication Service, NAT/FW that blocks UDP
>> >>
>> >> 3.2.2.1.  Description
>> >>
>> >>    This use-case is almost identical to the Simple Video
>> Communication
>> >>    Service use-case (Section 3.2.1).  The difference is that one of
>> the
>> >>    users is behind a NAT that blocks UDP traffic.
>> >>
>> >> 3.2.3.  Simple Video Communication Service, FW that only allows http
>> >>
>> >> 3.2.3.1.  Description
>> >>
>> >>    This use-case is almost identical to the Simple Video
>> Communication
>> >>    Service use-case (Section 3.2.1).  The difference is that one of
>> the
>> >>    users is behind a FW that only allows http traffic.
>> >>
>> >> > -----Original Message-----
>> >> > From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
>> >> Behalf
>> >> > Of Simon Perreault
>> >> > Sent: Tuesday, October 08, 2013 11:55 PM
>> >> > To: pntaw@ietf.org
>> >> > Subject: Re: [pntaw] Real-time media over TCP
>> >> >
>> >> > Le 2013-10-08 19:52, Parthasarathi R a =E9crit :
>> >> > > 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
>> >> > _______________________________________________
>> >> > pntaw mailing list
>> >> > pntaw@ietf.org
>> >> > https://www.ietf.org/mailman/listinfo/pntaw
>> >>
>> >> _______________________________________________
>> >> pntaw mailing list
>> >> pntaw@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/pntaw
>> >_______________________________________________
>> >pntaw mailing list
>> >pntaw@ietf.org
>> >https://www.ietf.org/mailman/listinfo/pntaw
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw


From Markus.Isomaki@nokia.com  Fri Oct 11 05:26:54 2013
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 AFF7621E80FB for <pntaw@ietfa.amsl.com>; Fri, 11 Oct 2013 05:26:53 -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 Qis-wLo8j5CS for <pntaw@ietfa.amsl.com>; Fri, 11 Oct 2013 05:26:47 -0700 (PDT)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id F2BB921E81B8 for <pntaw@ietf.org>; Fri, 11 Oct 2013 05:26:36 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.26]) by mgw-sa02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r9BCLcox023472 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 11 Oct 2013 15:21:39 +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; Fri, 11 Oct 2013 12:21:38 +0000
From: <Markus.Isomaki@nokia.com>
To: <partha@parthasarathi.co.in>, <hangzhou.chenxin@huawei.com>, <simon.perreault@viagenie.ca>, <pntaw@ietf.org>
Thread-Topic: [pntaw] Real-time media over TCP
Thread-Index: AQHOpWlrwk9eq/rvIEmYBkw2NSNGdZmyI/aAgACifgCAAN6pAIAApSuAgAAM8oCAACMQgIA1SsoAgAAHUgCAAYcrAIAACRcAgAF6zgCAAAPgcIAAkKAAgAEIx4CAAS4k0A==
Date: Fri, 11 Oct 2013 12:21:37 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A0E2DC6@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>
In-Reply-To: <004e01cec5df$cf8daaf0$6ea900d0$@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: [10.163.166.235]
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: Fri, 11 Oct 2013 12:26:54 -0000

Hi Partha,

Parthasarathi R [mailto:partha@parthasarathi.co.in] wrote:
>=20
> Hi all,
>=20
> As I mentioned below, ICE-TCP is not replacement for TURN but ICE-TCP
> helps for the browser-to-browser media flow without middle box (TURN
> Server).
> Also, please note that both browsers behind UDP blocked firewall is not t=
he
> worst case scenario for WebRTC firewall requirements. The actual worst ca=
se
> scenario is that both browsers are behind HTTP only firewalls and in this
> scenario, both TURN server and ICE-TCP will not work. There is a need of =
one
> more solution.
>

Agree. And we need to consider that BOTH endpoints may be behind such firew=
alls.
=20
> AFAIK, HTTP allowing firewall is not happen by mis-configuration but it i=
s
> policy of the given network. It is more appropriate to pass the media ove=
r
> HTTP based mechanism rather than finding the workarounds. The advantage
> with Media over HTTP is that HTTP friendly firewall shall filter out medi=
a from
> HTTP traffic if required. IMO, Media over HTTP based mechanism has to be
> used for HTTP only firewall (Sec 3.2.3 of
> draft-ietf-rtcweb-use-cases-and-requirements) requirement and ICE-TCP
> shall be used for (Sec 3.2.3 of draft-ietf-rtcweb-use-cases-and-
> requirements)
> requirement.
>=20

So, what is the overall set of traversal / connectivity / address gathering=
 mechanisms the browser should support that you are advocating? Mine is:

1.) UDP host candidates (native interface) - MUST
2.)UDP server-reflexive candidates (STUN) - MUST
3.) UDP relay candidates via UDP (TURN) - MUST
4.) UDP relay candidates via TCP (TURN) - MUST
5.) UDP relay candidates via some HTTP/TLS compatible transport (TURN) - MU=
ST/SHOULD
   (TLS via HTTP CONNET or TURN over WebSockets have been proposed.)
6.) TCP based candidates (ICE-TCP) - MAY/SHOULD

I believe 1.), 2.) and 3.) we all have consensus on, probably even on 4.). =
What we are discussing on this list is whether and how to do 5.), and how i=
mportant 6.) is.=20

My opinion is that 5.) becomes necessary due to the HTTP-limited environmen=
ts you mention above. So the communication needs to be compliant with HTTP =
and its upgrade mechanisms. 6.) I see as an optimization to 4.) in cases wh=
ere you can't do UDP but can establish outgoing TCP connections and the oth=
er peer can actually receive them. But that optimization does not hold very=
 often, since most of the time browsers are in networks where they can't re=
ceive TCP connections from the "outside world". So that's why I see it as M=
AY or SHOULD. You may argue that often browsers may talk to gateways or cen=
tral points that are reachable by TCP, and in those scenarios ICE-TCP might=
 make sense.=20

Markus=20


From andrew.hutton@siemens-enterprise.com  Mon Oct 14 07:42:18 2013
Return-Path: <andrew.hutton@siemens-enterprise.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 8D94A11E8140 for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 07:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 mJhVL0pbA9NY for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 07:42:13 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 40AC411E813F for <pntaw@ietf.org>; Mon, 14 Oct 2013 07:42:13 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id CFE691EB850B; Mon, 14 Oct 2013 16:42:11 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.31]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Mon, 14 Oct 2013 16:41:33 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>, "partha@parthasarathi.co.in" <partha@parthasarathi.co.in>, "hangzhou.chenxin@huawei.com" <hangzhou.chenxin@huawei.com>, "simon.perreault@viagenie.ca" <simon.perreault@viagenie.ca>, "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: [pntaw] Real-time media over TCP
Thread-Index: AQHOpWlrwk9eq/rvIEmYBkw2NSNGdZmyI/aAgACifgCAAN6pAIAApSuAgAAM8oCAACMQgIA1SsoAgAAHUgCAAYcrAIAACRcAgAF6zgCAAAPgcIAAkKAAgAEIx4CAAS4k0IAE5epg
Date: Mon, 14 Oct 2013 14:42:11 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17BEFB3E@MCHP04MSX.global-ad.net>
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>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A0E2DC6@008-AM1MPN1-043.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 14:42:18 -0000

On: 11 October 2013 13:22  Markus.Isomaki@nokia.com Wrote


>=20
> So, what is the overall set of traversal / connectivity / address
> gathering mechanisms the browser should support that you are
> advocating? Mine is:
>=20
> 1.) UDP host candidates (native interface) - MUST
> 2.)UDP server-reflexive candidates (STUN) - MUST
> 3.) UDP relay candidates via UDP (TURN) - MUST
> 4.) UDP relay candidates via TCP (TURN) - MUST
> 5.) UDP relay candidates via some HTTP/TLS compatible transport (TURN)
> - MUST/SHOULD
>    (TLS via HTTP CONNET or TURN over WebSockets have been proposed.)
> 6.) TCP based candidates (ICE-TCP) - MAY/SHOULD
>=20
> I believe 1.), 2.) and 3.) we all have consensus on, probably even on
> 4.). What we are discussing on this list is whether and how to do 5.),
> and how important 6.) is.
>=20
> My opinion is that 5.) becomes necessary due to the HTTP-limited
> environments you mention above. So the communication needs to be
> compliant with HTTP and its upgrade mechanisms. 6.) I see as an
> optimization to 4.) in cases where you can't do UDP but can establish
> outgoing TCP connections and the other peer can actually receive them.
> But that optimization does not hold very often, since most of the time
> browsers are in networks where they can't receive TCP connections from
> the "outside world". So that's why I see it as MAY or SHOULD. You may
> argue that often browsers may talk to gateways or central points that
> are reachable by TCP, and in those scenarios ICE-TCP might make sense.
>=20

Totally agree with the nice summary above and agree that 5) is necessary we=
 have use cases in draft-ietf-rtcweb-use-cases-and-requirements that say we=
 do. We need some mechanism that is HTTP compatible and we have these two o=
ptions available and to me there is very little difference between them it =
is just a matter of whether the use of the additional websockets layers giv=
e us any benefit. I am not convinced that 6) is needed but might be some co=
rner cases it satisfies.

Andy

From bernard_aboba@hotmail.com  Mon Oct 14 08:09:14 2013
Return-Path: <bernard_aboba@hotmail.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 CA7B721E80DF for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 08:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.529
X-Spam-Level: 
X-Spam-Status: No, score=-101.529 tagged_above=-999 required=5 tests=[AWL=-0.326, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 EZ5bALb9Kkaw for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 08:09:10 -0700 (PDT)
Received: from blu0-omc3-s4.blu0.hotmail.com (blu0-omc3-s4.blu0.hotmail.com [65.55.116.79]) by ietfa.amsl.com (Postfix) with ESMTP id 88A9321E817B for <pntaw@ietf.org>; Mon, 14 Oct 2013 08:08:54 -0700 (PDT)
Received: from BLU402-EAS357 ([65.55.116.72]) by blu0-omc3-s4.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Oct 2013 08:08:46 -0700
X-TMN: [7EsunHyQDJSzNMM+MczfyBHr9OU2amT+]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU402-EAS357ECBFC621A567B9D3A7B4931A0@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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>
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17BEFB3E@MCHP04MSX.global-ad.net>
Date: Mon, 14 Oct 2013 08:08:40 -0700
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-OriginalArrivalTime: 14 Oct 2013 15:08:46.0220 (UTC) FILETIME=[477964C0:01CEC8EF]
Cc: "simon.perreault@viagenie.ca" <simon.perreault@viagenie.ca>, "pntaw@ietf.org" <pntaw@ietf.org>, "partha@parthasarathi.co.in" <partha@parthasarathi.co.in>, "hangzhou.chenxin@huawei.com" <hangzhou.chenxin@huawei.com>, "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>
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 15:09:15 -0000

Agree on Markus's summary. I am also not convinced on #6 being a MUST becaus=
e so far there hasn't been a compelling use case.

> On Oct 14, 2013, at 7:42 AM, "Hutton, Andrew" <andrew.hutton@siemens-enter=
prise.com> wrote:
>=20
> On: 11 October 2013 13:22  Markus.Isomaki@nokia.com Wrote
>=20
>=20
>>=20
>> So, what is the overall set of traversal / connectivity / address
>> gathering mechanisms the browser should support that you are
>> advocating? Mine is:
>>=20
>> 1.) UDP host candidates (native interface) - MUST
>> 2.)UDP server-reflexive candidates (STUN) - MUST
>> 3.) UDP relay candidates via UDP (TURN) - MUST
>> 4.) UDP relay candidates via TCP (TURN) - MUST
>> 5.) UDP relay candidates via some HTTP/TLS compatible transport (TURN)
>> - MUST/SHOULD
>>   (TLS via HTTP CONNET or TURN over WebSockets have been proposed.)
>> 6.) TCP based candidates (ICE-TCP) - MAY/SHOULD
>>=20
>> I believe 1.), 2.) and 3.) we all have consensus on, probably even on
>> 4.). What we are discussing on this list is whether and how to do 5.),
>> and how important 6.) is.
>>=20
>> My opinion is that 5.) becomes necessary due to the HTTP-limited
>> environments you mention above. So the communication needs to be
>> compliant with HTTP and its upgrade mechanisms. 6.) I see as an
>> optimization to 4.) in cases where you can't do UDP but can establish
>> outgoing TCP connections and the other peer can actually receive them.
>> But that optimization does not hold very often, since most of the time
>> browsers are in networks where they can't receive TCP connections from
>> the "outside world". So that's why I see it as MAY or SHOULD. You may
>> argue that often browsers may talk to gateways or central points that
>> are reachable by TCP, and in those scenarios ICE-TCP might make sense.
>=20
> Totally agree with the nice summary above and agree that 5) is necessary w=
e have use cases in draft-ietf-rtcweb-use-cases-and-requirements that say we=
 do. We need some mechanism that is HTTP compatible and we have these two op=
tions available and to me there is very little difference between them it is=
 just a matter of whether the use of the additional websockets layers give u=
s any benefit. I am not convinced that 6) is needed but might be some corner=
 cases it satisfies.
>=20
> Andy
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

From sergio.garcia.murillo@gmail.com  Mon Oct 14 08:58:16 2013
Return-Path: <sergio.garcia.murillo@gmail.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 7FD1521E8177 for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 08:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 n7UjINjWIy5X for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 08:58:15 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id ED37421E80D0 for <pntaw@ietf.org>; Mon, 14 Oct 2013 08:58:03 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id b13so6293715wgh.15 for <pntaw@ietf.org>; Mon, 14 Oct 2013 08:58:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=cJSbQ30uYr5sLEA3FHV1cVevohPprgPcYFF6uHXLhC8=; b=LPavcf41dnJZ3mE12ruv/g40Oh4YueP6tbF8AT7uWaDsLwLRpkk8Sc8cyHpD2wGE5J Inun0ns5f7pta2U61G+jfA049QFRgD1ZPiWC9Qs+Dy81FofLxdG53js0jGP9/WtA12aN 2bIR+9JUiAMkJQY2rrcbyr39l5wm/PRzTLITidBCT4JDrgGGXvlAIELFYQ8ws3EPOV7o mMNu3D3qt05Vc+UBV4x6ULO8EYMLKQ+uj1wOD7CTq4E8PW8sTSVzQ12EJ/T55egRE7VY egdCRJbdBOZZngt60D0GsldxojdXFvXKlE4dERM6/UBz+5osMaGvCqkEwsSto1rD0gLD EHBg==
X-Received: by 10.194.60.73 with SMTP id f9mr1879458wjr.65.1381766282993; Mon, 14 Oct 2013 08:58:02 -0700 (PDT)
Received: from [192.168.1.45] (25.Red-79-153-32.dynamicIP.rima-tde.net. [79.153.32.25]) by mx.google.com with ESMTPSA id dl10sm36024484wib.1.2013.10.14.08.58.00 for <pntaw@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Oct 2013 08:58:02 -0700 (PDT)
Message-ID: <525C148F.8070502@gmail.com>
Date: Mon, 14 Oct 2013 17:58:07 +0200
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
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>	<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>
In-Reply-To: <BLU402-EAS357ECBFC621A567B9D3A7B4931A0@phx.gbl>
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: Mon, 14 Oct 2013 15:58:16 -0000

+1,

IMO 6) will only have some benefits in the case one of the endpoint been 
a gateway, but you would still have to deal with 5), so you won't avoid 
needing a TURN server (in any of its flavors ;)

BR
Sergio
El 14/10/2013 17:08, Bernard Aboba escribió:
> Agree on Markus's summary. I am also not convinced on #6 being a MUST because so far there hasn't been a compelling use case.
>
>> On Oct 14, 2013, at 7:42 AM, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> wrote:
>>
>> On: 11 October 2013 13:22  Markus.Isomaki@nokia.com Wrote
>>
>>
>>> So, what is the overall set of traversal / connectivity / address
>>> gathering mechanisms the browser should support that you are
>>> advocating? Mine is:
>>>
>>> 1.) UDP host candidates (native interface) - MUST
>>> 2.)UDP server-reflexive candidates (STUN) - MUST
>>> 3.) UDP relay candidates via UDP (TURN) - MUST
>>> 4.) UDP relay candidates via TCP (TURN) - MUST
>>> 5.) UDP relay candidates via some HTTP/TLS compatible transport (TURN)
>>> - MUST/SHOULD
>>>    (TLS via HTTP CONNET or TURN over WebSockets have been proposed.)
>>> 6.) TCP based candidates (ICE-TCP) - MAY/SHOULD
>>>
>>> I believe 1.), 2.) and 3.) we all have consensus on, probably even on
>>> 4.). What we are discussing on this list is whether and how to do 5.),
>>> and how important 6.) is.
>>>
>>> My opinion is that 5.) becomes necessary due to the HTTP-limited
>>> environments you mention above. So the communication needs to be
>>> compliant with HTTP and its upgrade mechanisms. 6.) I see as an
>>> optimization to 4.) in cases where you can't do UDP but can establish
>>> outgoing TCP connections and the other peer can actually receive them.
>>> But that optimization does not hold very often, since most of the time
>>> browsers are in networks where they can't receive TCP connections from
>>> the "outside world". So that's why I see it as MAY or SHOULD. You may
>>> argue that often browsers may talk to gateways or central points that
>>> are reachable by TCP, and in those scenarios ICE-TCP might make sense.
>> Totally agree with the nice summary above and agree that 5) is necessary we have use cases in draft-ietf-rtcweb-use-cases-and-requirements that say we do. We need some mechanism that is HTTP compatible and we have these two options available and to me there is very little difference between them it is just a matter of whether the use of the additional websockets layers give us any benefit. I am not convinced that 6) is needed but might be some corner cases it satisfies.
>>
>> Andy
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From partha@parthasarathi.co.in  Mon Oct 14 11:31:42 2013
Return-Path: <partha@parthasarathi.co.in>
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 2782621E80B3 for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 11:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.132
X-Spam-Level: 
X-Spam-Status: No, score=-2.132 tagged_above=-999 required=5 tests=[AWL=-0.467, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_35=0.6]
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 M4DtOSWMEiah for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 11:31:37 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us2.mailhostbox.com [69.93.141.235]) by ietfa.amsl.com (Postfix) with ESMTP id 7E9DB21F936F for <pntaw@ietf.org>; Mon, 14 Oct 2013 11:31:27 -0700 (PDT)
Received: from userPC (unknown [122.172.182.21]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id 70FCB639297; Mon, 14 Oct 2013 18:30:26 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1381775431; bh=4u5So05Kwsarpo4iEZikwSqUoI//fe2LXzps/m4Q06E=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=Zod+nfdvmY8724rZbpConn5FR0X0nIe8Ep/CKJkzspGR7/CjcWSIFzRddWhu1apqm Nvg4h86KQfoyxxomhKEQOQGAqfKDMqKNGTWaqa3bgDzOaD5n5HToVCMhoauXJtZeS5 z45RzvuG0mLP0LMMmD0dNsyExchn5Qh5T5eF1kBU=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Chenxin \(Xin\)'" <hangzhou.chenxin@huawei.com>, <Markus.Isomaki@nokia.com>, <simon.perreault@viagenie.ca>, <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>	<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> <9E34D50A21D1D1489134B4D770CE039768081D1B@SZXEMA504-MBX.china.huawei.com>
In-Reply-To: <9E34D50A21D1D1489134B4D770CE039768081D1B@SZXEMA504-MBX.china.huawei.com>
Date: Tue, 15 Oct 2013 00:00:22 +0530
Message-ID: <00cc01cec90b$75faff90$61f0feb0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHOp7eh97CWvanNyUO4L+fWrmoYupmyO7sAgADeqQCAAKUrgIAADPKAgAAjEICANUrLAIAAB1IAgAGHKgCAAAkXAIABes4AgAAIDACAARCqIIAA8XlQgADDLECABanJQA==
Content-Language: en-us
X-CTCH-RefID: str=0001.0A02020A.525C3847.00FE, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.142
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 18:31:42 -0000

Xin,

<snip> The
> advantage
> >with
> >Media over HTTP is that HTTP friendly firewall shall filter out media
> from
> >HTTP traffic if required.
> [xin] And media over websocket should be a option. The sub-protocol
> attribute in websokcet could also provide the firewall friendly
> information, so the firewall could decide to filter out the media or
> not.
</snip>

Agreed. I'll write DTLS-SRTP over WebSocket draft for more clarity. =20

Please read inline.

Thanks
Partha

> -----Original Message-----
> From: Chenxin (Xin) [mailto:hangzhou.chenxin@huawei.com]
> Sent: Friday, October 11, 2013 9:28 AM
> To: Parthasarathi R; Markus.Isomaki@nokia.com;
> simon.perreault@viagenie.ca; pntaw@ietf.org
> Subject: RE: [pntaw] Real-time media over TCP
>=20
> Hi
> >Hi all,
> >
> >As I mentioned below, ICE-TCP is not replacement for TURN but ICE-TCP
> helps
> >for the browser-to-browser media flow without middle box (TURN
> Server).
> >Also, please note that both browsers behind UDP blocked firewall is
> not the
> >worst case scenario for WebRTC firewall requirements. The actual =
worst
> case
> >scenario is that both browsers are behind HTTP only firewalls and in
> this
> >scenario, both TURN server and ICE-TCP will not work. There is a need
> of one
> >more solution.
> >
> >AFAIK, HTTP allowing firewall is not happen by mis-configuration but
> it is
> >policy of the given network. It is more appropriate to pass the media
> over
> >HTTP based mechanism rather than finding the workarounds. The
> advantage
> >with
> >Media over HTTP is that HTTP friendly firewall shall filter out media
> from
> >HTTP traffic if required.
> [xin] And media over websocket should be a option. The sub-protocol
> attribute in websokcet could also provide the firewall friendly
> information, so the firewall could decide to filter out the media or
> not.
>=20
>  IMO, Media over HTTP based mechanism has to be
> >used for HTTP only firewall (Sec 3.2.3 of
> >draft-ietf-rtcweb-use-cases-and-requirements) requirement and ICE-TCP
> shall
> >be used for (Sec 3.2.3 of draft-ietf-rtcweb-use-cases-and-
> requirements)
> >requirement.
>=20
>   [Xin] I think you means ICE-TCP shall be used for (*Sec 3.2.2* of
> draft-ietf-rtcweb-use-cases-and-requirements) requirement.:)

<Partha> Thanks for the indicating the cut&paste issue :-(. Your =
thinking is
correct. </Partha>

>=20
> Thanks,
>   Xin
> >
> >Thanks
> >Partha
> >
> >> -----Original Message-----
> >> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> Behalf
> >> Of Chenxin (Xin)
> >> Sent: Thursday, October 10, 2013 7:23 AM
> >> To: Markus.Isomaki@nokia.com; partha@parthasarathi.co.in;
> >> simon.perreault@viagenie.ca; pntaw@ietf.org
> >> Subject: Re: [pntaw] Real-time media over TCP
> >>
> >> Hi
> >>
> >>  I agree that ICE-TCP should not replace TURN as a requirement for
> >> every browser to implement. If we need support ICE-TCP , should we
> >> support TURN-TCP too? I do not think ICE-TCP will be more useful
> >> without TURN-TCP in the scenario where both browsers is under the
> NAT
> >> /FW which block UDP.
> >>
> >>   I believe the user 1->TCP->TURN server 1->UDP->TURN server =
2->TCP-
> >> >user 2, which Harald wrote before is workable. It is easy to =
tunnel
> >> the data internally if we need use the same server, right?
> >>
> >> Best Regards,
> >>      Xin
> >>
> >>
> >> >-----Original Message-----
> >> >From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> Behalf
> >> Of
> >> >Markus.Isomaki@nokia.com
> >> >Sent: Thursday, October 10, 2013 1:30 AM
> >> >To: partha@parthasarathi.co.in; simon.perreault@viagenie.ca;
> >> pntaw@ietf.org
> >> >Subject: Re: [pntaw] Real-time media over TCP
> >> >
> >> >Hi,
> >> >
> >> >I think the clarification is that it is not possible to initiate
> TCP
> >> connections from
> >> >the "outside" of any NAT or most of the firewalls. So even if the
> FW
> >> does not
> >> >block TCP per se, it only allows TCP connections to be opened from
> the
> >> "inside".
> >> >
> >> >I believe ICE-TCP will typically work only in cases where at least
> one
> >> of the
> >> >endpoints is NOT behind a NAT or FW. In cases where both endpoints
> are
> >> behind
> >> >firewalls completely blocking all UDP, the only option is to use a
> >> relay (TURN)
> >> >with endpoint initiated TCP connections. ICE allows us to optimize
> >> connectivity
> >> >in special cases, but I think we need also to make the worst case
> >> scenarios to
> >> >work. For that reason I don't see that ICE-TCP could replace TURN
> as a
> >> >requirement for every browser to implement. In some specific
> >> deployments it
> >> >may be that TURN does not get used much or at all, but browsers =
are
> >> used
> >> >everywhere.
> >> >
> >> >Markus
> >> >
> >> >> -----Original Message-----
> >> >> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> >> Behalf
> >> >> Of ext Parthasarathi R
> >> >> Sent: 09 October, 2013 20:01
> >> >> To: 'Simon Perreault'; pntaw@ietf.org
> >> >> Subject: Re: [pntaw] Real-time media over TCP
> >> >>
> >> >> Hi Simon,
> >> >>
> >> >> I have seen only two requirements in
> >> >> draft-ietf-rtcweb-use-cases-and-requirements-11, NAT/FW that
> blocks
> >> UDP
> >> >> and FW that only allows http. The relevant draft snippet is
> attached
> >> as a note
> >> >> of this mail. I'm discussing about NAT/FW that blocks UDP
> >> requirement. In
> >> >> case you foresee that the requirement is not detailed now, we
> need
> >> to sort
> >> >> out the requirement first before discussion the solutions.
> >> >>
> >> >> Regards
> >> >> Partha
> >> >>
> >> >> PS: In draft-ietf-rtcweb-use-cases-and-requirements-11 snippet,
> >> >>
> >> >> 3.2.2.  Simple Video Communication Service, NAT/FW that blocks
> UDP
> >> >>
> >> >> 3.2.2.1.  Description
> >> >>
> >> >>    This use-case is almost identical to the Simple Video
> >> Communication
> >> >>    Service use-case (Section 3.2.1).  The difference is that one
> of
> >> the
> >> >>    users is behind a NAT that blocks UDP traffic.
> >> >>
> >> >> 3.2.3.  Simple Video Communication Service, FW that only allows
> http
> >> >>
> >> >> 3.2.3.1.  Description
> >> >>
> >> >>    This use-case is almost identical to the Simple Video
> >> Communication
> >> >>    Service use-case (Section 3.2.1).  The difference is that one
> of
> >> the
> >> >>    users is behind a FW that only allows http traffic.
> >> >>
> >> >> > -----Original Message-----
> >> >> > From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] =
On
> >> >> Behalf
> >> >> > Of Simon Perreault
> >> >> > Sent: Tuesday, October 08, 2013 11:55 PM
> >> >> > To: pntaw@ietf.org
> >> >> > Subject: Re: [pntaw] Real-time media over TCP
> >> >> >
> >> >> > Le 2013-10-08 19:52, Parthasarathi R a =E9crit :
> >> >> > > 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
> >> >> > _______________________________________________
> >> >> > pntaw mailing list
> >> >> > pntaw@ietf.org
> >> >> > https://www.ietf.org/mailman/listinfo/pntaw
> >> >>
> >> >> _______________________________________________
> >> >> pntaw mailing list
> >> >> pntaw@ietf.org
> >> >> https://www.ietf.org/mailman/listinfo/pntaw
> >> >_______________________________________________
> >> >pntaw mailing list
> >> >pntaw@ietf.org
> >> >https://www.ietf.org/mailman/listinfo/pntaw
> >> _______________________________________________
> >> pntaw mailing list
> >> pntaw@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pntaw


From partha@parthasarathi.co.in  Mon Oct 14 11:56:00 2013
Return-Path: <partha@parthasarathi.co.in>
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 B3DBE21E80EE for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 11:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 88K0-Ig6hM6r for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 11:55:56 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us2.mailhostbox.com [69.93.141.237]) by ietfa.amsl.com (Postfix) with ESMTP id C57E721F9A44 for <pntaw@ietf.org>; Mon, 14 Oct 2013 11:55:43 -0700 (PDT)
Received: from userPC (unknown [122.172.182.21]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id D2D8D639142 for <pntaw@ietf.org>; Mon, 14 Oct 2013 18:54:40 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1381776881; bh=q8lahyL0G8mARxNfVaFH1PNECeJuMTe/NA0B/E83qJ0=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=RNWPwTPiamIWcuptklZSs4Eg8E1h60zOjwzvcELVESx769SKtIAcmkxPeH2QosIti seEMmXYPtFzjxO91XPj032sIDZt15NEXAhH3WuFiXvVNBWtrahaidFHrofFetNJUY5 d9rQrU4n5UAzZ6otSsJgLcO3HU67+CsSW/xOrLfQ=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
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>	<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>
In-Reply-To: <525C148F.8070502@gmail.com>
Date: Tue, 15 Oct 2013 00:24:37 +0530
Message-ID: <00d401cec90e$d688d5a0$839a80e0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac7I9jgo2wfDX8ucSuitWLbDOSb1HwAFgCTQ
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020208.525C3DF1.00F9, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.142
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 18:56:01 -0000

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

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of Sergio Garcia Murillo
> Sent: Monday, October 14, 2013 9:28 PM
> To: pntaw@ietf.org
> Subject: Re: [pntaw] Real-time media over TCP
>=20
> +1,
>=20
> IMO 6) will only have some benefits in the case one of the endpoint
> been
> a gateway, but you would still have to deal with 5), so you won't =
avoid
> needing a TURN server (in any of its flavors ;)
>=20
> BR
> Sergio
> El 14/10/2013 17:08, Bernard Aboba escribi=F3:
> > Agree on Markus's summary. I am also not convinced on #6 being a =
MUST
> because so far there hasn't been a compelling use case.
> >
> >> On Oct 14, 2013, at 7:42 AM, "Hutton, Andrew"
> <andrew.hutton@siemens-enterprise.com> wrote:
> >>
> >> On: 11 October 2013 13:22  Markus.Isomaki@nokia.com Wrote
> >>
> >>
> >>> So, what is the overall set of traversal / connectivity / address
> >>> gathering mechanisms the browser should support that you are
> >>> advocating? Mine is:
> >>>
> >>> 1.) UDP host candidates (native interface) - MUST
> >>> 2.)UDP server-reflexive candidates (STUN) - MUST
> >>> 3.) UDP relay candidates via UDP (TURN) - MUST
> >>> 4.) UDP relay candidates via TCP (TURN) - MUST
> >>> 5.) UDP relay candidates via some HTTP/TLS compatible transport
> (TURN)
> >>> - MUST/SHOULD
> >>>    (TLS via HTTP CONNET or TURN over WebSockets have been
> proposed.)
> >>> 6.) TCP based candidates (ICE-TCP) - MAY/SHOULD
> >>>
> >>> I believe 1.), 2.) and 3.) we all have consensus on, probably even
> on
> >>> 4.). What we are discussing on this list is whether and how to do
> 5.),
> >>> and how important 6.) is.
> >>>
> >>> My opinion is that 5.) becomes necessary due to the HTTP-limited
> >>> environments you mention above. So the communication needs to be
> >>> compliant with HTTP and its upgrade mechanisms. 6.) I see as an
> >>> optimization to 4.) in cases where you can't do UDP but can
> establish
> >>> outgoing TCP connections and the other peer can actually receive
> them.
> >>> But that optimization does not hold very often, since most of the
> time
> >>> browsers are in networks where they can't receive TCP connections
> from
> >>> the "outside world". So that's why I see it as MAY or SHOULD. You
> may
> >>> argue that often browsers may talk to gateways or central points
> that
> >>> are reachable by TCP, and in those scenarios ICE-TCP might make
> sense.
> >> Totally agree with the nice summary above and agree that 5) is
> necessary we have use cases in draft-ietf-rtcweb-use-cases-and-
> requirements that say we do. We need some mechanism that is HTTP
> compatible and we have these two options available and to me there is
> very little difference between them it is just a matter of whether the
> use of the additional websockets layers give us any benefit. I am not
> convinced that 6) is needed but might be some corner cases it
> satisfies.
> >>
> >> Andy
> >> _______________________________________________
> >> pntaw mailing list
> >> pntaw@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pntaw
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw
>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From Markus.Isomaki@nokia.com  Mon Oct 14 12:15:41 2013
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 blocke=
d 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 connecti=
on would be better than TCP based relay, its success rate would be very sma=
ll. I suppose we agree that UDP based relay would still be better than dire=
ct 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
>=20
> Hi all,
>=20
> My point is that the direct media connection has to be given priority ove=
r
> 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
>=20
> 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 t=
raffic
> is a matter of missing text in the requirement.
>=20
> Thanks
> Partha
>=20

From pkyzivat@alum.mit.edu  Mon Oct 14 14:42:58 2013
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
>


From dwing@cisco.com  Mon Oct 14 17:01:33 2013
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,
>=20
> In practice I doubt you find many situations where UDP is completely =
blocked but incoming TCP connections from anywhere are allowed.

Agreed. =20

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.
>=20
> Markus
>=20
>> -----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
>>=20
>> Hi all,
>>=20
>> 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
>>=20
>> 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.
>>=20
>> Thanks
>> Partha
>>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From dwing@cisco.com  Mon Oct 14 17:04:49 2013
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 F419321F9FCF for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 17:04:48 -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 qnhcVsObhw9v for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 17:04:44 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 95A0921F9B0D for <pntaw@ietf.org>; Mon, 14 Oct 2013 17:04:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3041; q=dns/txt; s=iport; t=1381795484; x=1383005084; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=eUvFlINpmvVyjb/KwrnB0qJ7/7vnEFNlAGAVhqQJ3dI=; b=RMY6+RT82aAMigWjiQfFMqST/5H+ZpwiePUS4A4MgmWDwCBjbSctYBPS GYix6EEwcIBCPkNzeM+ZBy98s3Y39oKLeXVLcoFUqPP7gE0hzGZbZ8JVz 5UnJduM2HJDeUVN2SZL4Ozyj47z6aJo9UZDzIdE9Sphveh7UqjPSQnQF5 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAFaFXFKrRDoI/2dsb2JhbABZDoJ5OMJygSgWdIIlAQEBAwEBAQE3NAsFBwQLDgMEAQEBJwcnHwkIBhOIAAUNvWMEjhGBBjMHBoMZgQYDiTyOSJICgmVfHIE0
X-IronPort-AV: E=Sophos;i="4.93,494,1378857600"; d="scan'208";a="92143554"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 15 Oct 2013 00:04:43 +0000
Received: from dhcp-10-155-84-77.cisco.com (dhcp-10-155-84-77.cisco.com [10.155.84.77]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9F04guH029351; Tue, 15 Oct 2013 00:04:42 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: <525C655B.6020802@alum.mit.edu>
Date: Mon, 14 Oct 2013 17:04:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0AE4085A-CE50-4813-B03C-9A5FB86277BD@cisco.com>
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> <525C655B.6020802@ alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1510)
Cc: pntaw@ietf.org
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:04:49 -0000

On Oct 14, 2013, at 2:42 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 10/14/13 3:06 PM, Markus.Isomaki@nokia.com wrote:
>> Hi,
>>=20
>> 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.
>=20
> Doesn't that depend on where the relay is?
>=20
> UDP relayed across the world might not be preferable to TCP direct to =
a point down the street.
>=20
> But in practice I suppose the relay will be conveniently located =
relative to one of the two endpoints.

I think that is a separate problem.  Smart ICE candidate prioritization =
would choose the "best candidate" (for some value of "best candidate").  =
The ICE connectivity check round-trip time is an oft-cited example of a =
reasonable metric (although it doesn't measure bandwidth and packet loss =
is considered by some to mislead [but if a path is lossy it may indeed =
be a very undesirable path]).  Geolocation of the TURN IP address versus =
my own IP address could also influence ICE candidate prioritization or =
candidate selection.

-d


>=20
> 	Thanks,
> 	Paul
>=20
>> Markus
>>=20
>>> -----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
>>>=20
>>> Hi all,
>>>=20
>>> 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
>>>=20
>>> 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.
>>>=20
>>> Thanks
>>> Partha
>>>=20
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
>>=20
>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From ted.ietf@gmail.com  Mon Oct 14 17:08:45 2013
Return-Path: <ted.ietf@gmail.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 2E80121E813D for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 17:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 qVtx6pjpqYNH for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 17:08:44 -0700 (PDT)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id E8EB021E80E5 for <pntaw@ietf.org>; Mon, 14 Oct 2013 17:08:41 -0700 (PDT)
Received: by mail-ie0-f182.google.com with SMTP id as1so12240732iec.27 for <pntaw@ietf.org>; Mon, 14 Oct 2013 17:08:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oMHalfgPlIOc8+CSVsEKEdNAmJb5IveqoJGPXXk/ThA=; b=GpkWINpcZ2VGwQmIFutinuxE4lVi5HHBbGPIVC/rs+9ji1Z7KLc9zK3jrdoJ4gK8+a mFO+NGFXAyxXlxA0sFYnwDX7uKOELjDh1c5teHg6KiP5ydEQRxoOL8BboLujun/TXUjF wp4xUyBf5LQDD5BVcnCNVAfSd26Hy0ymDpPDK1lCQFdmokoLelsjxfMlDmYj+gSO1IcB iubU5eoQvyCxKRVAka1rboeCiibDxi050FstfIInN97QNnPp8vz7hp9QzBhwJZmsny6P oHA3jPfRsg8afWg4WeXlecdkRYUVR1sIXMZIoIHVq1TU5POcnaFYmtXJuN/rs8k9lCis 4xXA==
MIME-Version: 1.0
X-Received: by 10.50.120.10 with SMTP id ky10mr15222233igb.29.1381795721467; Mon, 14 Oct 2013 17:08:41 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Mon, 14 Oct 2013 17:08:41 -0700 (PDT)
In-Reply-To: <0AE4085A-CE50-4813-B03C-9A5FB86277BD@cisco.com>
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> <525C655B.6020802@alum.mit.edu> <0AE4085A-CE50-4813-B03C-9A5FB86277BD@cisco.com>
Date: Mon, 14 Oct 2013 17:08:41 -0700
Message-ID: <CA+9kkMDofv4+nhAWhxVBT6dFy55uyCVCx=EEsatWiU=WvAhKKA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: multipart/alternative; boundary=047d7ba98232215de304e8bc6352
Cc: pntaw@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
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:08:45 -0000

--047d7ba98232215de304e8bc6352
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Oct 14, 2013 at 5:04 PM, Dan Wing <dwing@cisco.com> wrote:

>
> On Oct 14, 2013, at 2:42 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>
> > But in practice I suppose the relay will be conveniently located
> relative to one of the two endpoints.
>
> I think that is a separate problem.  Smart ICE candidate prioritization
> would choose the "best candidate" (for some value of "best candidate").
>  The ICE connectivity check round-trip time is an oft-cited example of a
> reasonable metric (although it doesn't measure bandwidth and packet loss is
> considered by some to mislead [but if a path is lossy it may indeed be a
> very undesirable path]).  Geolocation of the TURN IP address versus my own
> IP address could also influence ICE candidate prioritization or candidate
> selection.
>
> -d
>
>
Hi Dan,

I don't think I understand who is running a geolocation algorithm in this
scenario.  Can you elaborate?

regards,

Ted



>
> >
> >       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
> >>
> >
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw
>
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw
>

--047d7ba98232215de304e8bc6352
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Oct 14, 2013 at 5:04 PM, Dan Wing <span dir=3D"ltr=
">&lt;<a href=3D"mailto:dwing@cisco.com" target=3D"_blank">dwing@cisco.com<=
/a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quo=
te"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
On Oct 14, 2013, at 2:42 PM, Paul Kyzivat &lt;<a href=3D"mailto:pkyzivat@al=
um.mit.edu">pkyzivat@alum.mit.edu</a>&gt; wrote:<br>
<br>
&gt; But in practice I suppose the relay will be conveniently located relat=
ive to one of the two endpoints.<br>
<br>
</div>I think that is a separate problem. =A0Smart ICE candidate prioritiza=
tion would choose the &quot;best candidate&quot; (for some value of &quot;b=
est candidate&quot;). =A0The ICE connectivity check round-trip time is an o=
ft-cited example of a reasonable metric (although it doesn&#39;t measure ba=
ndwidth and packet loss is considered by some to mislead [but if a path is =
lossy it may indeed be a very undesirable path]). =A0Geolocation of the TUR=
N IP address versus my own IP address could also influence ICE candidate pr=
ioritization or candidate selection.<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-d<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br></div></div></blo=
ckquote><div><br></div><div>Hi Dan,<br><br></div><div>I don&#39;t think I u=
nderstand who is running a geolocation algorithm in this scenario.=A0 Can y=
ou elaborate?<br>
<br>regards,<br><br></div><div>Ted<br></div><div><br>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">
<br>
&gt;<br>
&gt; =A0 =A0 =A0 Thanks,<br>
&gt; =A0 =A0 =A0 Paul<br>
&gt;<br>
&gt;&gt; Markus<br>
&gt;&gt;<br>
&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt; From: <a href=3D"mailto:pntaw-bounces@ietf.org">pntaw-bounces@=
ietf.org</a> [mailto:<a href=3D"mailto:pntaw-bounces@ietf.org">pntaw-bounce=
s@ietf.org</a>] On Behalf<br>
&gt;&gt;&gt; Of ext Parthasarathi R<br>
&gt;&gt;&gt; Sent: 14 October, 2013 21:55<br>
&gt;&gt;&gt; To: <a href=3D"mailto:pntaw@ietf.org">pntaw@ietf.org</a><br>
&gt;&gt;&gt; Subject: Re: [pntaw] Real-time media over TCP<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Hi all,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; My point is that the direct media connection has to be given p=
riority over<br>
&gt;&gt;&gt; TURN based mechanism. In case of ICE-TCP, there is a possibili=
ty for the<br>
&gt;&gt;&gt; direction connection between two browsers involved in the WebR=
TC session<br>
&gt;&gt;&gt; and should be given priority over TURN based mechanism. So, 6)=
 TCP based<br>
&gt;&gt;&gt; candidates (ICE-TCP) - MUST<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; There is an assumption in the discussion that the incoming TCP=
 traffic is not<br>
&gt;&gt;&gt; allowed through firewall. In case it is the problem to be solv=
ed, RTCWeb<br>
&gt;&gt;&gt; usecase and requirement has to be updated. I noticed in<br>
&gt;&gt;&gt; draft-ietf-rtcweb-use-cases-and-requirements-12 (published tod=
ay) that<br>
&gt;&gt;&gt; there is no such requirement. I&#39;ll write the mail in RTCWe=
b WG to get the<br>
&gt;&gt;&gt; clarity on the requirement in case the firewall forbidding inc=
oming TCP traffic<br>
&gt;&gt;&gt; is a matter of missing text in the requirement.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Thanks<br>
&gt;&gt;&gt; Partha<br>
&gt;&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; pntaw mailing list<br>
&gt;&gt; <a href=3D"mailto:pntaw@ietf.org">pntaw@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pntaw" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/pntaw</a><br>
&gt;&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; pntaw mailing list<br>
&gt; <a href=3D"mailto:pntaw@ietf.org">pntaw@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pntaw" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/pntaw</a><br>
<br>
_______________________________________________<br>
pntaw mailing list<br>
<a href=3D"mailto:pntaw@ietf.org">pntaw@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pntaw" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/pntaw</a><br>
</div></div></blockquote></div><br></div></div>

--047d7ba98232215de304e8bc6352--

From dwing@cisco.com  Mon Oct 14 17:52:56 2013
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 6E29921E8134 for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 17:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 NH+28NflACOK for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 17:52:52 -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 0F7B121E811D for <pntaw@ietf.org>; Mon, 14 Oct 2013 17:52:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9269; q=dns/txt; s=iport; t=1381798370; x=1383007970; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=yC2VExo+44AmDjub78auUY9LMxBzEVjhn7U5CoN/3LA=; b=BrfS9SJxsM2vR2ST0XJ7/CLIBpv8+kZsJtzTUsZKHTkgnCNKLYIp+PFf aNSoE+MmPAmQ+dhOKJqp0RGh5mv7Hhd1bu4Rv/h8LH4Ji6YSuK4VxFcWL vpC5JLMaMi0yO0mQdxUmm0lB7i/zOwVoJL4LVP8PZMarBpgtQUYhhJmdF 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAMyQXFKrRDoI/2dsb2JhbABZgwc4wnGBJxZ0giUBAQEDAQEBAWsLBQcECxEEAQEBJwchBh8JCAYTh3QDCQUNs2wNiWcEjFyBNYE1BAcGgxmBBgOJPIxfgWmMTIU2g0QcgTQ
X-IronPort-AV: E=Sophos;i="4.93,495,1378857600"; d="scan'208,217";a="94721539"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 15 Oct 2013 00:52:49 +0000
Received: from dhcp-10-155-84-77.cisco.com (dhcp-10-155-84-77.cisco.com [10.155.84.77]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9F0qmS2027544; Tue, 15 Oct 2013 00:52:48 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_A2656246-BE9D-4D83-A720-67713EC58FE7"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <CA+9kkMDofv4+nhAWhxVBT6dFy55uyCVCx=EEsatWiU=WvAhKKA@mail.gmail.com>
Date: Mon, 14 Oct 2013 17:52:50 -0700
Message-Id: <557505AD-86DB-41D5-9ED7-71223D4937A9@cisco.com>
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> <525C655B.6020802@ alum.mit.edu> <0AE4085A-CE50-4813-B03C-9A5FB86277BD@cisco.com> <CA+9kkMDofv4+nhAWhxVBT6dFy55uyCVCx=EEsatWiU=WvAhKKA@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: pntaw@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
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:52:56 -0000

--Apple-Mail=_A2656246-BE9D-4D83-A720-67713EC58FE7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 14, 2013, at 5:08 PM, Ted Hardie <ted.ietf@gmail.com> wrote:

> On Mon, Oct 14, 2013 at 5:04 PM, Dan Wing <dwing@cisco.com> wrote:
>=20
> On Oct 14, 2013, at 2:42 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=20
> > But in practice I suppose the relay will be conveniently located =
relative to one of the two endpoints.
>=20
> I think that is a separate problem.  Smart ICE candidate =
prioritization would choose the "best candidate" (for some value of =
"best candidate").  The ICE connectivity check round-trip time is an =
oft-cited example of a reasonable metric (although it doesn't measure =
bandwidth and packet loss is considered by some to mislead [but if a =
path is lossy it may indeed be a very undesirable path]).  Geolocation =
of the TURN IP address versus my own IP address could also influence ICE =
candidate prioritization or candidate selection.
>=20
> -d
>=20
>=20
> Hi Dan,
>=20
> I don't think I understand who is running a geolocation algorithm in =
this scenario.  Can you elaborate?

The RTCWEB host.  For example, it could ask a geolocation service how =
many miles away the TURN server's IP address is from itself.  I'm not =
saying this is better than just doing a STUN transaction with that same =
TURN server; I just wanted another way to influence ICE candidate =
selection.

-d


>=20
> regards,
>=20
> Ted
>=20
> =20
>=20
> >
> >       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
> >>
> >
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw
>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw
>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


--Apple-Mail=_A2656246-BE9D-4D83-A720-67713EC58FE7
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 14, 2013, at 5:08 PM, Ted Hardie &lt;<a href="mailto:ted.ietf@gmail.com">ted.ietf@gmail.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><div dir="ltr">On Mon, Oct 14, 2013 at 5:04 PM, Dan Wing <span dir="ltr">&lt;<a href="mailto:dwing@cisco.com" target="_blank">dwing@cisco.com</a>&gt;</span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div class="im"><br>
On Oct 14, 2013, at 2:42 PM, Paul Kyzivat &lt;<a href="mailto:pkyzivat@alum.mit.edu">pkyzivat@alum.mit.edu</a>&gt; wrote:<br>
<br>
&gt; But in practice I suppose the relay will be conveniently located relative to one of the two endpoints.<br>
<br>
</div>I think that is a separate problem. &nbsp;Smart ICE candidate prioritization would choose the "best candidate" (for some value of "best candidate"). &nbsp;The ICE connectivity check round-trip time is an oft-cited example of a reasonable metric (although it doesn't measure bandwidth and packet loss is considered by some to mislead [but if a path is lossy it may indeed be a very undesirable path]). &nbsp;Geolocation of the TURN IP address versus my own IP address could also influence ICE candidate prioritization or candidate selection.<br>

<span class="HOEnZb"><font color="#888888"><br>
-d<br>
</font></span><div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>Hi Dan,<br><br></div><div>I don't think I understand who is running a geolocation algorithm in this scenario.&nbsp; Can you elaborate?<br></div></div></div></div></blockquote><div><br></div><div>The RTCWEB host. &nbsp;For example, it could ask a geolocation service how many miles away the TURN server's IP address is from itself. &nbsp;I'm not saying this is better than just doing a STUN transaction with that same TURN server; I just wanted another way to influence ICE candidate selection.</div><div><br></div><div>-d</div><div><br></div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>
<br>regards,<br><br></div><div>Ted<br></div><div><br>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; Thanks,<br>
&gt; &nbsp; &nbsp; &nbsp; Paul<br>
&gt;<br>
&gt;&gt; Markus<br>
&gt;&gt;<br>
&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt; From: <a href="mailto:pntaw-bounces@ietf.org">pntaw-bounces@ietf.org</a> [mailto:<a href="mailto:pntaw-bounces@ietf.org">pntaw-bounces@ietf.org</a>] On Behalf<br>
&gt;&gt;&gt; Of ext Parthasarathi R<br>
&gt;&gt;&gt; Sent: 14 October, 2013 21:55<br>
&gt;&gt;&gt; To: <a href="mailto:pntaw@ietf.org">pntaw@ietf.org</a><br>
&gt;&gt;&gt; Subject: Re: [pntaw] Real-time media over TCP<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Hi all,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; My point is that the direct media connection has to be given priority over<br>
&gt;&gt;&gt; TURN based mechanism. In case of ICE-TCP, there is a possibility for the<br>
&gt;&gt;&gt; direction connection between two browsers involved in the WebRTC session<br>
&gt;&gt;&gt; and should be given priority over TURN based mechanism. So, 6) TCP based<br>
&gt;&gt;&gt; candidates (ICE-TCP) - MUST<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; There is an assumption in the discussion that the incoming TCP traffic is not<br>
&gt;&gt;&gt; allowed through firewall. In case it is the problem to be solved, RTCWeb<br>
&gt;&gt;&gt; usecase and requirement has to be updated. I noticed in<br>
&gt;&gt;&gt; draft-ietf-rtcweb-use-cases-and-requirements-12 (published today) that<br>
&gt;&gt;&gt; there is no such requirement. I'll write the mail in RTCWeb WG to get the<br>
&gt;&gt;&gt; clarity on the requirement in case the firewall forbidding incoming TCP traffic<br>
&gt;&gt;&gt; is a matter of missing text in the requirement.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Thanks<br>
&gt;&gt;&gt; Partha<br>
&gt;&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; pntaw mailing list<br>
&gt;&gt; <a href="mailto:pntaw@ietf.org">pntaw@ietf.org</a><br>
&gt;&gt; <a href="https://www.ietf.org/mailman/listinfo/pntaw" target="_blank">https://www.ietf.org/mailman/listinfo/pntaw</a><br>
&gt;&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; pntaw mailing list<br>
&gt; <a href="mailto:pntaw@ietf.org">pntaw@ietf.org</a><br>
&gt; <a href="https://www.ietf.org/mailman/listinfo/pntaw" target="_blank">https://www.ietf.org/mailman/listinfo/pntaw</a><br>
<br>
_______________________________________________<br>
pntaw mailing list<br>
<a href="mailto:pntaw@ietf.org">pntaw@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/pntaw" target="_blank">https://www.ietf.org/mailman/listinfo/pntaw</a><br>
</div></div></blockquote></div><br></div></div>
_______________________________________________<br>pntaw mailing list<br><a href="mailto:pntaw@ietf.org">pntaw@ietf.org</a><br>https://www.ietf.org/mailman/listinfo/pntaw<br></blockquote></div><br></body></html>
--Apple-Mail=_A2656246-BE9D-4D83-A720-67713EC58FE7--

From tireddy@cisco.com  Mon Oct 14 23:02:41 2013
Return-Path: <tireddy@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 183D011E80F5 for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 23:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 DrOdSYvQX8dr for <pntaw@ietfa.amsl.com>; Mon, 14 Oct 2013 23:02:36 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 32B7811E8108 for <pntaw@ietf.org>; Mon, 14 Oct 2013 23:02:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3160; q=dns/txt; s=iport; t=1381816956; x=1383026556; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=mKuWhuJ8EDNfpptCDIiBye09C3QTeqVjQJyAe9WELMs=; b=k5b5TcliR1vusNluJb0xQcC7seE5lIxtESsiRtFYJqjeJehn//IM9xwJ j7Qg5tNfYrEvb1ZRqOIxjQX7jKScugL2f8mv3MDcOHtv5avCrIxR0ecK7 3w6L/wec+x1Dy075VTyvaMUF3MK8HS8E1G56HOQtfyUAh0QNln5FOrmNO M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjQFALTZXFKtJV2a/2dsb2JhbABZgwc4UsIkgRsWdIIlAQEBBAEBARUiNAsMBAIBCBEEAQEBChQJBycLFAkIAgQBDQUIh34MvVKOEYEIMQcGgxmBBgOZM5BTgySBcDk
X-IronPort-AV: E=Sophos;i="4.93,497,1378857600"; d="scan'208";a="272133388"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-7.cisco.com with ESMTP; 15 Oct 2013 06:02:35 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9F62ZdI010581 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 15 Oct 2013 06:02:35 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.33]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.004; Tue, 15 Oct 2013 01:02:34 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "Dan Wing (dwing)" <dwing@cisco.com>, "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>
Thread-Topic: [pntaw] Real-time media over TCP
Thread-Index: AQHOpWloM84ernwvrk6QQTyfUdhsoJmyd8iAgACifgCAAN6pAIAApSqAgAAM8oCAACMRgIA1SsoAgAAHUgCAAYcqAIAACRcAgAF6zwCAAAgMAIAAjHMAgAEIyICAATlMgIAE3kWAgAAHZgCAAA3RgIAAMVCAgAADQICAAFJ5AP//8Pjw
Date: Tue, 15 Oct 2013 06:02:34 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A2000EB57@xmb-rcd-x10.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> <A51F486D-3BC0-4090-80CD-B4A15AC3EE69@cisco.com>
In-Reply-To: <A51F486D-3BC0-4090-80CD-B4A15AC3EE69@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.56.33]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pntaw@ietf.org" <pntaw@ietf.org>, "partha@parthasarathi.co.in" <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 06:02:41 -0000

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf Of=
 Dan
> Wing (dwing)
> Sent: Tuesday, October 15, 2013 5:31 AM
> To: Markus.Isomaki@nokia.com
> Cc: pntaw@ietf.org; partha@parthasarathi.co.in
> Subject: Re: [pntaw] Real-time media over TCP
>=20
>=20
> On Oct 14, 2013, at 12:06 PM, Markus.Isomaki@nokia.com wrote:
>=20
> > Hi,
> >
> > In practice I doubt you find many situations where UDP is completely bl=
ocked
> but incoming TCP connections from anywhere are allowed.
>=20
> Agreed.
>=20
> But if both ends are trying to communicate with each other, their
> communications will appear as a TCP simultaneous-open.  That could (in fa=
ct,
> "should") work across a firewall because the firewall will see an outboun=
d SYN
> to a host/port after which it will see an inbound SYN from that same
> host/port.

But firewall TCP inspection causes the inbound SYN from the same host/port =
to be dropped (Firewalls typically do not permit TCP simultaneous-open). Ev=
en with NAT as per the survey results in ICE TCP (http://tools.ietf.org/htm=
l/rfc6544#appendix-A) TCP simultaneous-open worked only in roughly 45% of t=
he cases.

-Tiru.

>=20
> -d
>=20
>=20
> > 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 r=
ate
> 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 t=
he
> >> direction connection between two browsers involved in the WebRTC sessi=
on
> >> and should be given priority over TURN based mechanism. So, 6) TCP bas=
ed
> >> 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, RTCW=
eb
> >> 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 TC=
P
> 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
>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

From dwing@cisco.com  Tue Oct 15 09:16:37 2013
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 9987E11E818C for <pntaw@ietfa.amsl.com>; Tue, 15 Oct 2013 09:16:36 -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 JwF1tPePlh51 for <pntaw@ietfa.amsl.com>; Tue, 15 Oct 2013 09:16:28 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id F327121F9302 for <pntaw@ietf.org>; Tue, 15 Oct 2013 09:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3510; q=dns/txt; s=iport; t=1381853758; x=1383063358; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=eUJ3z57FbB1hA9gAKF5IqiVXDsFE2Bof3RjkpkuQI58=; b=OBTi2flXi9tmos+eymr1PXwpIxiDuLD2HbDQjHuaUjLNs193gR3ug7lI hpFbvjSGKcldJPNLU7ax01v+TV6/jRtPIqlnG+BJvjLFg992Ai1z54ISA iUsSKro1bhP48pOfVwpU+WEBm6oIPpv1bSRtQ8IG3pVdA+wtbMFQAnfpC Y=;
X-IronPort-AV: E=Sophos;i="4.93,500,1378857600"; d="scan'208";a="91484664"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 15 Oct 2013 16:15:58 +0000
Received: from dhcp-10-155-136-255.cisco.com (dhcp-10-155-136-255.cisco.com [10.155.136.255]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9FGFv5r004004; Tue, 15 Oct 2013 16:15:57 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: <913383AAA69FF945B8F946018B75898A2000EB57@xmb-rcd-x10.cisco.com>
Date: Tue, 15 Oct 2013 09:15:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F31D947-AB62-431A-875D-FCBAA2D38290@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> <A51F486D-3BC0-4090-80CD-B4A15AC3EE69@cisco.com> <913383AAA69FF945B8F946018B75898A2000EB57@xmb-rcd-x10.cisco.com>
To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
X-Mailer: Apple Mail (2.1510)
Cc: "pntaw@ietf.org" <pntaw@ietf.org>, "partha@parthasarathi.co.in" <partha@parthasarathi.co.in>, "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>
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 16:16:38 -0000

On Oct 14, 2013, at 11:02 PM, Tirumaleswar Reddy (tireddy) =
<tireddy@cisco.com> wrote:

>> -----Original Message-----
>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On =
Behalf Of Dan
>> Wing (dwing)
>> Sent: Tuesday, October 15, 2013 5:31 AM
>> To: Markus.Isomaki@nokia.com
>> Cc: pntaw@ietf.org; partha@parthasarathi.co.in
>> Subject: Re: [pntaw] Real-time media over TCP
>>=20
>>=20
>> On Oct 14, 2013, at 12:06 PM, Markus.Isomaki@nokia.com wrote:
>>=20
>>> Hi,
>>>=20
>>> In practice I doubt you find many situations where UDP is completely =
blocked
>> but incoming TCP connections from anywhere are allowed.
>>=20
>> Agreed.
>>=20
>> 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.
>=20
> But firewall TCP inspection causes the inbound SYN from the same =
host/port to be dropped (Firewalls typically do not permit TCP =
simultaneous-open). Even with NAT as per the survey results in ICE TCP =
(http://tools.ietf.org/html/rfc6544#appendix-A) TCP simultaneous-open =
worked only in roughly 45% of the cases.

If avoiding TURN improves the user experience, and IT policy says TCP is =
allowed, I expect firewall vendors would make sure TCP simultaneous open =
works.

-d


>=20
> -Tiru.
>=20
>>=20
>> -d
>>=20
>>=20
>>> 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.
>>>=20
>>> Markus
>>>=20
>>>> -----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
>>>>=20
>>>> Hi all,
>>>>=20
>>>> 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
>>>>=20
>>>> 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.
>>>>=20
>>>> Thanks
>>>> Partha
>>>>=20
>>> _______________________________________________
>>> pntaw mailing list
>>> pntaw@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pntaw
>>=20
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw


From harald@alvestrand.no  Wed Oct 16 05:02:57 2013
Return-Path: <harald@alvestrand.no>
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 C71B121F9C1D for <pntaw@ietfa.amsl.com>; Wed, 16 Oct 2013 05:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.385
X-Spam-Level: 
X-Spam-Status: No, score=-110.385 tagged_above=-999 required=5 tests=[AWL=0.214, 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 mv7sQ6a-UK2B for <pntaw@ietfa.amsl.com>; Wed, 16 Oct 2013 05:02:53 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 932B311E81C7 for <pntaw@ietf.org>; Wed, 16 Oct 2013 05:02:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 0855B39E1BB for <pntaw@ietf.org>; Wed, 16 Oct 2013 14:02:53 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tpzHn-uNWwaD for <pntaw@ietf.org>; Wed, 16 Oct 2013 14:02:52 +0200 (CEST)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:7646:a0ff:fe90:e2bb]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id F1F8B39E132 for <pntaw@ietf.org>; Wed, 16 Oct 2013 14:02:51 +0200 (CEST)
Message-ID: <525E806B.5060401@alvestrand.no>
Date: Wed, 16 Oct 2013 14:02:51 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: pntaw@ietf.org
References: <CAGTXFp92jSzQz05uHngzscz88n=fT_JPbEvQRxgeUUqPVRQUyQ@mail.gmail.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>	<A51F486D-3BC0-4090-80CD-B4A15AC3EE69@cisco.com>	<913383AAA69FF945B8F946018B75898A2000EB57@xmb-rcd-x10.cisco.com> <8F31D947-AB62-431A-875D-FCBAA2D38290@cisco.com>
In-Reply-To: <8F31D947-AB62-431A-875D-FCBAA2D38290@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 16 Oct 2013 12:02:57 -0000

On 10/15/2013 06:15 PM, Dan Wing wrote:
> On Oct 14, 2013, at 11:02 PM, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com> wrote:
>
>>> -----Original Message-----
>>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf Of Dan
>>> Wing (dwing)
>>> Sent: Tuesday, October 15, 2013 5:31 AM
>>> To: Markus.Isomaki@nokia.com
>>> Cc: pntaw@ietf.org; partha@parthasarathi.co.in
>>> Subject: Re: [pntaw] Real-time media over TCP
>>>
>>>
>>> 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.
>> But firewall TCP inspection causes the inbound SYN from the same host/port to be dropped (Firewalls typically do not permit TCP simultaneous-open). Even with NAT as per the survey results in ICE TCP (http://tools.ietf.org/html/rfc6544#appendix-A) TCP simultaneous-open worked only in roughly 45% of the cases.
> If avoiding TURN improves the user experience, and IT policy says TCP is allowed, I expect firewall vendors would make sure TCP simultaneous open works.
>
>
If something improves the user experience if it is possible to do it, 
but the basic functionality works without it, and it's unclear whether 
the special circumstances under which it's going to improve the user 
experience in fact exist in the field, I think that's perfect for a MAY 
implement.


From partha@parthasarathi.co.in  Sun Oct 20 09:11:06 2013
Return-Path: <partha@parthasarathi.co.in>
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 05C0111E822F for <pntaw@ietfa.amsl.com>; Sun, 20 Oct 2013 09:11:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.932
X-Spam-Level: 
X-Spam-Status: No, score=-0.932 tagged_above=-999 required=5 tests=[AWL=-0.526, BAYES_20=-0.74, IP_NOT_FRIENDLY=0.334]
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 O-AWJB6x6Dbe for <pntaw@ietfa.amsl.com>; Sun, 20 Oct 2013 09:11:01 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us2.mailhostbox.com [69.93.141.237]) by ietfa.amsl.com (Postfix) with ESMTP id B634111E81F0 for <pntaw@ietf.org>; Sun, 20 Oct 2013 09:11:01 -0700 (PDT)
Received: from userPC (unknown [122.179.103.73]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id D7B1C639103; Sun, 20 Oct 2013 16:10:57 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1382285460; bh=1U7qGbkS1K8Wmy2yYY7RwBO+VWk1aPEl/CiEeKfu2V8=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=kCOgEa9AGmJwYmf/TNznU6EE8nMYe2Sq+GQTMmH4DeNZ17RAnh8/W7jAUu653lju9 UtNDjLtuGTowCoEy+wegAD/pCqRlpNJTFirMfL6Kxgx/tmglzexGs9Y4wOUQDSs/F5 m6Jdb6+ijn4g+jP/A6L4u+F9ZebIiO9m/JS9mP6I=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Harald Alvestrand'" <harald@alvestrand.no>, <pntaw@ietf.org>
References: <CAGTXFp92jSzQz05uHngzscz88n=fT_JPbEvQRxgeUUqPVRQUyQ@mail.gmail.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>	<A51F486D-3BC0-4090-80CD-B4A15AC3EE69@cisco.com>	<913383AAA69FF945B8F946018B75898A2000EB57@xmb-rcd-x10.cisco.com>	<8F31D947-AB62-431A-875D-FCBAA2D38290@cisco.com> <525E806B.5060401@ alvestrand.no>
In-Reply-To: <525E806B.5060401@alvestrand.no>
Date: Sun, 20 Oct 2013 21:40:53 +0530
Message-ID: <000801cecdae$f6713160$e3539420$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac7KZ6iicREpjHj0Tm+KWS0ONEzwnADQ9BdA
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020203.52640094.0053, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.142
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: Sun, 20 Oct 2013 16:11:06 -0000

Hi Harald & all,

I agree that ICE-TCP qualifies for "MAY" requirement in case both browsers
are behind firewall. ICE-TCP is good for usecase wherein only one of the
browsers is behind firewall. Existing WebRTC usecase namely FedEx call is
good example for only one browser behind firewall wherein IVR is not going
to be behind UDP blocking firewall. In those usecases, ICE-TCP candidates
has merits over TURN relay candidates. IMO, ICE-TCP MUST be considered.

The current WebRTC FW usecase is (accidentially) inline with one of the
browser behind firewall scenario as mentioned in sec 3.3.2.1 of
draft-ietf-rtcweb-use-cases-and-requirements-12:

"The difference is that one of the users is behind a NAT that blocks UDP
traffic."

Thanks
Partha

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of Harald Alvestrand
> Sent: Wednesday, October 16, 2013 5:33 PM
> To: pntaw@ietf.org
> Subject: Re: [pntaw] Real-time media over TCP
> 
> On 10/15/2013 06:15 PM, Dan Wing wrote:
> > On Oct 14, 2013, at 11:02 PM, Tirumaleswar Reddy (tireddy)
> <tireddy@cisco.com> wrote:
> >
> >>> -----Original Message-----
> >>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> Behalf Of Dan
> >>> Wing (dwing)
> >>> Sent: Tuesday, October 15, 2013 5:31 AM
> >>> To: Markus.Isomaki@nokia.com
> >>> Cc: pntaw@ietf.org; partha@parthasarathi.co.in
> >>> Subject: Re: [pntaw] Real-time media over TCP
> >>>
> >>>
> >>> 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.
> >> But firewall TCP inspection causes the inbound SYN from the same
> host/port to be dropped (Firewalls typically do not permit TCP
> simultaneous-open). Even with NAT as per the survey results in ICE TCP
> (http://tools.ietf.org/html/rfc6544#appendix-A) TCP simultaneous-open
> worked only in roughly 45% of the cases.
> > If avoiding TURN improves the user experience, and IT policy says TCP
> is allowed, I expect firewall vendors would make sure TCP simultaneous
> open works.
> >
> >
> If something improves the user experience if it is possible to do it,
> but the basic functionality works without it, and it's unclear whether
> the special circumstances under which it's going to improve the user
> experience in fact exist in the field, I think that's perfect for a MAY
> implement.
> 
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

