metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port

Still current, but amended. Parts of this document are changed or extended by RFC 8035, RFC 8858. Read both.

In plain English — editorial summary, not part of the RFC

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 and RFC 3551 to describe when such multiplexing is and is not appropriate, and it explains how the Session Description Protocol (SDP) can be used to signal multiplexed sessions. [STANDARDS-TRACK]

Document record

Document ID
RFC5761
Published
April 2010
Authors
C. Perkins; M. Westerlund
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
13
Also known as
—
Updates:
RFC 3550, RFC 3551
Updated by:
RFC 8035, RFC 8858

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/5761-multiplexing-rtp-data-and-control-packets-on-a-single-port