Skip to main content

Requirements for ECRTP over MPLS
draft-ash-avt-ecrtp-over-mpls-reqs-01

Document Type Expired Internet-Draft (individual in gen area)
Authors Bur Goode , Gerald Ash , Jim Hand , Raymond Zhang
Last updated 2005-05-26 (Latest revision 2004-01-27)
Stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
Expired & archived
plain text htmlized pdfized bibtex
Stream WG state (None)
Document shepherd (None)
IESG IESG state Expired (IESG: Dead)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-ash-avt-ecrtp-over-mpls-reqs-01.txt

Abstract

VoIP typically uses the encapsulation voice/RTP/UDP/IP. When MPLS labels are added, this becomes voice/RTP/UDP/IP/MPLS-labels. For an MPLS VPN, the packet header is at least 48 bytes, while the voice payload is often no more than 30 bytes, for example. VoIP header compression can significantly reduce the VoIP overhead through various compression mechanisms, such as enhanced compressed RTP (ECRTP). We consider using MPLS to route ECRTP compressed packets over an MPLS LSP without compression/decompression cycles at each router. Such an ECRTP over MPLS capability can increase the bandwidth efficiency as well as processing scalability of the maximum number of simultaneous VoIP flows that use header compression at each router.

Authors

Bur Goode
Gerald Ash
Jim Hand
Raymond Zhang

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)