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

["Chenxin (Xin)" <[e-mail]>]

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: [e-mail] [mailto:[e-mail]] 
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