RFC 4815: RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095
In plain English — editorial summary, not part of the RFC
RFC 3095 defines the RObust Header Compression (ROHC) framework and profiles for IP (Internet Protocol), UDP (User Datagram Protocol), RTP (Real-Time Transport Protocol), and ESP (Encapsulating Security Payload). Some parts of the specification are unclear or contain errors that may lead to misinterpretations that may impair interoperability between different implementations. This document provides corrections, additions, and clarifications to RFC 3095; this document thus updates RFC 3095. In addition, other clarifications related to RFC 3241 (ROHC over PPP), RFC 3843 (ROHC IP profile) and RFC 4109 (ROHC UDP-Lite profiles) are also provided. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4815
- Published
- February 2007
- Authors
- L-E. Jonsson; K. Sandlund; G. Pelletier; P. Kremer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 33
- Also known as
- —
Topics
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 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 5426Transmission of Syslog Messages over UDPCurrent
March 2009
- RFC 3257Stream Control Transmission Protocol Applicability StatementCurrent
April 2002
- RFC 6679Explicit Congestion Notification (ECN) for RTP over UDPUpdated
August 2012
- RFC 2454IP Version 6 Management Information Base for the User Datagram ProtocolObsoleted
December 1998
- RFC 7604Comparison of Different NAT Traversal Techniques for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
September 2015
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?