Considerations with RTCWeb in Telecom Smart Pipe
draft-zhao-rtcweb-telesmartpipe-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | zhaojzh@ctbri.com.cn , Xin Yang , Peng Liang , Hua Ye | ||
| Last updated | 2015-03-30 (Latest revision 2014-09-26) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Smart Pipe Service is telecom operator's opening of network capacities to ISPs, which can provide broadband speeding-up and QoS experience to end users. This document describes the mechanism to accelerate media stream transport in telecom operator's network of smart pipe for Real-Time Communication in WEB-browsers (WebRTC). Compared with packet mark on browser side, this mechanism focus on platform side.
Authors
zhaojzh@ctbri.com.cn
Xin Yang
Peng Liang
Hua Ye
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)