Multiplexing RTP Data and Control Packets on a Single Port
draft-perkins-avt-rtp-and-rtcp-mux-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Magnus Westerlund , Colin Perkins | ||
| Last updated | 2008-04-16 (Latest revision 2006-09-25) | ||
| Replaced by | draft-ietf-avt-rtp-and-rtcp-mux | ||
| 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-avt-rtp-and-rtcp-mux | |
| 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 issues that arise when multiplexing RTP data packets and RTP control protocol (RTCP) packets on a single UDP port. It updates RFC 3550 to describe when such multiplexing is, and is not, appropriate, and explains how the Session Description Protocol (SDP) can be used to signal multiplexed sessions.
Authors
Magnus Westerlund
Colin Perkins
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)