RTP Considerations for Endpoints Sending Multiple Media Streams
draft-lennox-avtcore-rtp-multi-stream-02
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Jonathan Lennox , Magnus Westerlund , Qin Wu , Colin Perkins | ||
| Last updated | 2013-05-13 (Latest revision 2013-02-25) | ||
| Replaced by | RFC 8108 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-avtcore-rtp-multi-stream | |
| 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 expands and clarifies the behavior of the Real-Time Transport Protocol (RTP) endpoints when they are sending multiple media streams in a single RTP session. In particular, issues involving Real-Time Transport Control Protocol (RTCP) messages are described. This document updates RFC 3550 in regards to handling of multiple SSRCs per endpoint in RTP sessions.
Authors
Jonathan Lennox
Magnus Westerlund
Qin Wu
Colin Perkins
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)