RFC 3551 (rfc3551) - Page 1 of 44

RTP Profile for Audio and Video Conferences with Minimal Control

Alternative Format: Original Text Document

Next >

Network Working Group                                     H. Schulzrinne
Request for Comments: 3551                           Columbia University
Obsoletes: 1890                                                S. Casner
Category: Standards Track                                  Packet Design
                                                               July 2003

              RTP Profile for Audio and Video Conferences
                          with Minimal Control

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.


   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.

Schulzrinne & Casner        Standards Track

Next >

Web Standards & Support:

Link to and support eLook.org Powered by LoadedWeb Web Hosting
Valid XHTML 1.0! Valid CSS! eLook.org FireFox Extensions