RFC 4170: Tunneling Multiplexed Compressed RTP (TCRTP)
In plain English — editorial summary, not part of the RFC
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 specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4170
- Published
- November 2005
- Authors
- B. Thompson; T. Koren; D. Wing
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- rai
- Pages
- 24
- Also known as
- BCP110
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4175RTP Payload Format for Uncompressed VideoUpdated
September 2005
- RFC 4102Registration of the text/red MIME Sub-TypeUpdated
June 2005
- RFC 4060RTP Payload Formats for European Telecommunications Standards Institute (ETSI) European Standard ES 202 050, ES 202 211, and ES 202 212 Distributed Speech Recognition EncodingCurrent
May 2005
- RFC 4352RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio CodecCurrent
January 2006
- RFC 3952Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) SpeechCurrent
December 2004
- RFC 4587RTP Payload Format for H.261 Video StreamsCurrent
August 2006
- RFC 4628RTP Payload Format for H.263 Moving RFC 2190 to Historic StatusCurrent
February 2007
- RFC 4629RTP Payload Format for ITU-T Rec. H.263 VideoCurrent
January 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?