RTCWeb ROAP XMPP/Jingle Interworking
draft-li-rtcweb-roap-jingle-interworking-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kepeng Li | ||
| Last updated | 2012-08-30 (Latest revision 2012-02-27) | ||
| 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
This document proposes behavior of a RTCWeb signaling gateway for mapping message representations between RTCWeb Offer/Answer Protocol (ROAP) scheme and XMPP/Jingle messaging scheme. Such a signaling gateway is intended to translate ROAP to/from XMPP/Jingle [XEP-0166] for enabling use cases between a RTCWeb enabled browser and legacy mobile devices which use XMPP/Jingle for signalling.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)