RFC 4901: Protocol Extensions for Header Compression over MPLS
In plain English — editorial summary, not part of the RFC
This specification defines how to use Multi-Protocol Label Switching (MPLS) to route Header-Compressed (HC) packets over an MPLS label switched path. HC can significantly reduce packet-header overhead and, in combination with MPLS, can also increases bandwidth efficiency and processing scalability in terms of the maximum number of simultaneous compressed flows that use HC at each router). Here we define how MPLS pseudowires are used to transport the HC context and control messages between the ingress and egress MPLS label switching routers. This is defined for a specific set of existing HC mechanisms that might be used, for example, to support voice over IP. This specification also describes extension mechanisms to allow support for future, as yet to be defined, HC protocols. In this specification, each HC protocol operates independently over a single pseudowire instance, very much as it would over a single point-to-point link. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4901
- Published
- June 2007
- Authors
- J. Ash; J. Hand; A. Malis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 34
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4247Requirements for Header Compression over MPLSCurrent
November 2005
- RFC 4905Encapsulation Methods for Transport of Layer 2 Frames over MPLS NetworksCurrent
June 2007
- RFC 4906Transport of Layer 2 Frames Over MPLSCurrent
June 2007
- RFC 4920Crankback Signaling Extensions for MPLS and GMPLS RSVP-TECurrent
July 2007
- RFC 4842Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)Current
April 2007
- RFC 4804Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE TunnelsCurrent
February 2007
- RFC 4781Graceful Restart Mechanism for BGP with MPLSCurrent
January 2007
- RFC 5038The Label Distribution Protocol (LDP) Implementation Survey ResultsCurrent
October 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?