database logo graphic

STD 65

RFC 3551

"RTP Profile for Audio and Video Conferences with Minimal Control", July 2003

Canonical URL:
http://www.rfc-editor.org/rfc/rfc3551.txt
This document is also available in these non-normative formats: PDF, PostScript, PDF with images.
Status:
INTERNET STANDARD (changed from DRAFT STANDARD)
Obsoletes:
RFC 1890
Updated by:
RFC 5761, RFC 7007
Authors:
H. Schulzrinne
S. Casner
Stream:
IETF
Source:
avt (rai)

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


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]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Go to the RFC Editor Homepage.