Sending Multiple Types of Media in a Single RTP Session
draft-ietf-avtcore-multi-media-rtp-session-05
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8860.
Expired & archived
|
|
|---|---|---|---|
| Authors | Magnus Westerlund , Colin Perkins , Jonathan Lennox | ||
| Last updated | 2014-08-18 (Latest revision 2014-02-14) | ||
| Replaces | draft-westerlund-avtcore-multi-media-rtp-session | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | Roni Even | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 and RFC 3551 to enable this behaviour 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.)