Issues and Options for RTP Multiplexing
draft-ietf-avt-muxissues-00
| Document | Type |
Expired Internet-Draft
(avt WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jonathan Rosenberg , Henning Schulzrinne | ||
| Last updated | 1998-10-02 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memorandum discusses the issues and options involved in the design of a new transport protocol for multiplexed voice within a single packet. The intended application is the interconnection of devices which provide trunking or long distance telephone service over the Internet. Such devices have many voice connections simultaneously between them. Multiplexing them into the same connection improves on the efficiency, enables the use of low bitrate voice codecs, and improves scalability. Options and issues con- cerning timestamping, payload type identification, length indication, and channel identification are discussed. Sev- eral possible header formats are identified, and their efficiencies are compared.
Authors
Jonathan Rosenberg
Henning Schulzrinne
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)