RTCWeb Data Stream and RTP Synchronization
draft-mandyam-rtcweb-data-synch-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Giridhar Mandyam , Vijay Suryavanshi | ||
| Last updated | 2013-01-31 (Latest revision 2012-07-30) | ||
| 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 RTCWeb working group in the IETF is tasked with developing standards that will ensure interoperability between web browsers establishing rich communications sessions. This working group is tasked with delivering the specifications necessary to establish real-time transport sessions between browsers (e.g. those based on real-time protocol, i.e. RTP). Moreover, the group is also tasked with providing a means for application data streaming between browsers (i.e. opaque data streaming). Much like RTP synchronization sources (SSRC's) can be temporally synchronized, there are use cases that require opaque data stream synchronization with the real-time communications stream between browsers in an RTCWeb session. This document provides some options for temporally associating an opaque data stream with a voice/video stream as part of RTCWeb communications.
Authors
Giridhar Mandyam
Vijay Suryavanshi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)