RTP Profile for Audio and Video Conferences with Minimal Control
RFC 3551, “RTP Profile for Audio and Video Conferences with Minimal Control”, is an Internet Standard document published in July 2003 by H. Schulzrinne, S. Casner. It obsoletes RFC 1890. It has since been updated by RFC 5761, RFC 7007, RFC 8860. The canonical text is published by the RFC Editor.
Abstract
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]
What “Internet Standard” means
A mature, widely-implemented specification that has completed the full IETF standards process — the highest maturity level on the standards track.
The canonical text of RFC 3551 is hosted at rfc-editor.org. Available in TXT,PS,PDF,HTML.
- RFC 3550 RTP: A Transport Protocol for Real-Time Applications
- RFC 3552 Guidelines for Writing RFC Text on Security Considerations
- RFC 3549 Linux Netlink as an IP Services Protocol
- RFC 3553 An IETF URN Sub-namespace for Registered Protocol Parameters
- RFC 3548 The Base16, Base32, and Base64 Data Encodings
- RFC 3554 On the Use of Stream Control Transmission Protocol with IPsec
- RFC 3547 The Group Domain of Interpretation
- RFC 3555 MIME Type Registration of RTP Payload Formats