Multiple Media Types in an RTP Session
draft-westerlund-avtcore-multi-media-rtp-session-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Magnus Westerlund , Colin Perkins , Jonathan Lennox | ||
| Last updated | 2012-10-12 (Latest revision 2012-07-09) | ||
| Replaced by | draft-ietf-avtcore-multi-media-rtp-session | ||
| 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-avtcore-multi-media-rtp-session | |
| 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 specifies how an RTP session can contain media streams with media from multiple media types such as audio, video, and text. This has been restricted by the RTP Specification, and thus this document updates RFC 3550 to enable this behavior for applications that satisfy the applicability for using multiple media types in a single RTP session.
Authors
Magnus Westerlund
Colin Perkins
Jonathan Lennox
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)