The WebRTC Data Channel as a Transport for the Message Session Relay Protocol (MSRP)
draft-pd-msrp-webrtc-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Peter Dunkley , Gavin Llewellyn | ||
| Last updated | 2013-11-11 (Latest revision 2013-05-10) | ||
| 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
The WebRTC Data Channel enables two-way real-time communication between browsers. This document updates normatively updates RFC 4975 to add support for WebRTC Data Channel as a transport for MSRP (Message Session Relay Protocol). This will enable secure, low- latency, structured peer-to-peer messaging between WebRTC end-points.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)