home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_a_c
/
draft-ietf-avt-profile-06.txt
< prev
next >
Wrap
Text File
|
1996-01-26
|
3KB
|
72 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1890:
Title: RTP Profile for Audio and Video Conferences with
Minimal Control
Author: Audio-Video Transport Working Group,
H. Schulzrinne
Date: January 1996
Mailbox: schulzrinne@fokus.gmd.de
Pages: 18
Characters: 37,509
Updates/Obsoletes: none
URL: ftp://ds.internic.net/rfc/rfc1890.txt
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. This RFC is the product of the Audio/Video Transport
Working Group of the IETF.
This is now a Proposed Standard Protocol.
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.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds
USC/Information Sciences Institute