Protocol Extensions for Header Compression over MPLS
draft-ash-avt-hc-over-mpls-protocol-01

Document Type Replaced Internet-Draft (individual in gen area)
Author Gerald Ash 
Last updated 2015-10-14 (latest revision 2008-04-16)
Replaced by RFC 4901
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-avt-hc-over-mpls-protocol
Action Holders
(None)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Allison 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-hc-over-mpls-protocol-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 typically 48 bytes, while the voice payload is often no more than 30 bytes, for example. Header compression can significantly reduce the overhead through various compression mechanisms. MPLS is used to route header-compressed (HC) packets over an MPLS LSP without compression/decompression cycles at each router. Such an HC over MPLS capability increases the bandwidth efficiency as well as processing scalability of the maximum number of simultaneous compressed flows that use HC at each router. MPLS pseudowires are used to transport the HC context and other control messages between the ingress and egress MPLS label switched router (LSR), and the pseudowires define a point to point instance of each HC session at the header decompressor. Standard HC methods (e.g., ECRTP, ROHC, etc.) are re-used to determine the context.

Authors

Gerald Ash (gash@att.com)

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