BCP 110, RFC 4170 on Tunneling Multiplexed Compressed RTP (TCRTP)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


        BCP 110
        RFC 4170

        Title:      Tunneling Multiplexed Compressed RTP (TCRTP)
        Author(s):  B. Thompson, T. Koren, D. Wing
        Status:     Best Current Practice
        Date:       November 2005
        Mailbox:    brucet@cisco.com, tmima@cisco.com, dwing@cisco.com
        Pages:      24
        Characters: 48990
        SeeAlso:    BCP0110

        I-D Tag:    draft-ietf-avt-tcrtp-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4170.txt


This document describes a method to improve the bandwidth
utilization of RTP streams over network paths that carry multiple
Real-time Transport Protocol (RTP) streams in parallel between two
endpoints, as in voice trunking.  The method combines standard
protocols that provide compression, multiplexing, and tunneling over
a network path for the purpose of reducing the bandwidth used when
multiple RTP streams are carried over that path.

This document is a product of the Audio/Video Transport Working Group
of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
<ftp://ftp.isi.edu/in-notes/rfc4170.txt>
_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux