ROHC Formal Notation Requirements
draft-ozegovic-rohc-fn-requirements-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Julije Ozegovic | ||
| Last updated | 2003-07-23 | ||
| 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
This draft describes requirements expected to be achieved with profile formal notation system for ROHC. The RObust Header Compression (ROHC) [1] scheme is designed to compress packet headers over error prone channels. It is built around an extensible core framework that can be tailored to compress new protocol stacks by adding additional ROHC profiles. The role of formal notation is to provide a simple method for ROHC profile specification. It is to be used in the phase of profile refinement to achieve maximal compression ratio possible, as well as in the phase of software implementation to provide unambiguous profile specification.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)