rfc3095中文版_RFC3095

RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed

第一阶段

分类确定书的种类和分类

RFC协议

中心思想整本书在谈什么

Relevant information from past packets is maintained in a context. The context information is used to compress (decompress) subsequent packets.

提纲按照顺序与关系，列出全书的重要部分。将全书的纲要拟出来之后，再将各部分的纲要也一一列出。

3. Background

3.1. Header compression fundamentals

The main reason why header compression can be done at all is the fact that there is significant redundancy between header fields

Relevant information from past packets is maintained in a context.

The context information is used to compress (decompress) subsequent packets.

The compressor and decompressor update their contexts upon certain events.

3.2. Existing header compression schemes

CTCP compresses the 40 octet IP+TCP header to 4 octets.

CRTP [CRTP, IPHC] is a header compression scheme that compresses 40 octets of IPv4/UDP/RTP headers to a minimum of 2 octets when the UDP Checksum is not enabled. If the UDP Checksum is enabled, the minimum CRTP header is 4 octets.

CRTP uses explicit signaling messages from decompressor to compressor, called CONTEXT_STATE messages, to indicate that the context is out of sync.

3.3. Requirements on a new header compression scheme

The major problem with CRTP is that it is not sufficiently robust against packets being damaged between compressor and decompressor.

3.4. Classification of header fields

4. Header compression framework

4.1. Operating assumption

Channels

ROHC header-compressed packets flow on channels. Some cellular radio links can have several channels connecting the same pair of nodes. Each channel can have different characteristics in terms of error rate, bandwidth, etc.

Context identifiers

On some channels, the ability to transport multiple packet streams is required.

4.2. Dynamicity

The ROHC protocol achieves its compression gain by establishing state information at both ends of the link

Some state information is established at the time a channel is established.

An example of negotiated channel state is the highest context ID number to be used by the compressor (MAX_CID).

4.3. Compression and decompression states

one compressor machine and one decompressor machine, each instantiated once per context.

The compressor and the decompressor have three states each

Both machines start in the lowest compression state and transit gradually to higher states.

Transitions need not be synchronized between the two machines. In normal operation it is only the compressor that temporarily transits back to lower states. The decompressor will transit back only when context damage is detected.

4.3.1. Compressor states

For ROHC compression, the three compressor states are the Initialization and Refresh (IR), First Order (FO), and Second Order (SO) states.

The compressor starts in the lowest compression state (IR) and transits gradually to higher compression states.+----------+ +----------+ +----------+

IR State FO State SO State

+----------+ +----------+ +----------+

Decisions about transitions between the various compression states are taken by the compressor on the basis of:variations in packet headers

positive feedback from decompressor (Acknowledgments – ACKs)

negative feedback from decompressor (Negative ACKs – NACKs)

periodic timeouts (when operating in unidirectional mode, i.e., over simplex channels or when feedback is not enabled)4.3.1.1. Initialization and Refresh (IR) State

The purpose of the IR state is to initialize the static parts of the context at the decompressor or to recover after failure.

In this state, the compressor sends complete header information. This includes all static and nonstatic fields in uncompressed form plus some additional information.

The compressor stays in the IR state until it is fairly confident that the decompressor has received the static information correctly.4.3.1.2. First Order (FO) State

Some or all packets sent in the FO state carry context updating information.4.3.1.3. Second Order (SO) State

The compressor enters the SO state when the header to be compressed is completely predictable given the SN (RTP Sequence Number) and the compressor is sufficiently confident that the decompressor has acquired all parameters of the functions from SN to other fields.

4.3.2. Decompressor states

The decompressor starts in its lowest compression state, “No Context” and gradually transits to higher states. The decompressor state machine normally never leaves the “Full Context” state once it has entered this state.+--------------+ +----------------+ +--------------+

No Context Static Context | Full Context |

+--------------+ +----------------+ +--------------+Initially, while working in the “No Context” state, the decompressor has not yet successfully decompressed a packet.

Once a packet has been decompressed correctly, the decompressor can transit all the way to the “Full Context” state, and only upon repeated failures will it transit back to lower states.

There, reception of any pac