Browse Prior Art Database

RTP Profile for Audio and Video Conferences with Minimal Control (RFC1890)

IP.com Disclosure Number: IPCOM000004145D
Original Publication Date: 1996-Jan-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 23 page(s) / 35K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Audio-Video Transport Working Group: AUTHOR [+2]

Abstract

This memo describes a profile 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 text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 9% of the total text.

Network Working Group Audio-Video Transport Working Group

Request for Comments: 1890 H. Schulzrinne

Category: Standards Track GMD Fokus

January 1996

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.

Abstract

This memo describes a profile 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.

The 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. However, the encoding definitions are

independent of the particular transport mechanism used. 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.

1. Introduction

This profile defines aspects of RTP left unspecified in the RTP

Version 2 protocol definition (RFC 1889). This profile is intended

for the use within audio and video conferences with minimal session

control. In particular, no support for the negotiation of parameters

or membership control is provided. The profile is expected to be

useful in sessions where no negotiation or membership control are

used (e.g., using the static payload types and the membership

indications provided by RTCP), but this profile may also be useful in

conjunction with a higher-level control protocol.

Use of this profile occurs by use of the appropriate applications;

there is no explicit indication by port number, protocol identifier

or the like.

Other profiles may make different choices for the items specified

here.

2. RTP and RTCP Packet Forms and Protocol Behavior

The section "RTP Profiles and Payload Format Specification"

enumerates a number of items that can be specified or modified in a

profile. This section addresses these items. Generally, this profile

follows the default and/or recommended aspects of the RTP

specification.

RTP data header: The standard format of the fixed RTP data header is

used (one marker bit).

Payload types: Static payload types are defined in Section 6.

RTP data h...