RObust Header Compression (ROHC): The ROHC Architecture
draft-jonsson-rohc-architecture-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Lars-Erik Jonsson | ||
| Last updated | 2002-06-14 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
RFC 3095 defines a Proposed Standard framework with profiles for RObust Header Compression (ROHC). Various concepts are introduced within the standard, which might be difficult to understand, and especially how these relate to the surrounding environments where header compression may be used. This document aims at clarifying the architectural aspects of ROHC, discussing terms such as ROHC instances, ROHC channels, ROHC feedback, ROHC contexts, and how these terms relate to other terms like network elements and IP interfaces, commonly used when for example addressing MIB issues.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)