RFC 4247: Requirements for Header Compression over MPLS
In plain English — editorial summary, not part of the RFC
Voice over IP (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, such as enhanced compressed RTP (ECRTP) and robust header compression (ROHC). We consider using MPLS to route compressed packets over an MPLS Label Switched Path (LSP) without compression/decompression cycles at each router. This approach can increase the bandwidth efficiency as well as processing scalability of the maximum number of simultaneous flows that use header compression at each router. In this document, we give a problem statement, goals and requirements, and an example scenario. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4247
- Published
- November 2005
- Authors
- J. Ash; B. Goode; J. Hand; R. Zhang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6315IANA Registration for Enumservice 'iax'Current
July 2011
- RFC 4901Protocol Extensions for Header Compression over MPLSCurrent
June 2007
- RFC 5574RTP Payload Format for the Speex CodecCurrent
June 2009
- RFC 6035Session Initiation Protocol Event Package for Voice Quality ReportingCurrent
November 2010
- RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent
November 2011
- RFC 6405Voice over IP (VoIP) SIP Peering Use CasesCurrent
November 2011
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 4182Removing a Restriction on the use of MPLS Explicit NULLUpdated
September 2005
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?