A new Request for Comments is now available in online RFC libraries.


        RFC 1889:

        Title:      RTP: A Transport Protocol for Real-Time
                    Applications 
        Author:     Audio-Video Transport Working Group,
                    H. Schulzrinne, S. Casner, R. Frederick & 
                    V. Jacobson
        Date:       January 1996
        Mailbox:    schulzrinne@fokus.gmd.de, casner@precept.com,
                    frederic@parc.xerox.com, van@ee.lbl.gov
        Pages:      75
        Characters: 188,544
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1889.txt


This memo describes RTP, the real-time transport protocol. RTP
provides end-to-end network transport functions suitable for
applications transmitting real-time data, such as audio, video or
simulation data, over multicast or unicast network services. RTP does
not address resource reservation and does not guarantee
quality-of-service for real-time services. The data transport is
augmented by a control protocol (RTCP) to allow monitoring of the data
delivery in a manner scalable to large multicast networks, and to
provide minimal control and identification functionality. RTP and RTCP
are designed to be independent of the underlying transport and network
layers. The protocol supports the use of RTP-level translators and
mixers.  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