Re: [BEHAVE] [rtcweb] FW: New Version Notification for draft-chenxin-behave-turn-websocket-00.txt

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Wed, 15 May 2013 16:14 UTC

Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDCD421F8C69; Wed, 15 May 2013 09:14:57 -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 Me5UEFsQd3TR; Wed, 15 May 2013 09:14:53 -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 A7D5A21F8EFC; Wed, 15 May 2013 09:14:52 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 86FF91EB8473; Wed, 15 May 2013 18:14:51 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.159]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.02.0328.009; Wed, 15 May 2013 18:14:51 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "Chenxin (Xin)" <hangzhou.chenxin@huawei.com>, "behave@ietf.org" <behave@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "dispatch-bounces@ietf.org" <dispatch-bounces@ietf.org>
Thread-Topic: [rtcweb] FW: New Version Notification for draft-chenxin-behave-turn-websocket-00.txt
Thread-Index: AQHOUEBzwmg1PRmVTkGgLh5/jvIzeJkFdPzAgAD0rVA=
Date: Wed, 15 May 2013 16:14:50 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF11599668@MCHP04MSX.global-ad.net>
References: <9E34D50A21D1D1489134B4D770CE03974C6DC83A@szxeml538-mbs.china.huawei.com>
In-Reply-To: <9E34D50A21D1D1489134B4D770CE03974C6DC83A@szxeml538-mbs.china.huawei.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: [BEHAVE] [rtcweb] FW: New Version Notification for draft-chenxin-behave-turn-websocket-00.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 16:14:57 -0000

This is an interesting addition to the debate about how best to achieve connectivity for RTCWeb when the client is behind a restrictive firewall.

When we wrote the draft http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-considerations-00 we did not include this option because we did not see the benefit of additional transport options for TURN given that the existing options (E.g. TURN/TCP and TURN/TLS) seem to be meet our needs.

So what would be the benefits that justify this addition transport option for TURN?

Regarding F37 then this does need some rewording as I think the WG previously discussed as it needs to talk about the need for traffic to originate from the HTTP Proxy rather than allowing http traffic. That is probably worth a separate thread.

Regards
Andy



> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Chenxin (Xin)
> Sent: 15 May 2013 02:40
> To: behave@ietf.org; rtcweb@ietf.org; dispatch-bounces@ietf.org
> Subject: [rtcweb] FW: New Version Notification for draft-chenxin-
> behave-turn-websocket-00.txt
> 
> This draft defines a websocket extension to TURN to make TURN data have
> the ability to transport over the websocket connection.
> 
> This method could be a option to solve the Http-fallback requirement in
> RTCWEB.
> 
>     F37            The browser MUST be able to send streams and
>                    data to a peer in the presence of FWs that only
>                    allows http(s) traffic.
> 
> Besides, Turn server with websokcet extension could be a general relay
> server for some over websocket protocol, such as BFCP over websocket or
> MSRP over websocket. This could satisfy some Peer to Peer scene when
> using these protocol in the web environment , without a specific center
> server.
> 
> Comments and suggestions are welcome.
> 
> Best Regards,
>      Xin
> 
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Tuesday, May 14, 2013 9:15 AM
> To: Chenxin (Xin); Chenxin (Xin)
> Subject: New Version Notification for draft-chenxin-behave-turn-
> websocket-00.txt
> 
> 
> A new version of I-D, draft-chenxin-behave-turn-websocket-00.txt
> has been successfully submitted by Xin Chen and posted to the
> IETF repository.
> 
> Filename:	 draft-chenxin-behave-turn-websocket
> Revision:	 00
> Title:		 Traversal Using Relays around NAT (TURN) Extensions
> for Websocket Allocations
> Creation date:	 2013-05-13
> Group:		 Individual Submission
> Number of pages: 7
> URL:             http://www.ietf.org/internet-drafts/draft-chenxin-
> behave-turn-websocket-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-chenxin-behave-
> turn-websocket
> Htmlized:        http://tools.ietf.org/html/draft-chenxin-behave-turn-
> websocket-00
> 
> 
> Abstract:
>    This document defines an extension to TURN that allows it to run
> over
>    a Websocket [RFC6455] channel.  This will allow a client in a
>    restrictive network to exchange and relay media or data over the
>    websocket.
> 
> 
> 
> 
> The IETF Secretariat
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb