About: Robust Header Compression is a research topic. Over the lifetime, 398 publications have been published within this topic receiving 7024 citations. The topic is also known as: ROHC.
TL;DR: This document specifies an IPv6 header compression format for IPv6 packet delivery in Low Power Wireless Personal Area Networks (6LoWPANs) and a framework for compressing next headers.
Abstract: This document updates RFC 4944, "Transmission of IPv6 Packets over
IEEE 802.15.4 Networks". This document specifies an IPv6 header
compression format for IPv6 packet delivery in Low Power Wireless
Personal Area Networks (6LoWPANs). The compression format relies on
shared context to allow compression of arbitrary prefixes. How the
information is maintained in that shared context is out of scope. This
document specifies compression of multicast addresses and a framework
for compressing next headers. UDP header compression is specified
within this framework. [STANDARDS-TRACK]
TL;DR: This document describes a method for compressing the headers of IP/UDP/RTP datagrams to reduce overhead on low-speed serial links.
Abstract: This document describes a method for compressing the headers of IP/UDP/RTP datagrams to reduce overhead on low-speed serial links. In many cases, all three headers can be compressed to 2-4 bytes.
TL;DR: This document describes how to compress multiple IP headers and TCP and UDP headers per hop over point to point links.
Abstract: This document describes how to compress multiple IP headers and TCP and UDP headers per hop over point to point links. The methods can be applied to of IPv6 base and extension headers, IPv4 headers, TCP and UDP headers, and encapsulated IPv6 and IPv4 headers.
TL;DR: This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment and various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast.
Abstract: This RFC defines a proposed standard protocol to support NetBIOS
services in a TCP/IP environment. Both local network and internet
operation are supported. Various node types are defined to accommodate
local and internet topologies and to allow operation with or without
the use of IP broadcast. This RFC describes the NetBIOS-over-TCP
protocols in a general manner, emphasizing the underlying ideas and
techniques. Detailed specifications are found in a companion RFC,
"Protocol Standard For a NetBIOS Service on a TCP/UDP Transport:
Detailed Specifications".
TL;DR: In this article, a robust IP/UDP/RTP header compression scheme is proposed to correctly reconstruct IP/uDP/rTP headers in the presence of packet losses and errors of unreliable networks, where the header compression mechanism may include a compressor/de-compressor implemented for operation similarly to RFC 2508.
Abstract: A robust IP/UDP/RTP header compression mechanism is provided to correctly reconstruct IP/UDP/RTP headers in the presence of packet losses and errors of unreliable networks. The header compression mechanism may include a compressor/de-compressor implemented for operation similarly to RFC 2508 but designed specifically to address robustness when employed in lossy and error-prone networks. The robust header compression scheme requires that, when a second-order difference of a field is non-zero, not only a particular RTP packet whose second-order difference is non-zero is sent with the new first-order difference, but also those following packets are also sent with the new first-order difference as long as: (a) a period pre-determined by factors such as channel characteristics (e.g., link round-trip time RTT/inter-packet separation); or (b) a positive confirmation is received by the compressor that the new first-order difference has been correctly received. In addition, during a period of communicating with the new first-order difference, if the corresponding RTP field changes again with non-zero second-order difference, the “new” first-order difference is combined with the original first-order difference such that the two first-order differences may be appended together as a simple means of communicating the two first-order differences reliably.