metasystema.org
UpdatedINTERNET STANDARDIETF streamSTD65

RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control

Still current, but amended. Parts of this document are changed or extended by RFC 5761, RFC 7007, RFC 8860. Read both.

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

This document describes a profile called "RTP/AVP" for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. It provides interpretations of generic fields within the RTP specification suitable for audio and video conferences. In particular, this document defines a set of default mappings from payload type numbers to encodings. This document also describes how audio and video data may be carried within RTP. It defines a set of standard encodings and their names when used within RTP. The descriptions provide pointers to reference implementations and the detailed standards. This document is meant as an aid for implementors of audio, video and other real-time multimedia applications. This memorandum obsoletes RFC 1890. It is mostly backwards-compatible except for functions removed because two interoperable implementations were not found. The additions to RFC 1890 codify existing practice in the use of payload formats under this profile and include new payload formats defined since RFC 1890 was published. [STANDARDS-TRACK]

Document record

Document ID
RFC3551
Published
July 2003
Authors
H. Schulzrinne; S. Casner
Status
INTERNET STANDARD
Stream
IETF
Area
rai
Pages
44
Also known as
STD65
Obsoletes:
RFC 1890
Updated by:
RFC 5761, RFC 7007, RFC 8860

Topics

Referenced by

3 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/3551-rtp-profile-for-audio-and-video-conferences-with-minimal-control