RTP Requirements for RTC-Web
draft-perkins-rtcweb-rtp-usage-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Colin Perkins , Magnus Westerlund , Joerg Ott | ||
| Last updated | 2011-10-25 (Latest revision 2011-08-28) | ||
| Replaced by | draft-ietf-rtcweb-rtp-usage | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-rtcweb-rtp-usage | |
| 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 memo discusses use of RTP in the context of the RTC-Web activity. It discusses important features of RTP that need to be considered by other parts of the RTC-Web framework, describes which RTP profile to use in this environment, and outlines what RTP extensions should be supported. This document is a candidate to become a work item of the RTCWEB working group as <WORKING GROUP DRAFT "MEDIA TRANSPORTS">.
Authors
Colin Perkins
Magnus Westerlund
Joerg Ott
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)