RFC 3095: RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed
In plain English — editorial summary, not part of the RFC
This document specifies a highly robust and efficient header compression scheme for RTP/UDP/IP (Real-Time Transport Protocol, User Datagram Protocol, Internet Protocol), UDP/IP, and ESP/IP (Encapsulating Security Payload) headers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3095
- Published
- July 2001
- Authors
- C. Bormann; C. Burmeister; M. Degermark; H. Fukushima; H. Hannu; L-E. Jonsson; R. Hakenberg; T. Koren; K. Le; Z. Liu; A. Martensson; A. Miyazaki; K. Svanbro; T. Wiebke; T. Yoshimura; H. Zheng
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 168
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
- RFC 2508Compressing IP/UDP/RTP Headers for Low-Speed Serial LinksCurrent
February 1999
- RFC 7604Comparison of Different NAT Traversal Techniques for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
September 2015
- RFC 3241Robust Header Compression (ROHC) over PPPUpdated
May 2002
- RFC 3408Zero-byte Support for Bidirectional Reliable Mode (R-mode) in Extended Link-Layer Assisted RObust Header Compression (ROHC) ProfileCurrent
December 2002
- RFC 3816Definitions of Managed Objects for RObust Header Compression (ROHC)Current
June 2004
- RFC 3843RObust Header Compression (ROHC): A Compression Profile for IPUpdated
June 2004
- RFC 4019RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) LiteUpdated
April 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?