Open In-The-Wire Protocol for RTC-Web
draft-sipdoc-rtcweb-open-wire-protocol-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Inaki Baz Castillo , Jose Luis Millan , Saúl Ibarra Corretgé | ||
| Last updated | 2012-04-26 (Latest revision 2011-10-24) | ||
| 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
RTC-Web clients communicate with a server in order to request or manage realtime communications with other users. This document exposes four hypothetical and different RTC-Web scenarios and analyzes the requirements of the in-the-wire protocol in each of them. The aim of this document is to make RTC-Web properly fit in the nature of the Web.
Authors
Inaki Baz Castillo
Jose Luis Millan
Saúl Ibarra Corretgé
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)